Bart Oldeman said:
> I see no problem here
> What are you seeing? How do you load emsdsk? What is a minimal
> config.sys/autoexec.bat that exposes the problem? In other words,
> how can others reproduce your problem?
I load it in config.sys :
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
.
.
.
and see this after autoexec.bat finishes:
Volume in drive G has no label
Directory of G:\
COMMAND COM 93,963 10-12-03 4:49
E3 EXE 4,095 02-03-08 22:48
LF COM 256 07-03-09 2:59
BROWSE COM 1,044 24-02-91 3:04
TETRIS COM 2,048 13-04-05 23:29
6 file(s) 101,406 bytes
0 dir(s) 325,632 bytes free
Note the reported free value.
There is a value of EMSDSK size (5648K) above which dir
reports correct values.
If I omit the FRAME option in CONFIG.SYS, then I see this
message during boot:
*** EMS RAMdisk v1.9I (FU - 08/98): ems get frame error
and EMSDSK does not install. The memory map in this case
shows no EMMXXXX0.
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.
Should real-mode UMBs be different from UMBs created by
paging ? DR/MS/PC DOS work well with real-mode UMBs.
JAS
------------------------------------------------------------------------------
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
