HDTenEightyP/NetNews huggingface dataset:
From: trs@tad.eds.com (Tim Steward)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: NTFS Security - Beware
Date: 29 Dec 92 19:03:14 GMT
Distribution: usa
Organization: EDS Technology Architecture, Dallas

I am using the October pre-release of NT.  As an experiment, I built an
NTFS partition to explore the security features.  As initialized, the 
ACL on all of the NT files reads Everyone (All)(All) OWNER CREATOR (None)(All)
giving any user full access to the system critical files.

It seemed to me that this was pretty insecure, so I decided to modify it.
At first, I simply changed the Everyone entry to Read Only.  When I logged off
and back on again, bad things seemed to happen.  I tried to go to the 
Permissions... window, but got an error dialog saying "Server not available".
I poked around some and tried to resolve the issue, but I was locked out of the
apps in the Administrative Tools group.  I tried to reboot and found that there
was a 0x00... bug report.  NT wouldn't come up.  I had to use OS/2 fdisk to 
trash the partition in order to recover so that I could reinstall NT (Ouch).

Being a glutten for punishment, I tried two more installs.  The first time I
changed Everyone to (Read)(Read) and OWNER CREATOR to (Full)(Full).  Same result.
The second time I made the same changes and then added Administrators (Full)(Full).
This worked and I can use NTFS without problems.

NOTES: I was logged on as the default Administrator account, which is a 
member of the Administrators group.  The OWNER CREATER of all files was 
listed as Administrators (I assume the group).  When I changed permissions,
I cascaded the changes to the entire drive.  The NT system directory was 
on the NTFS drive.
From: cnolan@vax1.tcd.ie
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Desperation : 0x0000000A ERROR
Date: 21 Dec 92 10:32:36 GMT
Organization: Trinity College Dublin

In article <1992Dec17.161642.12591@sol.ctr.columbia.edu>, dicks@cfsmo.honeywell.com (Richard D. Schlotfeldt) writes:
> Torsten Sturm (tnsturm@cip.informatik.uni-erlangen.de) wrote:
> : 
> : Now I'm near to desperation,
> : 
> : FATAL SYSTEM ERROR
> : 
> : *** 0x0000000A
> : 
> : *** IRQL expected to be less or equal
> 
> Since you are desperate I will give as many hints as I can,
> though I do not know the solution.
> 
> - Review Appendix B of Release Notes for clues
> - Remove any non-essential hardware from your machine until you
>   get it working
> - Get a newer AMI bios
> - Check for interrupt level conflicts
> - Slow down the computer
> - Slow down DMA rate
> - Change VGA to 8 bit
> - Wait for next version of SDK??
> 
> Others have experienced the dreaded 0x0000000A fault associated with:
> - WD card driver (8-bit Elite Plus)
> - WD8003EP card driver (ok if disable network support, unplug card)
> - Olivetti PWS4000 with built-in ethernet adaptor and TCP/IP software
>   crashes when running telnet
> - File manager says 8 SCSI cd-rom devices on an FD 845 SCSI adapter
>   but system actually has only one. Crashes upon select of ficticious
>   device.
> - My own problem was old bios and firmware on an Adaptec 1542B.
> 
> Some of the above reports were for the July release. Looks like
> there are various problems which can lead to this error message.
> 
> Anyone else have something to add??
> 
> Dick Schlotfeldt

Add to that list the NE2000 driver for me, 'tho others have got
this to work.  I have successfully used a WD8013 with the 8003EP
driver!!

-- 
===============================================================================
		Conor Nolan	(cnolan@tcd.ie)
	Microelectronics Dept. Trinity College, Dublin.  IRELAND.
===============================================================================
Newsgroups: comp.os.ms-windows.programmer.win32
From: philc@aruba.uucp (Phil Calvin)
Subject: Re: Porting X applications to NT/Win32
Date: Tue, 22 Dec 1992 18:33:24 GMT
Organization: Project Zed

In article <1992Dec22.013247.22651@microsoft.com> johnhall@microsoft.com (John Hall) writes:
>Windows 3.x certainly does, and I believe Windows NT will allow
>it as well though I'm not 100% certain.
>
>Try it.  Get a DC, pass to another process, and use it to draw
>on the original window.
>

Huh??

Doesn't that violate the NT security model??  I was under the
assumption that anything that was given to a particular process
was local to that process.

One of the examples I have seen is a direct contraction to your
statement.  (I believe it was at the GDI overview in the July 
rollout)

Phil

-- 
--------------------------------------------------------------------------
Phil Calvin                      |Internet Style: aruba!philc@uu2.psi.com
Systems Programming, Project Zed |UUCP: ...!uunet!uu2.psi.com!aruba!philc
--------------------------------------------------------------------------
Newsgroups: comp.os.ms-windows.programmer.win32
From: toreh@bootes.sds.no (Tore Haraldsen)
Subject: Problems running DOS apps under WNT
Organization: Statens Datasentral A/S, SDS, Norway
Date: Tue, 22 Dec 1992 13:17:08 GMT

I have WNT SDK/October installed on two machines, one with a large DOS
partition & NTFS partition, the other with an NTFS partition only.

On the one with both DOS & NTFS partitions I cannot execute DOS apps at
all, on the other DOS apps runs just fine.

What is wrong? How do I remedy it?

Config for both machines are AMI BIOS & motherboards & 16MB ram, 246Mb
IDE disks, 3C503/16 ethernet cards & ET4000 video.

-- tore
-- 
------------------------------------------------------------------------
Tore Haraldsen, Statens Datasentral A/S - SDS, Norway
email: toreh@bootes.sds.no
Newsgroups: comp.os.ms-windows.programmer.win32
From: alexism@ngc.com (Alexis Mermet)
Subject: New compiler/linker
Summary: New NT compiler/linker on compuserve
Keywords: compiler linker patch
Organization: Network General Corporation
Date: Wed, 23 Dec 1992 21:50:26 GMT

There is a new compiler and linker for the windows NT October beta release
on Compuserve.
However , it is more than 800000 bytes long and I cannot download it with a 
2400 bauds modem.

I know Microsoft does not provide support on INTERNET, but as a NT developper
I would like to get this new compiler/linker.

Could MICROSOFT be 'kind' enough to post it in this group, or maybe some 
developper out there, if MICROSOFT does not agree.

It seem to me that it does not make a lot of sense to only distribute such
huge fixes exclusively on Compuserve. There are still some 2400 bauds modem
out there!

Thanks a lot.
-- 
Alexis MERMET-GRANDFILLES		Voice: 415-617-2943
Software Engineer. R&D    		Fax:   415-321-0855
Network General Corp.
Newsgroups: comp.os.ms-windows.programmer.win32
From: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Subject: NT and OS/2 servers
News-Software: IBM OS/2 PM RN (NR/2) v0.16 by O. Vishnepolsky and R. Rogers
Reply-To: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Organization: Techn. Univ. Clausthal
Date: Sun, 3 Jan 1993 21:32:08 GMT

Has anyone managed to NET USE an NT drive from an OS/2 requester?

I am using LANMAN for NT on one machine and OS/2 1.30.1 with MS-LANMAN 2.1a
on the other machine. I can successfully NET USE an OS/2 drive from the NT
machine, but not vice versa.

The error, that occures is "SYS0082: The specified server cannot perform the
requested action". From DOS or Windows for Workgroups machines I can NET USE
from both NT and OS/2 servers.

Christoph
-------------------------------------------------------+-----------------------
Christoph H. Hochstaetter, Philipps-University Marburg | Universitaetsstr. 25
Internet: hochstae@allfiwib1.wiwi.uni-marburg.de       | D-W-3550 Marburg
Bitnet  : HOCHSTAE AT DMRHRZ11                         | Germany
Fido    : 2:243/660                                    | Phone +49-6421-28-7092
Fax     : +49-6421-28-4858                             |
From: swhall@eng.auburn.edu (Steven Wayne Hall)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Win NT Installation
Date: 21 Dec 92 21:01:28 GMT
Reply-To: swhall@eng.auburn.edu
Organization: Auburn University Engineering


I too am having difficulties installing NT.  I am getting a 0x00000006 error during 
installation.  Ih have to use the dos based install routine, and when it goes to
load the NT kernel, it gives me this error.  Can anyone help??
---

    +================================================================+
    | /* Steven W. Hall */  | A theory can be proved by experiment;  |
    | Computer Engineering  | but no path leads from experiment to   |
    | Auburn University, AL | the birth of a theory.		     |
    |  	       	            |					     |
    |swhall@eng.auburn.edu  | Albert Einstein (1879-1955)            |
    +================================================================+
Newsgroups: comp.os.ms-windows.programmer.win32
From: coffler@dbased.enet.dec.com (Jeff Coffler)
Subject: Re: Can the Python DAT driver in Win NT be used with a WangDAT?
Keywords: WangDAT
Reply-To: coffler@dbased.enet.dec.com (Jeff Coffler)
Organization: Digital Equipment Corporation, Nashua, NH
Distribution: comp
Date: Tue, 22 Dec 1992 14:40:39 GMT


In article <goyal.724982374@willow.cs.scarolina.edu>, goyal@cs.scarolina.edu (Sanjay Goyal) writes:

|>2. I have partitioned my hardrive with DOS/NT on first partition
|>and ISC 3.0 UNIX on second partition.
|>The Dos and NT operating system was installed a while back. And
|>Windows NT was installed on the DOS partition a few days back.
|>
|>When the system comes up and ISC Boot Manager asks me which partition
|>to boot from , and I select NT ... NT gives me a Fatal Error and hangs up!!
|>The only way to boot NT is to go into UNIX and make the first partition
|>active and then reboot the computer
|>
|>There is something strange going on here ... 

I've seen this one with DELL Unix as well.

From looking at the output from the NT Boot Loader, it appears that the NT boot
software assumes that NT is in the primary (active) paritition.  Thus, when it
isn't, it looks for stuff in the wrong place and gets mucho confused.

I boot off of a DOS diskette and change the active partition to my NT
partition, then boot NT.  When done, I reboot from the DOS diskette and
run fdisk to change the active partition back to the UNIX partition ...

--
Jeff Coffler				TCP/IP: coffler@dbased.nuo.dec.com
Database Systems Engineering		DECnet: DBASED::COFFLER
Digital Equipment Corporation		Voice:  1-603-884-1351
Nashua, New Hampshire			FAX:    1-603-884-0829

                {Disclaimer: What I say is my personal opinion}
From: muzo@waffle.sns.com (muzaffer kal)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: NT: Help!  Fatal System Error 0x00000069 during boot.
Date: 29 Dec 92 06:07:58 GMT
Organization: Systems'n'Software

Systems'n'Software, Fremont, CA  94539-6669
Date: Mon, 28 Dec 92 22:05:44 PST
Organization: Systems'n'Software, Fremont, CA  94539-6669

pss1@kepler.unh.edu (Paul S Secinaro) writes:

> 
> I need help getting NT to boot on my system.  I get the following
> error after the setup program finishes and the kernel begins to boot:
> 
> MS-Windows NT - Beta October 1992 [16064KB available mem]
> 
> *** Fatal System Error 0x00000069
> 
> *** Phase 1 I/O initialization failed
> 
> Kernel Debugger using COM1:
> 
> 
> 
> I'm using a Tri-Star 486/33 EISA system (Free Technologies motherboard
> w/AMI BIOS) with two SCSI Adapters - a DTC 3290HD EISA SCSI for the
> hard disk, and a Future Domain TMC-850MEX for the CD-ROM.  This
> combination works find under DOS, and the NT Setup program detects
> both adapters (it detects the DTC as an Adaptec 154x, which should be
> okay in theory.)
> 
> Appendix B of the Release Notes mentions something about possible
> address conflicts with the Future Domain controllers, but I've tried a
> few different combinations with no luck.  It does not appear to
> conflict with anything.
> 
> Does anyone have any ideas?  Could having two different SCSI
> controllers be causing a problem?
> 
> Thanks,
> 
> Paul
> -- 
> Paul Secinaro
> pss1@kepler.unh.edu
> Synthetic Vision and Pattern Analysis Laboratory
> UNH Dept. of Electrical and Computer Engineering

there is a NTFAQ on compuserve WINNT lib 1. I am not able to upload any
thing to this bbs where I read net news, sorry. I have seen error 69 in 
that faq.

hope this helps

Muzaffer

----
muzo@waffle.sns.com  (muzaffer kal)
Systems'n'Software Free Public Access BBS --- (510)623-8652
Newsgroups: comp.os.ms-windows.programmer.win32
From: RUESS_M@rzmain.rz.uni-ulm.de (Ruess Michael)
Subject: Re: NT Installation with WD8003E Ethernet
Organization: University of Ulm, Germany
Date: Sun, 3 Jan 1993 19:59:52 GMT
X-News-Reader: VMS NEWS 1.24

In <1993Jan3.182844.637@solaris.rz.tu-clausthal.de> hochstae@allfiwib1.wiwi.uni-marburg.de writes:


> Inport Mouse on IRQ2, Serial Ports on IRQs 3&4, NE2000 Ethernet card on
> IRQ5. This works fine for me and I don't have any problems. But be
> careful: Some (especially older) ET4000 cards always utilize IRQ2, which
> prevents other software using IRQ2.

I think it's a good choice using IRQ 5. The cause that WD8003-Installations
do not work are the default settings in the release notes: Base=0x0.

The configuration recommended is Base=0xa000 (yes ist works with NT).
Unfortunately the Base=0xd000 is not supported under NT (Why?).

Michael Ruess
University of Ulm, Germany
  
Newsgroups: comp.os.ms-windows.programmer.win32
From: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Subject: Re: NT server under OS/2 Domain?
News-Software: IBM OS/2 PM RN (NR/2) v0.16 by O. Vishnepolsky and R. Rogers
Reply-To: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Organization: Techn. Univ. Clausthal
Date: Sun, 3 Jan 1993 20:36:17 GMT

In <1993Jan3.194555.2959@wega.rz.uni-ulm.de> RUESS_M@rzmain.rz.uni-ulm.de (Ruess Michael) writes:
>In <1993Jan1.194142.9476@solaris.rz.tu-clausthal.de> hochstae@allfiwib1.wiwi.uni-marburg.de writes:
>
>[...] Stuff deleted
>
>
>> 1) You must have "LAN-Manager for Windows/NT" (the purple CD).
>> 2) The Primary Domain-Controller must be an NT machine.
>
>[...]
>
>
>> Christoph
>
>Christoph, this is not correct.
>First I use the normal NT (October beta) without LAN-Manager for NT and my
>Primary Domain-Controller is the OS/2 machine. The only restriction is that
>I cannot use the commmand NET LOGON on normal NT, this is only for
>LAN-Manager for NT.

The NET LOGON command is not available on the Lanman/NT SCS either, you
do this by normal GUI logon. I did not say, that you cannot NET USE
OS/2 drives from OS/2 servers on NT. The only thing is, that you cannot
setup a *SINGLE* domain of NT and OS/2 servers, when the primary DC is
an OS/2 machine.

Domains have identical sets of Users and Groups. This can be done in
a mixed OS/2 - NT domain only, if the primary DC is running under LAN
Manager for NT.

If there is enough interest here in this group (e-mail me), I will post a
short summary about LAN Manager for NT, differences between NT and
LAN Manager for NT and mixed domain containing OS/2 and NT servers.

Christoph
-------------------------------------------------------+-----------------------
Christoph H. Hochstaetter, Philipps-University Marburg | Universitaetsstr. 25
Internet: hochstae@allfiwib1.wiwi.uni-marburg.de       | D-W-3550 Marburg
Bitnet  : HOCHSTAE AT DMRHRZ11                         | Germany
Fido    : 2:243/660                                    | Phone +49-6421-28-7092
Fax     : +49-6421-28-4858                             |
Newsgroups: comp.os.ms-windows.programmer.win32
From: corne@aie.nl (Corne Brouwers)
Subject: Re: Date For January NT Drop?
Organization: AI Engineering BV, Amsterdam, Netherlands
Date: Tue, 22 Dec 1992 11:14:45 GMT

In article <1992Dec16.013430.7175@microsoft.com> dwightm@microsoft.com (Dwight Matheny) writes:
>We haven't announced dates for the next release of the SDK.
>
>
>-Dwight (MS)

But, then again the first non-pre-developpers release will by the end of this
year!
Read my lips!
(I for one will be very supprised if I get the October release before 93)


-- 
|	       Corne Brouwers, A.I. Engineering BV,  Amsterdam		      |
|   Domain: corne@aie.nl                               UUCP: corne@aie.UUCP   |
Newsgroups: comp.os.ms-windows.programmer.win32
From: johnhall@microsoft.com (John Hall)
Subject: Re: Multi-processors for NT
Date: 31 Dec 92 16:48:22 GMT
Organization: Microsoft Corporation
Keywords: multi-processor, NT, MP

In article karmira@natinst.com (Apostolos Karmirantzos) writes:
|   I am a developer for NT and I am looking to buy a multiprocessor (MP) 
| machine for NT development. But when I saw the prices I almost fainted :-). 

I've seen decent 3 x '486/33s for about $12,000.  You'd have to flip
through the compatibility list and ask each vendor.

|   Did the machine performed well? Does NT speedup at all? 

The ones in the lab do very well under load.  NT scales at about
a 90% efficiency.  Note the key is 'under load'.  An MP machine will
make something like a SqlSrvr DB scream, but not do a lot for your
compilers or editor.  They are also very good for testing device
drivers.

| How stable is NT under MP compared with a single processor machine. 

Less but close.  Note you can run the single processor NT on an MP
if necessary.

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

Xref: sparky comp.os.ms-windows.programmer.win32:2636 comp.os.ms-windows.misc:5849
From: tnsturm@cip.informatik.uni-erlangen.de (Torsten Sturm)
Newsgroups: comp.os.ms-windows.programmer.win32,comp.os.ms-windows.misc
Subject: Re: Help unistalling Windows NT
Date: Sat, 2 Jan 1993 11:28:13 GMT
Organization: CSD., University of Erlangen
NNTP-Posting-Host: faui00a.informatik.uni-erlangen.de

boot dos, and call fdisk the following way :

fdisk /mbr

which will install the master boot block, that fdiskj
has installed when you configured your disk last time .

Hope that helps !
Torsten

---
Torsten Sturm :	    Computer Science Department 
                    University of Erlangen-Nuremburg,  Germany

Internet :          tnsturm@immd4.informatik.uni-erlangen.de
                    ( tnsturm@immd8.informatik.uni-erlangen.de )
From: rogere@ogicse.ogi.edu (Roger Ellingson)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Installation adveNTures with NT
Keywords: Speedstar 24x, ET4000
Date: 2 Jan 93 19:09:24 GMT
Article-I.D.: ogicse.47888
Organization: Oregon Graduate Institute (formerly OGC), Beaverton, OR

In article <EBROWN.92Dec29120203@bud_light.kodak.com> ebrown@tap.kodak.com writes:
>
>The ET4000 drivers do work for the Diamond Speedstar 24. That
>is what I am using. However, you must boot DOS and run windows
>first and then Ctrl-Alt-Del and run NT. The problem is that NT
>does not sync the ET4000 clocks (or something like that). The
>DOS vmode or windows driver sets up the card somehow. It then
>works in NT.
>
I am interested in this subject but brand new to this newsgroup.
Could someone point me to where these et4000 drivers are located?
I think I have tried all et*.* sys and ts*.* dll files on both
July and Oct releases of NT and have not been able to get a 
24X to run at high res on Oct NT.

Are the correct drivers the Oct NT ET4000.sys drivers?
Is it still necessary to copy files to vga.sys and vga.dll?

Thank you for any help on this.

From: Randall.Adams@ttlg.UUCP (Randall Adams)
Sender: postmaster@ttlg.UUCP
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Windows NT October Beta
Date: 29 Dec 92  16:42:48 mst

Hello, I'm testing Windows NT, and was wondering if you want each update
you would have to buy a cdrom each month, or is there a upgrade disk or
disks that we can get. Also I'm using a Sony CDROM drive with a 40 Pin
Scsi which is not supported.  Does anyone plan to develop basic SCSI 
driver?  Also I have a Panasonic Worm drive that I would like to get a
driver for any ideas?
 
Lastly, where can I find an NT support BBS?

Randall Adams
Ultra Fast Systems BBS (403) 488-0657

   
 * WinQwk 2.0 a#0 * Unregistered Evaluation Copy

 * Origin: Alberta Express RBBS-PC (403) 471-6763 14.4 HST (42:100/41)
From: f88hv@efd.lth.se (Henrik Vallgren)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Problems with SCSI-controller and Windows NT
Date: 27 Dec 92 15:18:16 GMT
Reply-To: f88hv@efd.lth.se
Organization: Lund Institute of Technology, Sweden

Windows NT doesn't get along with my SCSI-controller, and I'd like
to know why and/or what I can do about it. I didn't ask before
since I hoped that the October version of Windows NT would have 
taken care of the problem.

I have the following setup:

  AMI Fastdisk controller (an EISA-based SCSI-2 controller)
  Seagate 1239N 200MB SCSI drive
  Toshiba 3301B CDROM drive (Windows NT compatible)
  The boot drive is an 80MB IDE drive with Windows NT installed.

The controller is Adaptec 154x compatible, and Windows NT detects
an Adaptec 1540 during setup. But it can't work with it. I have no
problems with dos and Windows 3.1.

With the July version, I had to use dos2nt to install NT. When
installation was complete, it got error 0x69 when I tried to
boot. I removed the scsi controller, and NT worked. I could then 
reinstall the scsi control and NT didn't look for it. I could never
access my d: drive (the 200MB scsi).

With the October version, installation was a bit easier. NT detected
my "Adaptec 1540" and proceeded to decide that I didn't have a NT
compatible CDROM drive. It installed the data it needed on my IDE
harddrive and then tried to reboot. Instead of getting error 0x69
NT now hangs. I reinstalled the data onto the harddrive, deleted
the Adaptec driver and NT would now install OK.

Neither of the above setups let's me access my d: drive. I don't care
much about the CDROM, but I really need to have more storage at hand.

-------------------------- Questions below --------------------------

Does anybody have an idea of what I might try to solve my
problem ? 

Is the problem due to that my harddrive is SCSI-1 ?

Could I trick NT into believing that my d: drive is an ordinary 
drive (the controler is WD 1003 compatible) ? 


Thanks for any help

Henrik Vallgren
f88hv@efd.lth.se
From: jeh@cmkrnl.com
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: NT Installation with WD8003E Ethernet
Date: 3 Jan 93 01:10:05 GMT
Organization: Kernel Mode Consulting, San Diego, CA

In article <1992Nov26.082015.21435@solaris.rz.tu-clausthal.de>, hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter) writes:
> In <1992Nov23.104029.19031@infocomm.com> mark@infocomm.com writes:
>>Has anyone gotten NT to install with the Western Digital 8003E Ethernet Card?
>>The installation goes along fine until the point where it "starts the network".
>>At this point, the cursor stops tracking and pressing the RESET button is
>>required to get any furthur action from the system.
>>
>>I've selected/configured IRQ=2, PORT=0x200 and Memory Base=0x0
>>       (As suggested on page 43 of the Release Notes)
>>
> 
> I personally can not recommend IRQ2. This leads to several problems in
> many cases, because of the "cascade" function of IRQ2. 

What are we supposed to do?  COM ports come set up to only use IRQ 3 and 4. 
If you want to be able to use both of them as serial ports (rather than using
one for a mouse), you need a bus mouse.  Microsoft's bus mouse can only be
used at IRQ 2, 3, 4, or 5.  Many Ethernet cards are similarly limited to 
2, 3, 4, or 5.  If I can't use IRQ 2, that effectively means that I can't have
two working serial ports.  

The combination of mouse at IRQ 2, serial ports on 3 and 4, and Ethernet card
on 5 works fine for me under DOS.  Can I expect problems with this under NT?
Could this be related to my NT system being unable to write to the floppy
drives?

	--- Jamie Hanrahan, Kernel Mode Consulting, San Diego CA
uucp 'g' protocol guru and release coordinator, VMSnet (DECUS uucp) W.G., and 
Chair, Programming and Internals Working Group, U.S. DECUS VMS Systems SIG 
Internet:  jeh@cmkrnl.com, hanrahan@eisner.decus.org, or jeh@crash.cts.com
Uucp:  ...{crash,eisner,uunet}!cmkrnl!jeh
Newsgroups: comp.os.ms-windows.programmer.win32