🚀 go-pugleaf

  > jbayer@ispi.COM (Jonathan Bayer) writes:
       >jimm@cbnewsi.cb.att.com (james.mumper) writes:
            >>...all except mouse.sys loads high.  I have tried to load
            >>only the mouse driver into high memory by REM'ing out the other
            >>drivers and it still won't go...  
  >
  >The mouse driver probably uses more than 44 KB when starting up
  [some comments deleted]  
  >
  >QEMM will solve your problem...

Well, now, What I don't get is why the mouse driver doesn't load even
when it is the only one Jim is trying to load into the UMB.  I didn't
have any trouble loading mouse.sys without any trickery.  Perhaps there
is some incompatibility with your particular driver.. are you using the
MS mouse driver that came with Win 3.1, or some other driver?

In any case, I would have to agree with Jonathan on one point.  QEMM 386
will make your life easier ... may not solve this problem directly, but
certainly will be a lot more informative to you concerning what your
problem is and how to go about solving it.

A very nice feature of QEMM is the Optimize program, which will
automatically look at all of your device drivers and TSRs, test them all
for loading, determine optimum loading sequence and parameters, and then
insert all the necessary lines in your autoexec.bat and config.sys
files.  All you have to do  is sit back and watch it work.

MS, on the other hand, leaves you to figure out how to do this, and it
is *not* a simple job.

P.S.  When you use QEMM, you do not need HIMEM.SYS nor EMM386.EXE.  QEMM
takes up much less memory than those two, so you get even better
performance.

Disclaimer bit:  Quarterdeck doesn't pay me, but maybe they should.

-- 
--------------------------------------------------------------------------
Roy Schmidt                 |  #include <disclaimer.h>     
Indiana University          |  /* They are _my_ thoughts, so you can't
School of Business          |     have them, so there! */