-=> Quoting Pat Gibney to Larry Marable <=-
Ok, here are some comments about this.  I don't know anything much
about QEMM, but will talk about it a little later.  I moved CONFIG first,
because it is executed first at boot, before AUTOEXEC.
 PG> --- And my config.sys;
 PG> device=c:\qemm\dosdata.sys
 PG> DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:7 D:3 H:5
 PG> DEVICE=C:\SB16\DRV\CTMMSYS.SYS
Neither of above 2 drivers loaded high?????
 PG> LASTDRIVE=D
 PG> DEVICE=C:\QEMM\QEMM386.SYS RAM R:2 ST:M
As I said, don't know about QEMM, but I wonder if RAM option is same as
EMM386's RAM option.  If so, this is setting up EXPANDED memory (I don't
know how much memory will be used.)  If this is what that option does,
I wonder if you actually need it.  Only games and older programs in
general (such as Lotus 123 for DOS) might even be using EXPANDED memory.
And this memory may not be released by QEMM when you start Windows,
with the memory lost to Windows use.
I recommend you read QEMM manual about this option.  And if it is
EXPANDED memory being activated, unless you need it for a DOS game,
I think you can kill it.
 PG> device=c:\qemm\dos-up.sys @c:\qemm\dos-up.dat
 PG> device=c:\qemm\loadhi.sys /r:1 /size=12704 c:\rocket.bin /m=4 /s
Don't know what this is.  Is it a driver for a harddrive of more than 540meg
space to be 'seen and used' on your harddrive?  If so, you definitely
need this to get to your data on your harddrive.
If it is a harddrive 'optimizer/speedup' ("rocket drive") it may
actually be a 'cache' and this means you have 4 'caches' active (see
below).  Horror of horrors.
 PG> FILES=80
 PG> buffers=25
 PG> shell=c:\qemm\loadhi.com /r:2 c:\dos\command.com c:\dos\ /e:512 /p
 PG> device=c:\qemm\loadhi.sys /r:2 /size=14032 c:\dos\setver.exe
Very few people need SETVER, only used with very old software. Kill it.
 PG> fcbs=20,8
 PG> device=c:\qemm\loadhi.sys /r:2 /size=47040 c:\hyperdkx.exe c:2048 h or
Ok, here you are loading up a 'cache', and giving it 2meg of your memory.
Don't know how it works under Windows.
 PG> device=c:\qemm\loadhi.sys /r:2 /size=9360 ansi.sys
 PG> dos=high
 PG> stacks=9,256
 PG> DEVICE=C:\QEMM\LOADHI.SYS /R:2 /SIZE=14160 C:\SB16\DRV\SBCD.SYS
 PG> /D:MSCD001 /P:2 0
 PG> DEVICE=C:\QEMM\LOADHI.SYS /R:2 /SIZE=4848 C:\WINDOWS\IFSHLP.SYS
This implies you have Win 3.11 for Workgroups, it isn't available in
earlier versions.  IFSHLP is a 2nd 'cache' you are loading up.  This is
the software to enable in Windows the 32 Bit File Access which is
Microsoft's name for Window's cache.
 PG> Ok, lets give it a go, here is my autoexec.bat;
 PG> C:\QEMM\LOADHI /R:2 C:\WINDOWS\SMARTDRV.EXE
Well, here you are loading up a 3rd 'cache'.  (Thought you weren't
using smartdrv?)  You didn't give it any memory options, so it will
take a default of 2meg in DOS and 2meg in Windows for your 8meg
memory machine.
 PG> SET SOUND=C:\SB16
 PG> SET BLASTER=A220 I7 D3 H5 P330 T6
 PG> SET MIDI=SYNTH:1 MAP:E
 PG> C:\SB16\DIAGNOSE /S
 PG> C:\SB16\SB16SET /P /Q
 PG> C:\QEMM\LOADHI /R:2 C:\WINDOWS\MSCDEX.EXE /S /D:MSCD001 /V /M:15
 PG> @ECHO OFF
 PG> REM C:\QEMM\LOADHI /R:1 C:\DOS
 PG> rem PROMPT $P
 PG> rem prompt $e[37;44;1m$p  blue & white
 PG> prompt $e[33;44;1m$p
 PG> rem prompt $e[37;41;1m$p  red & whit
 PG> rem prompt $e[37;42;1m$p  green & white
 PG> path=C:\WINDOWS;c:\;c:\dos;c:\qemm;c:\ut;c:\ss;c:\netscape;c:\trumpet;c
 PG> :\fprot; :\dr
 PG> C:\QEMM\LOADHI
Is this a 'stray' QEMM command with no options, or is it needed for
some purpose?
 PG> SET TEMP=C:\WINDOWS\TEMP
 PG> SET VIRSTOP=C:\FPROT
 PG> SET DIRCMD=/P/O:N
 PG> SET VIP=C:\UT
 PG> SET QSORT=C:\UT
 PG> c:\qemm\loadhi /r:1 /lo c:\MOUSE\MOUSE.EXE /Q
 PG> CALL eb
 PG> eb scan /pause
I don't know what the 'eb' software is.
 PG> CD\
 PG> MENU.BAT
 PG> -----------------------------------------------------------------------
OK, I see probably 3 separate 'cache' softwares being loaded in your
Config and Autoexec.  It's a wonder your machine will run at all in
Windows.  I don't know how Hyperdisk works, but can see you giving it
2meg of memory.  And Smartdrv is going to default to 2meg under Windows
with no specific options given (on an 8meg machine).  And IFSHLP will use
what you have set in Windows Control Panel, Virtual Memory, 32 Bit File
Access box.  And if the RAM option is activating Expanded memory, and
QEMM is not releasing this when Windows starts, you are also fragmenting
your upper memory for Windows use.  I'm guessing you have up to 6meg of
your 8meg memory given up to 'caches' when you start Windows.  As I said,
its a wonder Windows runs at all.  You will only have about 2meg memory
to load Windows and what applications you want to run.  You must have a
'swap' file set in Windows Control Panel or I would think you would get
out of memory error.  I'll bet the old disk drive really 'sings' when
you start up something like Q5forWin, using the swap disk drive as
virtual memeory since you don't have any 'real' memory much left.
Ok, on my QEMM soapbox.  I can't see anything being done much with
QEMM.  You don't even load the CTSB16 and CTMMSYS drivers high in Config.
I have about the same kind of soundblaster and cdrom machine as you,
use Msoft's MEMMAKER and get EVERYTHING loaded high and have 612K
memory free.  After DOS 6.0 came out, most of the 'utility' software
almost all people need was in DOS or Windows.  And Msoft wrote it and
the conflicts are reduced using only their stuff.  But you do what you
wish about QEMM.  If you drop it, you will need some different commands
in your Config and Autoexec.  Off my soapbox.
My recommendations:
First, copy your Config and Autoexec to different names.  Apparently
the above does run, and if you mess with them much, the machine might
not start at all. Actually, make a 'bootable' floppy and copy them
there, then you can boot from this with the same old Config and Autoexec.
Try each one of these changes at a time.  See if the machine and then
Windows starts ok.  If so, then add next change.
-Try to find documentation on 'rocket.bin'.  If it is giving you access
to your greater than 540meg harddrive, leave it alone.  If it is a
'disk speedup', I would REM it.
-REM the Setver line, unless you really know of some software that
will not run without it.  I doubt you do.
-REM Hyperdkx line.
-Keep the IFSHLP line.  Under non-QEMM there is no need to load it
high, it will load high on its own.  With QEMM, you probably have to
do as you are doing.
-You can keep the SMARTDRV, with the following changes.  Under Win for
Workgroups 3.11, with IFSHLP/32Bit File Access working, smartdrv will
be inactivated as your harddrive 'cache' when Windows starts, but will
remain active as your floppy cache if set up as below.  This keeps a DOS
2meg cache active and a 256k cache in windows for floppys only.
   ...C:\WINDOWS\SMARTDRV 2056 256
-In Windows,CONTROL PANEL,ENHANCED,VIRTUAL MEMORY,CHANGES:
---Set a PERMANENT swap file of about 4 meg.  You shouldn't need more
   unless you start editing graphics or some such stuff.  A large swap
   file (10meg and up) actually will slow windows down.
---Check 32Bit Disk Access (unless it is 'greyed out'.  If greyed out,
   you don't have an IDE diskdrive, or it is not compatible with this
   option, maybe because of its >540meg driver.  May not be able to
   'fix' this problem.)
---Check 32Bit File Access and set about 1.5 to 2meg as the 'cache'
   size.  For an 8meg memory machine, or really any machine, I wouldn't
   go over 2meg.  With this in effect, you will still have about 6meg
   of 'real' memory to start windows and then load applications.
   Plus the swap file if you fire up more applications.  This should
   run things nicely.
These windows changes will require you to re-start windows to go into
effect.
As I told you in my earlier message, I can start Quicken For Win Version 4
including  putting a 8 character password in, in I think I said 16 seconds.
I also have 3 years of transactions in my checking account.  And I have
a 486DX33 with 16meg memory.
Version 5 will start slower.  All new versions have run slower that I
have seen since Version 1 for Win.
But the above will get your machine set about as good as it can be set.
Since my machine is quite similar to your, with a SB16 soundcard and a
IDE CD-ROM, here is my Config and Autoexec.  I can't help myself, I
think I would also drop QEMM and use MEMMAKER.  Or use the following as
an example, since everything loads high and I think I still have 17k
of upper memory not being used.  Of course, I am not setting up Expanded
memeory, I seldom play games that use Expanded.
MY CONFIG:
-------------------------------------------
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS
BUFFERS=40,0
FILES=40
DOS=UMB
LASTDRIVE=J
FCBS=4,0
DEVICEHIGH /L:1,26928 =F:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 
H:5
DEVICEHIGH /L:1,10416 =F:\SB16\DRV\CTMMSYS.SYS
DEVICEHIGH /L:1,22576 =F:\SBCD\DRV\SBIDE.SYS /D:MSCD001  /P:1E8,11
DOS=HIGH
STACKS=9,256
SWITCHES=/F
DEVICE C:\WINDOWS\IFSHLP.SYS
MY AUTOEXEC:
-------------------------------------------
SET SOUND=F:\SB16
SET BLASTER=A220 I5 D1 H5 P330 T6
SET MIDI=SYNTH:1 MAP:E
F:\SB16\DIAGNOSE /S
F:\SB16\SB16SET /P /Q
LH /L:1,32096 F:\SBCD\DRV\MSCDEX.EXE /D:MSCD001 /M:8 /V
@ECHO OFF
@c:\windows\ad_wrap.com
SET MOUSE=C:\MOUSE
LH /L:1,56944 C:\MOUSE\MOUSE
LH /L:1,6384 C:\DOS\DOSKEY
LH /L:1,944 C:\UTIL\COLORDOS\COLORSET 2
LH /L:0;1,45456 /S C:\WINDOWS\SMARTDRV.EXE    2048 256
PROMPT $t$e $d $P$G
PATH 
C:\WINDOWS;C:\DOS;C:\;C:\MENU;C:\UTIL;C:\WINAPP\WINWORD;C:\wINAPP\WINFAX;C:\CO
MPRESS
SET TEMP=C:\TEMPFILE
SET DIRCMD=/O:N /P
SET WINPMT=WIN RUNNING!! EXIT Returns $p$g
MENU
... Any sufficiently advanced technology looks like magic. 
---
---------------