Xref: utzoo comp.sys.ibm.pc:52581 comp.windows.ms:2839
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!elroy.jpl.nasa.gov!decwrl!shlump.nac.dec.com!hpspwr.enet.dec.com!simon
From: simon@hpspwr.enet.dec.com (Curiosier and curiosier...)
Newsgroups: comp.sys.ibm.pc,comp.windows.ms
Subject: Re: RE problems with Windows/Disk Manager....
Message-ID: <12558@shlump.nac.dec.com>
Date: 15 Jun 90 18:40:17 GMT
Sender: newsdaemon@shlump.nac.dec.com
Followup-To: comp.sys.ibm.pc
Distribution: usa
Organization: Digital Equipment Corporation
Lines: 25


In article <55253@microsoft.UUCP>, philba@microsoft.UUCP (Phil BARRETT) writes...
>In article <4aff1a12.20b6d@apollo.HP.COM> nelson_p@apollo.HP.COM (Peter Nelson) writes:

>>   I do have a question.  Since Windows can apparently detect "known
>>   incompatibility" (1st paragraph, above) does it tell you when it
>>   finds such an incompatibility?  
> 
>Since it refuses to create a permanent swapfile,  it kind of figures
>that it gives you a message.  It says (from memory so dont nitpick)
>something like -- incompatible device driver foo in config.sys.

The message unfortumately does not state what device is incompatible.  
You have to figure it out on your own.  My config.sys is not that big, 
it didn't take me long to find out that Windows didn't like Speedstor's 
HarDisk.sys.  The HarDisk.sys was also the reason why Windows refused to 
see any partition of the disk beyond C: while scanning the disk for the 
applications.  Removing HarDisk.sys and re-partitioning with FDISK fixed 
the problem.

---------
Leo Simon			simon@pwrvax.enet.dec.com

Who is not liberal when young, does not have a heart.
Who is not conservative when old, does not have a brain.