home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!das.wang.com!ulowell!news.bbn.com!usc!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!ames!network.ucsd.edu!psycho!rec
- From: rec@psycho.uucp (Richard E. Currier)
- Newsgroups: rec.games.misc
- Subject: Re: uw2 : stacker conflicts
- Date: 26 Jan 1993 17:32:14 GMT
- Organization: UC San Diego
- Lines: 19
- Message-ID: <1k3siuINNio9@network.ucsd.edu>
- References: <44034@sdcc12.ucsd.edu>
- NNTP-Posting-Host: psycho.ucsd.edu
-
- In article <44034@sdcc12.ucsd.edu> garton@jeeves.ucsd.edu (Simon Garton) writes:
- >A very big warning to all in net land ! I installed uw2 on
- >my stacker 3.0 drive and played merrily for 10 days, nearly
- > (then crashing)
-
- One thing I have found is that running the stacker disk cache in expanded memory
- with the "/EMS" switch on the stacker driver line in config.sys. If you have the
- /EMS switch in your config.sys, just edit it out. Its ok to run Stacker in UMBs
- but not expanded memory with some programs. Actually, the manual for Stacker 3.0
- warns about this. You don't need the cache in expanded memory. It's just handy if
- you want to run big buffers there for speed.
-
-
-
- --
-
- richard currier IGPP u.c. san diego
- rec@psycho.ucsd.edu
- 619-534-3759
-