Re: Memory management FAQ

> Now if you don't want those drivers eating away from conventional RAM
> then you can use
> c)
> DOS=HIGH,UMB
> DEVICE=HIMEM.EXE
> DEVICE=EMM386.EXE

in most cases, you can use
> DEVICE=EMM386.EXE NOEMS

as only few programs require EMS. this makes 64 KB more UMB available,
which is in most cases more helpful, specially with (MS) network client.


> DEVICE=FDXMS.SYS (<64M) or DEVICE=FDXXMS.SYS (>64M memory) or
>   DEVICE=HIMEM.EXE (if you feel like it)

testing:
with only 
	 DEVICE=FDXMS286/FDXMS/FDXXMS/HIMEM.EXE

and nothing else, mem /f reports:

DEVICE=HIMEM         available memory      631904 byte
DEVICE=FDXMS286    available memory    631712 byte  (*) see below)
DEVICE=FDXMS         available memory    631488 byte
DEVICE=FDXXMS        available memory    631072 byte

conclusion:If you want more free memory, you should use HIMEM.EXE.
using FDXXMS unnecessary costs 400/800 byte, compared to FDXMS/HIMEM

(*) with FDXMS286, after running MEM /F, the PC was dead. YMMV



> In general, using the XMS-swapping FreeCOM, situation b) isn't nearly as
> bad as it used to be. Only if you need a few large device drivers you
will
> get into trouble.
or use MSNET or NTFSDOS ;-)

tom