CB> CB>    Having some strange goings on here since installing FP#3, on
CB> CB> boot I'm getting a "VW32S.SYS" not a valid device in the
CB> CB> config.sys but it points to lines other than the VW32S.SYS line. Any
CB> CB> ideas?
CB> 
CB>  WH> Sounds like time for some 'REM' entries til the bugger is found....
CB> 
CB> It seems to be related to the vdos*.*, etc.. entries.  I tried to
CB> overwrite the VW32S.SYS and got the "file in use" message.
CB> 
Hmmm... I got into this rat race with (I think) Warp 3 Red when it
first came out.  Even after the boot completed I could NOT open a DOS
or WinOS2 session.  Trying it gave me and 'out of memory' or some such
message box.  Turned out to be one of the vdos---.sys modules was
crashing during the boot and it tied up the whole subsystem.  I started
rem'ing out the vdos---.sys entries in Config.sys one at a time til I
got thru.  I'd strongly suspect the line immediately preceeding the
VW32S.SYS entry - as good a place to start as any!
You might also check you Config.sys file with a different editor just
in case there is a screwy character there that's fouling things up. 
Had this happen once also - talk about hard to find!!
CB> What I failed to mention, and should have initially, is that I 
CB> reinstalled 4.0 and put FP3 on top of that.  When I did the FP3
CB> over FP1 everything (including NS/2) worked fine but the system was
CB> running slow. 
AH! That is a critical point - all my machines were at the FP1 level. 
As to speed, I see no perceptible change, but on a DX2/66, 32 meg what
can I expect??
--- Maximus/2 3.01
1:128/166)
---------------