🚀 go-pugleaf

In article <shopsis.51@panther.adelphi.edu> shopsis@panther.adelphi.edu (Charles Shopsis) writes:
>After I installed stacker 3 I re-stacked my disks to take
>advantage of its improved compression (I got an extra 3 or 4 Mb
>on each disk). I then started getting "read errors" from some
>programs.  Often the errors weren't fatal; I'd get a message
>about a read error, and then the program would manage to read
>its code or data and continue to run.
>
>Charles Shopsis, Dept. Chemistry, Adelphi University
>shopsis@auvax1.adelphi.edu       or        shopsis@panther.adelphi.edu

My friend recently bought Stacker 3.0 and managed to figure out what was
wrong (at least for his machine).  He mentioned that the use of a
386 memory manager and running Stacker 3.0 with the /ems option caused disk
read/write errors.  He switched to the upper memory or conventional memory
configuration and mentioned that any problems were completely fixed.

I think that Stacker 2.0 had this problem with qemm as well, but it was
less frequent.

-- 
Bing Ho
bing@zinc.cchem.berkeley.edu   University of California, Berkeley