🚀 go-pugleaf

> Perhaps you can answer a question for me.  As I understand it, the
> settings you refer to in Win95 apply system-wide, is that the case?  To
> me, that seems like an unacceptable limitation.  With OS/2, I can
> tailor the settings for each program individually.  
> 
> Now, let's say that I want to run a DOS game that likes FILES=50.  In
> OS/2, I simply change the game's settings to boost the files for that
> session -- then, whenever I run the game, it uses FILES=50 and then drops
> back to my system default (FILES=20) when I exit the game.  Why should I
> penalize all my other tasks just for the sake of that one program by
> increasing my system-wide FILES statement?  How does Win95 handle this
> example?  From what I understand, it would require that I use FILES=50
> system-wide or reboot into another configuration -- is that correct?  If
> so, it doesn't seem like much of an improvement over what many people
> currently do in DOS. 
> 
Win 95 has the same capability.  All you need to do is click on the icon 
of the program with the right mouse button and select "properties" from 
that option a slew of possibilities for the individual configuration of 
that program come into play.  Setting the exact amount of Conventional 
memory, extended, expanded, etc.  Or just leave it on Auto, and let the 
OS figure the stuff out for you (works most of the time).  You can also 
set the configuration of the mouse driver, soundboard, etc if you are 
going to have the dos program load in a Dos only environment.  In that 
case the system reboots only to that program in a Dos session (with the 
exact configuration you specified).  Uppon exiting the program, the 
computer reboots again (this may take some time depending on your system) 
and reloads Win 95 exactly the way you left it.  It warns you that it 
will close other applications though.