Re: Combined MEMORY FAQ now online

On Sun, 10 Nov 2002, Arkady V.Belousov wrote:

> ______________O\_/_________________________________\_/O______________
> if you have an AT (286) with a fair amount of memory (at least more
> than 640k) then you can use for CONFIG.SYS a)
> DOS=HIGH
> DEVICE=FDXMS286.SYS
> and use the XMS-swapping command.com. That way you have ~620000 bytes
> free, but all drivers you load (ctmouse, nansi, ...) are going to be
> in conventional RAM, thus eating from those 620000 bytes.
> _____________________________________________________________________
>               O/~\                                 /~\O
>
>      "If chipset supports, then UMB also may be present with help of some
> UMB driver. In this case DOS=HIGH,UMB statement should be used."

Right, the request was for a _simple_ guide of how to get memory free in
FreeDOS. Saying "some UMB" driver is not specific. So yes, of course there
are AT's with special chipsets out there; it was just beyond the scope of
the explanation here.

> ______________O\_/_________________________________\_/O______________
> The technique with UMBPCI is a variation between b) and c) and
> looks like this d)
> DOS=HIGH,UMB
> DEVICE=FDXMS.SYS (<64M)
> or DEVICE=FDXXMS.SYS (>64M memory)
> or DEVICE=HIMEM.EXE (if you feel like it)
> DEVICE=UMBPCI.SYS
> _____________________________________________________________________
>               O/~\                                 /~\O
>
>      Isn't better to run UMBPCI before other drivers (including XMS)?

No. UMBPCI extends the XMS interface supplied by the XMS driver so must be
loaded after the XMS driver. Some other UMB drivers can be loaded before
the XMS driver but UMBPCI isn't one of them.

Bart