HDTenEightyP/NetNews huggingface dataset:
From: unixlan+@pitt.edu (Wei-ming William Lin)
Newsgroups: comp.os.ms-windows.programmer.misc
Subject: Wanted: MSC 6.0a (Yes, !! 6.0a !!) (Please read if you have
Date: 8 Oct 92 13:48:13 GMT
Organization: University of Pittsburgh


***************************************************************************
 Due to the system problem, the machine I posted this messages last
time won't accept your reply.  So please, if you got trouble, try to
reply to this account again: unixlan@unix.cis.pitt.edu.  Sorry for the trouble.
			     ^^^^^^^^^^^^^^^^^^^^^^^^^
***************************************************************************

Hi Folks,

I know this is not the best place to do so, but I need your help!!

Don't say I am crazy.  Yes, I need your olde version of MSC!!  My old libraries
can support nothing but MSC 6.0, so.....  If you have a copy of MSC 6.0a
gathering dust in your shelf, now is the best time to send it out.  It does not
have to be in the mint condition, but at least descent.  Manuals must be 
complete.  And if you still have your registration card, that will be perfect 
(although not necessary).  Just remember, IT MUST BE 6.0a, NOT 6.0.  Please 
reply by e-mail.  Thanx in advance. (One more: 3.5" is preferred,
although 5.25" is OK.)

Willie

"UNIX(tm), X & LAN --- The Promise of the Future!!"
"And OS/2 V2.0!!"

+=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=+
| Internet e-mail:                       Mom Bell:                        |
| unixlan@unix.cis.pitt.edu                 H: (614)267-2674  (after 9pm) |
| wmlin@speedy.cs.pitt.edu                  O: (614)888-3833              |
| Compu$erve: 71650,1444                                                  |
+=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=+
From: hjh@goose.dsto.gov.au (Howard Harvey)
Newsgroups: comp.os.ms-windows.programmer.misc
Subject: Re: reply: serialnumber harddisk
Date: 15 Oct 92 17:01:49 GMT

eduard@htsa.aha.nl (Eduard Beijnes) writes:

>The following programs writes 2911.1971 as a serialnumber on the 
>default drive (29 nov 1971) 

>----- uuencoded program / cut here -----
>begin 600 serial.com
>4N %ILP"Z#@'-(;1,S2$  '$9$2D 
> 
>end
>----- end of uuencoded program /cut here -----

>dump van debug.com:

>2F73:0100 B80169        MOV	AX,6901                            
>2F73:0103 B300          MOV	BL,00                              
>2F73:0105 BA0E01        MOV	DX,010E                            
>2F73:0108 CD21          INT	21                                 
>2F73:010A B44C          MOV	AH,4C                              
>2F73:010C CD21          INT	21                                 
>2F73:010E 0000          ADD	[BX+SI],AL                         
>2F73:0110 7119          JNO	q012B                               
>2F73:0112 1129          ADC	[BX+DI],BP          

>I don't have the documentation with me because I am on school while
>I am writing this.

>I am not sure but if you change MOV AX,6901 in MOV AX,6900 it reads the
>serialnumber.

>If this doesn't work email me (eduard@solist.htsa.aha.nl) and I will
>look it up

You are right: 6900 returns the serial number in the disk info buffer
pointed to by DS:DX

Now my question:  I have precise detail on how the number is initially
generated.  It is a combination of date and time.  However, on a hard disk
the top two bits of the second group are set.  In theory they are beyond the
range of any combination of date and time.  Both bits may not be set.
I have seen different combinations of these bits on different systems.
Does anyone know the real mechanism for generating these two bits?

BTW, the probability of any two diskettes having the same serial number is
about 1 in 2**28, but playing around with function 6901 could lead to
identical numbers and hence a failure by MS-DOS to identify a changed
diskette (see MS-DOS User's Guide, p134)

Howie

----------------------------------------------------------------------------
Howard J. Harvey                              | Email: hjh@aeg.dsto.gov.au
SOIC - Avionics Integration                   | Phone: +61 8 259 6322
Air Operations Division                       | FAX:   +61 8 259 5507
Defence Science and Technology Organisation   | c = 1802617499785.254116 f/f
Salisbury, South Australia                    |     (furlongs/fortnight)
----------------------------------------------------------------------------
Newsgroups: comp.os.ms-windows.programmer.misc
From: blakeco@microsoft.com (Blake Coverett)
Subject: Re: Browse Sequences in WinHelp - how?
Date: 08 Oct 92 17:08:27 GMT
Organization: Microsoft Canada Inc.
Keywords: help compiler,help

In article <1992Oct5.173145.10025@cs.tu-berlin.de> loewis@opal.cs.tu-berlin.de (Martin v.Loewis) writes:
>Summary: I found no way to define browse sequences using hc31,
>	 the sdk manual is wrong or I missed something.

Sounds like option two to me. :-)

[a correct description of adding footnotes deleted]

Sounds like you are missing the "BrowseButtons()" macro from the [CONFIG]
section of your HPJ file.  The "+" footnotes provide the browse sequence
data, but you need the macro to enable display of the buttons.

>If it does matter, I'm using hc31 from Borland, but the compiler of
>the SDK is not better.

They are identical, Borland licences the help compiler from MS.

>Another question about help compilers:
>How can one use the INDEX option? If I'm using it, I get warnings:
>'Unknown INDEX option in [OPTIONS] section', and the option is 
>ignored.

INDEX was changed to CONTENTS with the 3.1 help compiler (in the same fashion
that the label on the button changed in the help engine.)

-Blake
-- 
#include <std/disclaimer.h>                       blakeco@microsoft.com
Mail Flames, Post Apologies.                      ...!uunet!microsoft!blakeco
Newsgroups: comp.os.ms-windows.programmer.misc
From: cwvernon@napier.uwaterloo.ca (Vern)
Subject: IconTitleFont option
Organization: University of Waterloo
Date: Thu, 15 Oct 1992 01:58:13 GMT

What is the option that changes the icon font in WIN.INI?  Is it:

IconTitleFont=<font>
IconTitleFontSize=<font-size>
Newsgroups: comp.os.ms-windows.programmer.misc,comp.windows.ms.programmer,comp.os.ms-windows.misc
From: hewitt@vaxc.cc.monash.edu.au
Newsgroups: comp.os.ms-windows.programmer.misc
Subject: Re: Simple way to author Help Files
Date: 13 Oct 92 07:55:06 +1000
Organization: Computer Centre, Monash University, Australia

Help Files for Windows Applications are very easily written using Xantippe
which is available under /pub/pc/win3/util at many sites.  It costs $25 for
a usable version and $99 for the 'Commercial' version.  Very easy to use
and takes nearly all the pain out the process - much better than W4W and RTF
format.

David Hewitt
Chemistry Department
Monash University
Newsgroups: comp.os.ms-windows.programmer.misc
From: blakeco@microsoft.com (Blake Coverett)
Subject: Re: Undocumented functions
Date: 08 Oct 92 16:53:00 GMT
Organization: Microsoft Canada Inc.

In article <1apnqpINNqf9@iraul1.ira.uka.de> s_furrer@irau28.ira.uka.de (Andreas Furrer) writes:
>Does anybody know the usage of the undocumented functions
>
>ExtractAssociatesIcon
>ExtractInternalIcon (or InternalExtractIcon??)
>GetIconHeader

Bah, I don't feel energetic enough at the moment to get out my "if you needed
them they wouldn't be undocumented" soapbox.

Have a look a FindExecutable and ExtractIcon instead.

>It seems that you have to use them for setting the icon of
>a DOS-Application.

Nope.

>Or - Who you set the icon of a DOS-Application?

Search for "Shell Dynamic-Data Exchange Interface Overview" in win31wh.hlp.
In a nutshell, when you launch a DOS app the WinOldApp module will 
attempt to find a DDE server to provide the description/caption, working
directory and icon that it should use for that app.  Normally ProgMan
will be that DDE server, but if your app launches a DOS app, then it needs
to provide that service.

-Blake
-- 
#include <std/disclaimer.h>                       blakeco@microsoft.com
Mail Flames, Post Apologies.                      ...!uunet!microsoft!blakeco
From: lou@pacvax.pacersoft.com (Lou Iannucci)
Newsgroups: comp.os.ms-windows.programmer.misc
Subject: HELP - Windows 3.1 Custom Edit Control
Date: 12 Oct 92 13:36:16 GMT
Organization: Pacer Software Inc.
X-UserAgent: Nuntius v1.1.1d7
X-XXDate: Mon, 12 Oct 92 09:47:01 GMT

Help,
  I need to create a edit control for Windows 3.1 that supports multiple
fonts and font sizes for windows 3.1 in C++.   THANKS
From: equine@eng.umd.edu (Melinda L. Gierisch)
Newsgroups: comp.os.ms-windows.programmer.misc
Subject: MDI Child Window Menus
Summary: Creating menus on MDI child windows
Keywords: MDI, menu
Date: 14 Oct 92 20:11:33 GMT
Organization: College of Engineering, University of Maryland, College Park

I need help creating menus on MDI child windows.  If anyone out there
has any examples or hints on this, please let me know.

Thanks in advance,
Melinda Gierisch
From: kelfink@ecst.csuchico.edu (Kevin Fries)
Newsgroups: comp.os.ms-windows.programmer.misc
Subject: DLL dialog box.  (Rookie win. programmer)
Date: 16 Oct 92 15:39:33 GMT
Distribution: usa
Organization: California State University, Chico
NNTP-Posting-Host: cscihp.ecst.csuchico.edu


Hello,
	I'm tryin to pick up the art of windows programmig, following
Petzold's 3.0 guide.  We'll be getting the more up-to-date MS 7.0
compiler and SDK soon, but in the mean time, I wonder if someone can
give me some pointers.  Specifically:

	Can anyone show me sample code to open a dialog box from a DLL?

	Is there some large source for sample code in general?

	I've seen several package advertisements claiming to put
together C skeleton code fro a dialog description.  Has anyone tried one
of these?

	Thanks for any advice you have,

	Kevin Fries
	kelfink@cscihp.ecst.csuchico.edu
From: twbrown@PE-Nelson.COM (Tom W. Brown)
Newsgroups: comp.os.ms-windows.programmer.misc
Subject: Re: Icons for minimized Dialog Boxes
Date: 14 Oct 92 21:14:01 GMT
Organization: PE-Nelson

In article <92288.175936HELLER@DMSWWU1A.UNI-MUENSTER.DE>, HELLER@DMSWWU1A.UNI-MUENSTER.DE (Thomas Heller) writes:
|> How can associate Icons to Dialog Boxes?
|> 
|> Hint: SetClassWord(GCW_HICON) does work, but not as intended, 'cause all
|> Dailogs will display the same icon then. I want different icons, and only for
|> MY dialogs.
|> 
|> Thomas Heller

This may be tricky.  I know that if you register a window class with a NULL
icon then you can use GDI calls to paint into the icon area.  Effectively
a call to GetClientArea returns the correct information when iconic and you
can always call IsIconic() in your paint procedure to determine whether to
do normal stuff or do icon stuff.  This simplest thing is then to load your
icon from the resource file and do a DrawIcon().

However, you have no control over the call to RegisterClass in the case of
a dialog box and replacing the class icon with a NULL handle will affect
all dialogs as you've seen.

This sounds like a hack, but it's the only way I can think of to get around
this:

   - Register your own window class, one that has the desired icon.

   - When you want a dialog box, create a window of the above class and
     a dialog box for it that will be positioned to fit exactly in the
     window.  The window has the caption bar, etc. and the dialog box should
     be completely borderless.

   - I think there are only two messages you need to handle in the window
     procedure:

        WM_SIZE : handle this by doing a MoveWindow on the dialog to keep it
                  positioned in the parent window.

        WM_CLOSE: Send a CANCEL message to the dialog box and then, if ok,
                  destroy the window (not the dialog, the parent window).

   - If the dialog box procedure relies on doing things with the parent
     window handle (thinking it's your application window) you'll need to
     add another GetParent() call.

Since the parent window is fully under your control it displays your icon
when minimized.  It should look identical to a dialog that has its own caption
bar and system buttons.


----------------------------------------------------------------------------
Tom Brown               |  "Strange women, lying in ponds, distributing
PE Nelson Systems       |   swords is no basis for a system of government."
twbrown@pe-nelson.com   |                    Monty Python and the Holy Grail
----------------------------------------------------------------------------
Newsgroups: comp.os.ms-windows.programmer.misc
From: geirt@Lise.Unit.NO (Geir Torheim)
Subject: Summary: TDW and SVGA
Organization: Norwegian Institute of Technology
Date: Wed, 7 Oct 92 12:29:08 GMT


Some time ago I reported problems with TDW running in SVGA using an STB WIND/X
card.  Others were interested in this, therefore I post this summary.

1) Read the README file which came with your BC package. There is a section on
   TDW and different device drivers. (One of these are called STB.DLL.
   This one did not work with my card.)

2) If none of the drivers which came with BC fit your needs, try the
   Borland BBS. Lots of drivers. One of them is called SVGA.DLL. This
   should work with ALL superVGA cards. If you don't have access to the
   Borland BBS, let me know and I'll send you an uuencoded file.

3) Dr. Dobbs journal #192 contains info about TDW and custom video DLLs.
   (How to write your own..)

I'm currently using the SVGA.DLL, this works fine.

Thanks to Qiang Zheng, Chris Fortier and Timo K Saarelma, who supplied the
above information.

-geir

-- 
Geir Torheim                             email: geirt@lise.unit.no

Newsgroups: comp.windows.ms.programmer,comp.os.ms-windows.programmer.misc
From: wilcox@swarm.wustl.edu (Don Wilcox)
Subject: Re: Memory allocation in BC++ v3.1 of structures in windows
Organization: Washington University in St. Louis, MO
Date: Thu, 8 Oct 1992 19:45:36 GMT

In article <1992Oct8.191854.20153@cs.odu.edu> popkin@orchid.cs.odu.edu (Brian Popkin) writes:
>Hello Fellow Netters:
>
>I have a question I cannot find in any book.
>I am using bc++ v3.1.
>
>How do I allocate memory in windows for a pointer to a structure, a structure,
>or an array using the functions globalalloc etc in windows.
>

If I were you, I'd just use new and delete (or malloc and free).  They do
sub-segment allocation, and you don't have to carry handles around.  Since
locked blocks aren't a problem in protected mode, there is no penalty for this
approach, and nothing but benefits.

>Brian

-- 
Don Wilcox                         | "For I am not ashamed of the Gospel of
Washington University in St. Louis |   Christ, for it is the power of salvation
email: wilcox@swarm.wustl.edu      |   to all who believe."
Newsgroups: comp.os.ms-windows.programmer.misc
From: tdugan@news.weeg.uiowa.edu (Tim Dugan)
Subject: Re: Which C Compiler
Organization: University of Iowa, Iowa City, IA, USA
Date: Sat, 10 Oct 1992 09:34:03 GMT

In article <1992Oct9.174844.7129@cis.ohio-state.edu> jgeniec@banana.cis.ohio-state.edu (Joseph Geniec) writes:
>
>
>	You might want to consider Borland C++ with Object Windows. Object 
>Windows is a framework that is built upon the Windows API functions; it
>takes most of the hassle out of windows programming. However, I found
>that Borland defeats its own purpose by giving you extremely crappy
                                                    ^^^^^^^^^ ^^^^^^
>and cryptic manuals for a beginning windows programmer (like me!).
 ^^^ ^^^^^^^ ^^^^^^^
  .. Stuff deleted ...

Couldn't agree more.  I just finished a book called:
  
  Windows Programmer's Guide To Object Windows Library
  By Namir Clement Shammas
  Sams Publishing  ISBM 0-672-30106-7

It was well worth my time, I am now begining to think: "gee this ain't so
hard". 

                                   Hope its helps
                                   Tim M. Dugan








Newsgroups: comp.os.ms-windows.programmer.misc
From: geirt@Lise.Unit.NO (Geir Torheim)
Subject: Window an memory
Keywords: OWL, WIN31, enhanced mode, memory
Organization: Norwegian Institute of Technology
Date: Wed, 7 Oct 92 13:11:10 GMT

I have a simple app. developed using BC++ 3.1 and OWL, running under 
Windows 3.1 enhanced mode. The .exe file is 440 Kbytes (with debug info).
I allocate three large arrays and one large bitmap, a total of 900K.

I tried to run this on a 386 w. 6 MB of 'real' memory, 12MB virtual memory 
and win3.1 enhanced mode. Windows reported "Insufficient memory..".
Running the program on my 486 with 16MB is no problem.

When I removed the debug info, the program could run without any
problems on the 6MB machine as well. (the exe file became 197K ...)

I still feel unhappy about this. I believed that running in enhanced mode,
WIN could use all the (virtual) memory which is available ? Why wouldn't my
440K app. start??

I'm using the large memory model. I know this isn't recommended, (because you
have to fix the segments in memory) but I thought that running in protected
mode automagically solved this problem, since WIN can move the segments anyway.
Is this correct?
Do I have to use the GlobalAlloc() to get this behaviour?
Or can I use the malloc()?
Are there other reasons why I shouldnt use the large model?

Petzold talks alot about memory, but he also says that most of it applies to
real mode. It's not always clear in his text what applies to protected mode.
I'm only interested in protected mode. What are the rules here?

I guess a lot of people are interested in memory management. If you're a viz,
please enlighten us! (mail to me, and I can make a summary).


All answers appreciated,

-geir


-- 
Geir Torheim                             email: geirt@lise.unit.no

Newsgroups: comp.os.ms-windows.programmer.win32
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: Multiuser NT???
Date: 15 Oct 92 08:35:39 GMT
Organization: Microsoft Corporation

In article <719058360.F00113@monly.wlink.nl.wlink.nl> Mikael.Wahlgren@f1.n100.z60.wlink.nl (Mikael Wahlgren) writes:
>don't understand the low-budget a shareware-program starts with

We designed the cd-rom only option to be most attractive for developers with
limited budgets, whether developing shareware or not. $69 for final
product and pre-releases, or reasonable equivalent in other countries, set
a new low for comparable products. We have no program to give away the
documents, and instead, are placing emphasis on making the vast amount
of information readable on-line, and printable in sections. You will find
that this has improved further in the imminent "beta" release

-- Alistair
Newsgroups: comp.os.ms-windows.programmer.win32
From: kaz@iastate.edu (Jimmy Buffet)
Subject: Installing nt pre-beta
Summary: Installing nt pre-beta
Keywords: NT
Organization: Iowa State University, Ames IA
Date: Thu, 15 Oct 1992 23:52:04 GMT

I'm having slight probelms installing the windows nt pre-beta.  I have 3
partitions of my hard drive:  a dos, an OS/2, and an OS/2 boot manager.
It installed fine in my dos partition.  I got an error that it coulnd't find
the ntoskrn.exe file in \nt\system.  I changed the \winnt dir to \nt
and it still doesn't work.  I can't find any help in the documentation.  Any
ideas?  Thanks...

--
From: kenyee@sneakers (Ken Yee)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Fatal System Errors
Date: 12 Oct 92 09:50:10 EDT

In article <1992Oct09.001459.13838@microsoft.com> leehart@microsoft.com  
(Lee Hart) writes:
> In article <1992Oct8.024618.17756@solaris.rz.tu-clausthal.de>,  
hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter) writes:
> > This has also been discussed before, of course you can install NT  
after
> > you have installed OS/2 2.0. NT's flexboot just gets a little confused
> > about the drive letters. So change the x:\WINNT to
  Just a followup...changing the bus and DMA speed on my WD7000FASST
  SCSI card did not work.  I still get the 0x69 fatal error.
  Ah well, back to OS/2.  Hope the next NT beta fixes the problem.
  C'est la guerre...

 ken
Newsgroups: comp.os.ms-windows.programmer.win32
From: mab@mentor.cc.purdue.edu (Mike Brown)
Subject: Re: MS: New Windows NT DDK info
Keywords: DDK
Organization: Purdue University Computing Center
Date: Thu, 15 Oct 1992 23:32:32 GMT

In article <1992Oct14.222210.15648@microsoft.com> dwightm@microsoft.com (Dwight Matheny) writes:
>The documentation will be included 
>on the CD in both Postscript and Write format

Good move!  Write-format files will make it easier to print the
documentation on non-Postscript printers.  If it's not too late, I'd
encourage you to also do this with future SDK releases.  Any chance of
this happening in the October SDK release?

-- 
Mike Brown, Network Systems Programmer		Internet: mab@cc.purdue.edu
Purdue University Computing Center		Bitnet:   xmab@purccvm
1408 MATH, Room B18				Phone:    (317) 494-1787
West Lafayette, IN 47907-1408, USA		Fax:      (317) 494-0566
Newsgroups: comp.os.ms-windows.programmer.win32
From: johnhall@microsoft.com (John Hall)
Subject: Re: NT Under SCO Unix
Date: 16 Oct 92 00:48:07 GMT
Organization: Microsoft Corporation

In article peter@ferranti.com (peter da silva) writes:
| Actually, at least one Microsoft employee has indicated that they don't much
| care if it runs on a 386SX, either. I take that to imply that a >16MB memory
| requirement is not out of the question.

NT currently runs on a 386SX/20 with 8Mb, and we have booted the 
system in as little as 5Mb.  Since none of the working set tuning
has been done and our performance guru is a no-nonsense sort of
guy who has told me he is confident about the 8Mb number, 
I'd say >16Mb memory requirement was farcical.

Remember, 8Mb means 6Mb for the system and 2Mb for apps
without significant paging.  It doesn't mean the system will
barely boot in 8Mb.





-- 
-------------------------
My comments are my own.  They are independent and unrelated to the
views of my company , relatives or elected representatives.

Newsgroups: comp.os.ms-windows.programmer.win32
From: dwightm@microsoft.com (Dwight Matheny)
Subject: MS: New Windows NT DDK info
Date: 14 Oct 92 22:22:10 GMT
Organization: Microsoft
Keywords: DDK

Thanks to everyone who commented on our pricing/packaging plans 
for the Windows NT Preliminary DDK. In response to your requests 
we have decided to lower the price for the DDK, and offer a CD-only 
version of the product. Here's the new US pricing: 

	DDK CD-ROM only-			$69
	DDK CD-ROM with hard-copy documentation	$399

This pricing is consistent with our SDK pricing, and includes updates 
and the final version of the DDK. The documentation will be included 
on the CD in both Postscript and Write format, and all the device 
driver functions will be documented in Winhelp.

The DDK will be available before the end of November. If you are in 
the US and  currently own the Win32 SDK, you will be receiving a 
mailing on the DDK in mid-November which will include 4 page 
product datasheet, and an order coupon. We encourage you to order 
via this coupon since we are unable to keep up with extremely high 
call volumes the past few weeks. You will receive this coupon in 
plenty of time before the product ships.

International customers should contact their local MS office for 
ordering, pricing, and  availability information.

One other important change which you should be aware of. Everyone 
who purchases the hard-copy documentation for the DDK will receive 
the new book "Inside Windows NT" from MS Press. This book will 
not be on the CD.

Again, thanks for your feedback.

Dwight Matheny
Product Manager- SDKs and DDKs


Newsgroups: comp.os.ms-windows.programmer.win32