🚀 go-pugleaf

In article <3n4rkl$g...@taco.cc.ncsu.edu>, jlwo...@unity.ncsu.edu (Jeffrey Lee Woodall) writes:
|> Mark R. Johnson (m...@knapp24.res.iastate.edu) wrote:
|> : In article <3n3j7a$12...@bubba.ucc.okstate.edu>,
|> : root <ro...@wentz1.reslife.okstate.edu> wrote:
|> 
|> : >Hahhaha, I can sniff a OS/2 zealot from a mile away.  Yup, you can run 
|> : >separate DOS sessions with specified or automatically allocated EMS, XMS, or 
|> : >DPMI memory, different environment size, configurable conventional memory 
|> : >amount, separate autoexec.bat and config.sys for each dos app.
|> 
|> : OS/2 has been doing all this since 2.0
|> 
|> Automaticly adjusting memory per app as required? Dont think so.

Whether you think so or not, it does it. What you set up is the maximum
RAM the session can get. It gets memory as needed up to that limit

|> 
|> : >It's really cool to be able to run DOS games in a window and stuff, although 
|> : >I prefer to switch to full-screen with a quick alt-enter.  The really cool 
|> : >stuff, though, is gonna be the crop of new games optimized for Win95 using 
|> : >the WING libraries.  I really couldn't live without the backward 
|> : >compatibility offered by Win95 for both Windows apps and dos apps (read: 
|> : >games ;) and I'd guess that most gamers would feel the same way.
|> 
|> : Gee, OS/2 does all this now, has been doing it for years, and will 
|> : continue to do it.  Get a clue.
|> 
|> But not as well.  YOU get a clue.

It does it as well, what you get is a Win95 shutdown which ends in a DOS
session (as via dualboot) and when you exit the game Win95 starts up again.

In OS/2 everything is running all the time, I would call OS/2 the better
solution.

  -Mike