🚀 go-pugleaf

In <shopsis.55@panther.adelphi.edu> shopsis@panther.adelphi.edu (Charles Shopsis) writes:

>Earlier this week, I posted a message about read errors that I
>encountered after upgrading from Stacker 2 to stacker 3.  I
>received a number of responses from people having similar
>problems, and two suggested solutions.  The first one is the one
>I tried (deleting the /EMS on the stacker command line, so that
>stacker does not try to cache in expanded memory) and it did the
>job.  Following are the two suggested solutions and messages from
>other sufferers of the problem.

Hmmm.  This works for me with no problem (with QEMM 6.03).


>1. From: bing@zinc.cchem.berkeley.edu (Bing Ho)
>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.

The only problem I was aware of between Stacker and QEMM involving
/EMS was if you tried to use ST:F Stealth.  The problem there can be
corrected by doing what optimize tells you (adding the DBF parameter
to QEMM to make it trap INT13 accesses to EMS memory and buffer them
itself).  Otherwise, you can turn off the /EMS switch on Stacker to
eliminate the problem.

-- 
"Insisting on perfect safety is for people who don't have the balls to live
 in the real world."   -- Mary Shafer, NASA Ames Dryden
------------------------------------------------------------------------------
Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.