Well, for what it's worth included in this archive are my OS/2 Warp
config.sys, autoexec.bat, system.ini, and win.ini files.  This setup allows
me to run NDW 3.0/WFWGroups over OS/2 Warp.  Here is some basic info in 
case you need it:

System Info:  Gateway P5-90 Pentium, 16MB ram, Soundscape Soundcard, Supra 
Modem on COM1, Mouse on COM2.

OS/2 Info:  OS/2 refuses to recognize my soundcard.  I run a program called
Seamless Windows (look for it under seamwin3.zip) in my startup folder 
which basically fulfills the same functions as the Fastload option in Warp. 
It preloads a dummy inactive session of Windows to allow fast loading of 
later Windows apps.  I have found, through limited unscientific testing, 
that it works better than Fastload.  See for yourself.  I load Seamless 
Windows in Enhanced mode in a windowed setting (i.e. not Fullscreen).  All 
my other windows applications are set to run in Enhanced/Windows mode, 
including Norton Desktop.  All Windows applications with these 
settings will load on top of the Seamless windows session and inherit its 
settings (at least it appears to me that OS/2 is setting things up this 
way).

First caution.  When you load NDW in this fashion it will not paint the
Windows bitmap on top of the OS/2 screen.  Instead it will merely draw all 
the Norton icons and drives etc.  If you don't like this you can load NDW 
as a full screen application.  The drawback to this is the longer load 
time.  I have found that it works for me either way.

Second caution:  Sound card interrupt conflicts will bring the system down 
every time.  That is to say, the first Windows application that loads will
grab your soundcard and lock onto it.  If you load another Windows 
application on top of the first (i.e. you don't set it up to full screen 
and/or it has the same enhanced/standard mode as the first) everything is 
fine sound wise.  However, if another instance of Windows is loaded, this 
second instance will try to grab the soundcard and find it in use.  Weird 
things happen at this point which will almost certainly lead to a crash. 
If you want to prevent this you can just disable sound in Windows.  There 
may be other ways around this but, at this point, I'm clueless.

Given the above constraints, NDW 3.0 seems to work fine.  I have not 
extensively tested it but I have loaded many of my applications and they 
appear to load fine and function normally (Word 6.0, Excel 5.0, Quicken, 
among others).  The NDW 3.0 file manager seems to work just fine also.  The
only problem I have noticed is that there is an error
message at startup from NDW telling you that symevnt.386 is not installed. 
I would imagine that is is some sort of driver/handler that OS/2 removed 
from one of the ini files.  Whatever it controlled is presumably now 
controlled by OS/2.  Again, I'm clueless here.

I hope this helps.  If you have any questions you may contact me on 
Compuserve (75226,1266) or at charlie392@aol.com.

Good luck... Charlie
