-=> Quoting Jean Parrot to Dan Ceppa <=-

 DC> As it is, I'm sorta running 3 versions of BW  One is 2.12, the one 
 DC> I use most often is 2.30 now.  But, I've been messing with 2.30/386 

 JP> You got me wondering. Should I not be in BW/386 as I run it from a
 JP> Windows setup ? Instead of BW/DOS ? The small qwirks that I suffer
 JP> might then go away. (???)

And you will run in to the BW/386 quirks. 

I copied the DOS4GW.EXE program into the C:\BWAVE directory so that 
BlueWave/386 wouldn't have to rely on it being in the PATH during 
startup. 

BW/386 loads it on startup, then unloads it when exiting. 

As I pointed out to Dan, you will HAVE to read the instructions in, 
and set the parameters in, the BWAVE386.VMC file. It controls more 
then the virtual swap file. It also controls how much RAM must be 
available before BW/386 is allowed to start and the maximum amount 
of RAM DOS4GW.EXE will make available for BW/386. 
I have mine set for 2048kb (2MB) MAXMEM, and have never run out of 
room. 
Back in the good old days, when people got their internet newsgroups 
on the BBSes, a HUMONGOUS message packet could require making that 
setting larger, or setting the VIRTUALSIZE larger then the MAXMEM 
so that excess swapped to a swap file on the hard drive (back when 
people only had maybe 4megs of RAM on a Win3.1 system). 

If you want to change anything in the BWAVE386.VMC it is recommended 
to make a backup first. 
I do this by copying the original to: BWAVE386.VM0

Bruce Clark 

 
___ Blue Wave/386 v2.30
--- Platinum Xpress/Win/WINServer v3.0pr5a