Hi! > DEVICE=C:\DEVS\RDOSUMB.COM #19 * > DEVICEHIGH=C:\DEVS\JEMMEX.EXE A20METHOD:FAST FRAME=E000 VERBOSE NOE801 NOE820 > NORAM D=0 VCPI > DOS=UMB,HIGH > DEVICEHIGH=C:\DEVS\EMSDSK.EXE 4364 /c02 ... > 6 file(s) 101,406 bytes > 0 dir(s) 325,632 bytes free > Note the reported free value. ... > It seems that FreeDOS does not work well with real-mode > UMBs, since EMSDSK no longer shows any problems if I rem the > first line in CONFIG.SYS and change the NORAM option to RAM. > Looking into UMBs (when they are real-mode), I found > command.com there, possibly overlapping the EMS frame area.
I do not know how command.com came there (try using SHELL instead of SHELLHIGH) but UMBs always cause a risk of using areas of RAM that you should not use. This happens both with real-mode UMBs and with JEMM386 / JEMMEX. You also use very "forcing" command line options for JEMMEX so maybe you even force it to use areas it should not. This can mean that access to disk/sound/network/USB/... will trigger something which overwrites your UMB, etc. Try finding a suitable X=... option for your JEMMEX and/or suitable options for RDOSUMB (or try UMBPCI) to avoid any problematic areas in your UMB. Note that EMSDSK might be able to work without page EMS frame, giving you more UMB. Eric ------------------------------------------------------------------------------ _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
