HDTenEightyP/NetNews huggingface dataset:
From: sammy@anagld.analytics.com (Sam Blackburn)
Newsgroups: comp.os.ms-windows.programmer.misc
Subject: Re: Dialog instance data...
Date: 10 Nov 92 01:15:37 GMT
Distribution: na
Organization: Computer Sciences Corporation - Systems Engineering Division

carty@ists.ists.ca (Ed Carty) writes:


>9 Nov. 1992

>Anyone walked this road before...
>I'd like to encapsulate instance data with a modeless dialog.  I'm creating
>the dialog with CreateDialogParam(), passing initialization data via the
>lParam.

Are you passing a handle to a data structure?  If so you can simply put a
property on the dialogbox window.

SetProp( dialog_box_handle, "Instance Data", instance_data_handle );
and to retrieve it:
instance_data_handle = GetProp( dialog_box_handle, "Instance Data" );

Properties are a great (and portable) way of holding per-instance or global
data.  They work especially well with data striuctures that are GlobalAlloc'd.

Hope This Helps . . .

sammy@sed.csc.com
Newsgroups: comp.os.ms-windows.programmer.misc
From: "Stephen Guthrie" <guthrie@moose.cs.indiana.edu>
Subject: clipboard and bitmaps
Organization: Indiana University, Bloomington
Date: Tue, 10 Nov 1992 12:58:08 -0500

I am trying to save a bitmap that is on the clipboard to a .bmp file
Does anyone have any sample code showing how to do this, or some 
hints to get me pointed in the right direction?  Any help is 
greatly appreciated!!

Thanks,
Steve
From: tad@wrq.com (Tad Marshall)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Changing login Screen.... How?
Date: 5 Nov 92 05:30:04 GMT
Distribution: usa
Organization: Walker Richer & Quinn, Inc., Seattle, WA

In article <1992Nov5.010416.23447@ncsu.edu> jmsmith@eos.ncsu.edu (JEFFREY MARTIN SMITH) writes:
>How does one go about changing the colors of the login screen of Win NT
>Oct beta?
>
>I thought it was the Administrator Color scheme but I was wrong...

I asked this question of several Microsoft people at the Device Driver
Conference and no one knew, but I eventually figured it out.

Run REGEDIT and go to HKEY_USERS\.DEFAULT\Control Panel\Colors and change
the color values by hand.  You can also edit ~\Desktop to change screen
saver parameters.

There should be a cleaner GUI way to do this, but this makes it possible.

-- Tad
Newsgroups: comp.os.ms-windows.programmer.win32
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: Mail on NT:  What, and when?
Date: 09 Nov 92 07:11:04 GMT
Organization: Microsoft Corporation
Keywords: NT, mail, TCP/IP, Unix

In article <Bx4FDI.GBG@world.std.com> digilab@world.std.com (BioRad Digilab) writes:
>Has anyone here had the guts to try a port
>of sendmail, or something crazy like that?

I saw a port of uucp & sendmail working on the july sdk - I'm not sure
where it came from, but it was working, if not 100%, then 90%+
working. If you'd like to take the sources and volunteer some time
to get them to 99%+, then I'm sure the pd-tools@microsoft.com
alias would like to hear from you. They're collecting public
domain ports from all over the place, and will take more, and more
help, anytime! -- Alistair
Newsgroups: comp.os.ms-windows.programmer.win32
From: beame@maccs.dcss.mcmaster.ca (Carl Beame)
Subject: DuplicateHandle -- passing handles to other processes
Organization: Beame & Whiteside Software Ltd.
Date: Mon, 9 Nov 1992 16:31:58 GMT

Forgive me if this has already been answered ... but ...

I am trying to pass a handle to a named pipe to a process which I have just
created. After reading the docs :-), I called DuplicateHandle with 
the GetCurrentProcess() as the source process handle, the handle returned
to me from the create process call as the destination handle and
the pipe as the handle to duplicate. The call returned TRUE and filled in
the new handle ... I passed this new handle to the new process via another
named pipe ... Using the new handle in the created proceedure fails.

Help ... What am I doing wrong ... (if anything :-) ).

- Carl Beame
beame@bws.com
Newsgroups: comp.os.ms-windows.programmer.win32
From: joiner@exa.cs.umn.edu (Jay K. Joiner)
Subject: Re: GCC
Organization: University of Minnesota
Distribution: comp
Date: Sun, 8 Nov 1992 03:22:08 GMT

In <BxBvG3.MG@huey.jpl.nasa.gov> brad@huey.Jpl.Nasa.GOV (Brad Hines) writes:

>There is a port of GCC to OS/2, so in theory it should be able to run under
>NT.  However, there is a problem (one which I have had with a number of
>OS/2 character-mode programs), in that many OS/2 programs (and I'm pretty
>sure I recall that GCC is one of them) check first to see whether
>you're trying to run them in an OS/2 DOS box instead of an OS/2 command
>prompt window.  If you are, they say "This program cannot be run in
>DOS mode".  Such a program, when run under NT, prints out this message
>and then terminates.  I'm going to complain about this on CI$ this
>weekend to see what they say about it.

I was under the impression that NT only supported OS/2 1.x binaries,
i.e., 16-bit.  GCC is a 2.0 (32-bit) app.

From: darrylo@hpnmdla.sr.hp.com (Darryl Okahata)
Date: Wed, 4 Nov 1992 18:22:53 GMT
Subject: Re: October Release - some problems
Organization: Center for Primal Scream Therapy
Newsgroups: comp.os.ms-windows.programmer.win32

In comp.os.ms-windows.programmer.win32, mike-b@hpfcso.FC.HP.COM (Michael Bishop) writes:

> Well, I found a halfway solution to this problem.  After booting NT, go
> into the control panel and select "drivers".  Add the Creative Labs
> Soundblaster driver.  After selecting an appropriate port address (e.g.,
> 220 hex), and an IRQ (e.g., 5), press (Done/Ok).  You will get an error
> saying that this hardware is not installed on your system - ignore it.
> The driver still gets installed.  Now exit Windows NT and boot DOS (but
> not Windows 3.1).  This will initialize the MediaVision Soundcard -
> assuming you are loading the mvsound.sys driver in CONFIG.SYS.  Now
> reboot Windows NT, and voila!  - the soundcard will work!

     I believe Media Vision has released some beta NT drivers for the
PAS16, although it may only be SoundBlaster emulation support.  It's
available from Media Vision's support library on CompuServe.

     -- Darryl Okahata
	Internet: darrylo@sr.hp.com

DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion or policy of Hewlett-Packard or of the
little green men that have been following him all day.
Newsgroups: comp.os.ms-windows.programmer.win32
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: Getting DOS TCP/IP software to work with NT
Date: 09 Nov 92 07:35:34 GMT
Organization: Microsoft Corporation

>>In article <1992Nov5.031150.12271@ucsu.Colorado.EDU> ushomirs@spot.Colorado.EDU (USHOMIRSKIY GRIGORIY) writes:
>>
>>   I remeber reading here that Win NT's network drivers are similar to NDIS.
>>   In this case it seems to be easy to get any dos TCP/IP software that uses
>>   packet drivers or NDIS to work with NT.

Windows NT has a very distinct "user-mode" and "kernel-mode" - apps are run
in user-mode, and can't use kernel-mode APIs, and drivers are written in
kernel-mode.

The NDIS 3 interface in Windows NT is a kernel-mode interface to support
network interface cards. Generally, network transports are written as
drivers, and therefore interface with the NDIS 3 layer, and export an
interface called "TDI". TDI is also a kernel interface - network file
systems interface to TDI, and themselves are most often written as
kernel-mode services.

Windows Sockets, named pipes, netbios, Remote Procedure Calls, are all
user-mode network IPC mechanisms. Applications would choose to write
to one of these.

The only interface between user-mode and kernel-mode is an ioctl-style
interface (very unfriendly) - so we provide a bunch of "friendly"
code between TDI and an appication, which live inside the Windows
Sockets implementation. We believe that Windows Sockets will in fact
be useable for more transports that tcp/ip under Windows NT, and
are hoping to match ipx/spx and appletalk and others.

The Windows Sockets API may not be a perfect match for all the
esoteric functionality of each peculiar transport, but it is
enough for everyday applications which require common network
functionality.

If some specific unique functinality of a new trasnport is
required, then some more "easy glue" needs to be written by
that vendor between the kernel-mode TDI & user-mode.

Windows NT includes netbeui & tcp/ip trasnports - We've demoed
most SNA transports on Windows NT now, also appletalk. DEC are
working on DECNet, and various vendors are starting OSI work.

Good transports are hard to write - we hope we've got most
coverred

If you want to do the kind of direct-interfacing to NDIS 3
drivers, then you'll need the Windows NT Device Driver Kit, and
you'll wish you'd just have been to the big DDK conference in
Aneheim -- Alistair
-- Alistair
From: sasdxk@skyhawk.unx.sas.com (Dave Kolb)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: How do I load mep online help?
Date: 5 Nov 92 15:31:14 GMT
Article-I.D.: unx.Bx91s2.AID
Organization: SAS Institute Inc.
Originator: sasdxk@skyhawk.unx.sas.com


In article <1992Nov5.092123.26141@netcom.com>, erc@netcom.com (Eric Smith) writes:
|> In article <1992Nov4.140648.29322@rsd0.rsd.dl.nec.com> dave@rsd.dl.nec.com (Dave Rogers) writes:
|> >In article <1992Nov3.172049.9720@netcom.com>, erc@netcom.com (Eric Smith) writes:
...
|> >You must set INIT to \mstools\init or where ever you put the tools.ini
|> >file for your system.
|>
|> Thanks, that was the problem.

Is there a way to globally do this for all users?  The best I've seen
is editing the set variables via control panel/systsem icon for each
user individually after they log on.

Seems like the July release used to have this alread set.
-- 
Dave Kolb                     Opinions are mine not SAS'
SAS Institute, Inc.           EMAIL:      sasdxk@unx.sas.com
SAS Campus Drive - J206       Phone:      (919) 677-8000 x6827
Cary, NC  27513-2414 USA      FAX:        (919) 677-8123
Newsgroups: comp.os.ms-windows.programmer.win32
From: jody@shell.com (Jody Winston)
Subject: GCC
Organization: Shell Development Company, Bellaire Research Center, Houston, TX
Distribution: comp
Date: 5 Nov 92 08:26:01

Has anyone ported gcc to run on NT?  If not, is there documentation on
Microsoft's compiler input format or the object file format and the
executable format?

--
Joseph Winston		jody@shell.com
...!{sun,psuvax1,bcm,rice,decwrl,cs.utexas.edu}!shell!jody
Consultant to:
Shell Development Company, Bellaire Research Center
P.O. Box 481, Room 4205, Houston, TX 77001	(Voice: 713 245-7574)
From: tad@wrq.com (Tad Marshall)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: hostnames
Date: 5 Nov 92 05:10:59 GMT
Article-I.D.: u.1992Nov5.051059.26200
Organization: Walker Richer & Quinn, Inc., Seattle, WA

In article <Bx74ns.FAA@unx.sas.com> sasdxk@skyhawk.unx.sas.com (Dave Kolb) writes:
>
>In the July release one had to run regedit to remove the leading zeroes
>from the name server addresses because of a control panel bug.
>
>Has this been fixed in the Oct release?

Yes, the Connectivity dialog no longer adds leading zeros to nameserver
addresses.  Thank you, Microsoft.
Newsgroups: comp.os.ms-windows.programmer.win32
From: brad@huey.Jpl.Nasa.GOV (Brad Hines)
Subject: Re: GCC
Reply-To: brad@huey.Jpl.Nasa.GOV
Organization: JPL Spatial Interferometry Group
Distribution: comp
Date: Sat, 7 Nov 1992 04:07:15 GMT

>In article <JODY.92Nov5082601@colorado.shell.com>, jody@shell.com (Jody Winston) writes:
>Has anyone ported gcc to run on NT?  If not, is there documentation on
>Microsoft's compiler input format or the object file format and the
>executable format?


There is a port of GCC to OS/2, so in theory it should be able to run under
NT.  However, there is a problem (one which I have had with a number of
OS/2 character-mode programs), in that many OS/2 programs (and I'm pretty
sure I recall that GCC is one of them) check first to see whether
you're trying to run them in an OS/2 DOS box instead of an OS/2 command
prompt window.  If you are, they say "This program cannot be run in
DOS mode".  Such a program, when run under NT, prints out this message
and then terminates.  I'm going to complain about this on CI$ this
weekend to see what they say about it.

In theory, if we can get past that point, it should work as-is, I think.
Gnu Emacs has also been ported to OS/2, but it won't work under NT yet
because it uses ANSI screen-control sequences, which NT doesn't support
yet.


-- 
Brad Hines
Internet: brad@huey.jpl.nasa.gov
Jet Propulsion Lab, Pasadena, California
Newsgroups: comp.os.ms-windows.programmer.win32
From: johnhall@microsoft.com (John Hall)
Subject: Re: Thread signalling and ERROR_INTERRUPT (shades of OS2 1.3)
Date: 09 Nov 92 21:53:57 GMT
Organization: Microsoft Corporation

In article sasdxk@skyhawk.unx.sas.com (Dave Kolb) writes:
| Is there any concept of the OS/2 ERROR_INTERRUPT return code for
| Windows NT WIN32 calls made into a blocking system call by a thread?

No.

| If not, how can you "wake up" a thread in a multi-threaded application
| that happens to be blocked in a system call such as a Windows SOCKET
| or 3270 HLLAPI call?  Blowing away the thread is not an option.
| Nor can a list of semaphores be waited on instead.

The best way to do this is to have your thread wait on multiple
objects with 'ANY' meaning only one has to be signaled for the
wait to complete.

Then, you just do a SetEvent() or some such if you want 
the attention of that thread.

Signals that interrupt system calls are not supported in Windows
NT.  Nor are cross-process signals.  The NT designers do not think
that the Unix model (any system call may be interrupted at any
time by a signal) is they way to right good, robust systems.





-- 
-------------------------
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: jagrant@emr1.emr.ca (John Grant)
Subject: Re: Does Borland plan to support NT on non-X86 archtectures?
Organization: Energy, Mines, and Resources, Ottawa
Date: Thu, 12 Nov 1992 18:00:49 GMT

In article <5600@krafla.rhi.hi.is> karlth@rhi.hi.is (Karl Thoroddsen) writes:
>In <1992Nov12.023730.1101@mnemosyne.cs.du.edu> ebergman@nyx.cs.du.edu (Eric Bergman-Terrell) writes:
>
>>In article <BxKCIC.5KE@undergrad.math.waterloo.edu> hjhoffma@cayley.uwaterloo.ca (henning hoffmann) writes:
>
>>Many of us are also wondering what Borland's commitment to NT on Intel
>>silicon.  When can we expect a compiler supporting (minimally) WIN32S?
>
>>Terrell
>
>Borland is working on both NT & OS/2 compilers.  I would guess that their 
>development priorities have by now shifted from OS/2 over to NT so we
>should be able to get our hands on a NT & WIN32S compiler possibly in the
>first half of '93.
>
>Ciao.


I understand that the NT compiler is available now under their EEP program
(Early Experience Program).  I guess that means 'beta'?  On Compu$erve, they
have also been talking about it being officially available 12 weeks after
the official release of NT.  That has been repeated many times and has many
people somewhat upset.  I wonder if that magic 12 weeks has something to do
with their QA program or licensing rules for some MS stuff.

They also say that OWL programs will just have to be re-compiled - everything
widens to 32 bits (just like the API).  Apparently the same is true for OWL
on OS/2.
-- 
John A. Grant						jagrant@emr1.emr.ca
Airborne Geophysics
Geological Survey of Canada, Ottawa
Newsgroups: comp.os.ms-windows.programmer.win32
From: hjhoffma@cayley.uwaterloo.ca (henning hoffmann)
Subject: Does Borland plan to support NT on non-X86 archtectures?
Originator: hjhoffma@cayley.uwaterloo.ca
Organization: University of Waterloo
Date: Wed, 11 Nov 1992 17:56:35 GMT

That is, will Borland add suppoer to their C++ compiler to produce
Windows NT code for running under MIPS, DEC's RISC (what's its name?),
and PS-RISC (still not sure of NT support) ??

Thanks

H Hoffmann
From: edwardm@hpcuhe.cup.hp.com (Edward McClanahan)
Date: Thu, 5 Nov 1992 01:38:02 GMT
Subject: Re: ATI ultra drivers
Organization: Hewlett Packard, Cupertino
Newsgroups: comp.os.ms-windows.programmer.win32

Jerry Schneider writes:

> Today, I feel like one of those fools who bought a top-of-the-line
> product from DAK, only to find out that the reason it was such a
> "bargain" was because it was not compatible with anything else, and
> no longer supported by the manufacturer.

> After carefully reading (and then desperately re-reading) the list
> of supported hardware for the October NT release, I was dismayed
> to find there was no 8514 support, and in particular no ATI Ultra
> drivers.  Gosh, I bought the ATI card because it was a superset of
> the 8514 hardware, and even though I knew that ATI had a lousy reputation
> for delivering drivers for their products, I just _knew_ that the
> 8514 was going to be supported by Microsoft.

> The MS NT announcement suggests that 8514 and ATI support will be
> available "some time in the future".  From this, I can only assume that
> they are not developing drivers in house, but instead, are waiting
> for ATI to supply them.  This sounds a lot like Microsoft's earlier
> philosophy about letting each printer manufacturer write their own
> drivers for Win2.0.  After a year of sparse printer support, buggy
> third-party drivers, and howls of laughter and complaints from end
> users, the Win3 group decided that they must write drivers for the
> "main stream" peripherals.

> ...

Did you notice that the Oct'92 H/W Compatibility List included
the Gateway DX2/66V - a 66MHz DX2 system with VESA Local Bus
and the new ATI Mach 32 Ultra Pro VL-Bus card?  Does this mean
that NT must use a lowly 640x480 VGA-compatible mode on the
ATI card?  I recall that the old (Mach 8) Graphics Ultra had
(added to the 8514 Ultra) a 640x480 VGA compatibility mode.  I
didn't know that the new Ultra Pro had this same support...
Xref: sparky comp.os.ms-windows.programmer.win32:1846 comp.os.ms-windows.misc:4413 comp.os.ms-windows.programmer.misc:3279 misc.forsale.computers:39462
From: tad@wrq.com (Tad Marshall)
Newsgroups: comp.os.ms-windows.programmer.win32,comp.os.ms-windows.misc,comp.os.ms-windows.programmer.misc,misc.forsale.computers
Subject: Re: HELP ME!!!
Date: 7 Nov 92 00:12:55 GMT
Article-I.D.: u.1992Nov7.001255.1896
Distribution: usa
Organization: Walker Richer & Quinn, Inc., Seattle, WA

In article <Nov04.224920.52591@yuma.ACNS.ColoState.EDU> kyoder@lamar.ColoState.EDU (Kenneth Yoder) writes:
>In article <1992Nov4.162950.12374@eng.ufl.edu> jason@hal.eel.ufl.edu (Jason Nadrowski) writes:
>>Is this possible?
>>
>>Can I have a triboot feature where NT,OS/2,&DOS are chosen at power on
>>and thus pick either of the three to go into?  If so how?
>
>I want to do the same thing (great for comparing features, speed, etc.).  I 
>know OS2 allows for multiple boot partitions, but will NT work with this.  I 
>would guess there are others out there with the same idea so posts to the net 
>would be great.

Here's one method that worked for me.  I installed DOS and Windows onto an
empty partition.  I installed OS/2 over this as a same-partition install
(I think IBM calls this DualBoot) -- this is the method that does not involve
extra partions, but requires to choose your next operating system WHEN YOU
SHUT DOWN instead of when you boot.  This resulted in BOOT.DOS and BOOT.OS2
files being created, containing the DOS and OS/2 boot sectors.

I then booted into DOS and installed NT.  This copied the DOS boot sector to
BOOTSECT.DOS and replaced the physical boot sector with an NT boot sector.  I
then used debug to grab a copy of the NT boot sector (debug;l cs:100 2 0 1;
rcx 200;nboot.nt;w), and copied the resulting file over the BOOT.DOS file.

When I next boot up, if set for OS/2 I boot into OS/2; if set for DOS, I boot
up into the NT boot loader, which lets me choose between DOS and NT.

Others may have more clever methods, but this one works for me.

-- Tad
From: sasdxk@skyhawk.unx.sas.com (Dave Kolb)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Object Manager Namespace and Files
Date: 5 Nov 92 16:01:56 GMT
Article-I.D.: unx.Bx9378.Cpn
Organization: SAS Institute Inc.
Originator: sasdxk@skyhawk.unx.sas.com


Anyone know of a way to use the Object Manager Namespace to eliminate
the need for switch entering in a drive letter?

E.G. To be able to:

- "cd \Device\HardDisk0\mydir" instead of "d:" and "cd mydir".

- or to open a file "\Device\HardDisk0\mydir"

- or even better yet have the symbolic link capability to equate
  "\mydir" to a specific drive and path.

The File System Namespace uses A:, B:, C: etc. drive names as symbolic
links internally but I can't seem to take advantage of this fact from
the command line with "cd" or "dir" commands.

Is it possible using OpenFile?  Or does the File System just short
circuit the global name space and start it's root at the level of the
File System Namespace.

What I'm looking for here is something akin to the old DOS "join" or
Unix "mount" command where the size and number of physical drives in
your system can be transparent.  A lot easier for users and apps to
deal with.

How about it Microsoft?  If you expose some more symbolic link
capability to the user this seems like it would be possible and
very user friendly.
-- 
Dave Kolb                     Opinions are mine not SAS'
SAS Institute, Inc.           EMAIL:      sasdxk@unx.sas.com
SAS Campus Drive - J206       Phone:      (919) 677-8000 x6827
Cary, NC  27513-2414 USA      FAX:        (919) 677-8123
Newsgroups: comp.os.ms-windows.programmer.win32
From: jkf@Franz.COM (Sean Foderaro)
Subject: Re: S3 Pprobles [was Re: ATI ultra drivers]
Organization: Franz Inc., Berkeley, CA
	<1992Oct30.040110.8153@u.washington.edu>
	<1992Oct31.185237.28717@leela.cs.orst.edu> <lg7gjaINN3q8@news.bbn.com>
Date: Fri, 13 Nov 1992 21:31:11 GMT


>>      I have a greater concern. When I switched to 1024x768 I could no longer
>> see anything. Since the NT setup is 100% graphical I had no choice than
>> reinstalling ALL of NT.

 I had this problem too but rather than reinstalling NT I just booted dos,
found the et4000 driver file in the nt drivers area and copied the vga driver
on top of it and rebooted nt.  viola, it was now running in vga mode.

Newsgroups: comp.os.ms-windows.programmer.win32
From: jagrant@emr1.emr.ca (John Grant)
Subject: NT console mode?
Organization: Energy, Mines, and Resources, Ottawa
Date: Thu, 5 Nov 1992 05:52:16 GMT

I don't have NT and will wait until it's released, but I've been listening
in on all of the (interesting) conversations here.  I've overheard some
discussion of console mode.  Could someone give me a brief description of
this console mode? Is it initiated much like a DOS session is initiated from
Windows 3.1 or is it an option for booting, i.e. can you just boot up in
console mode and later run the GUI if you wish.  Is it a suitable environment
for porting large FORTRAN character-based apps from systems like VAXes?

John A. Grant
Geological Survey of Canada
Newsgroups: comp.os.ms-windows.programmer.win32