>> 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
>> No
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 th
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\
2009/6/21 jasse...@itelefonica.com.br
> I only tested it with 4364KB, which is the same size I use under
> DR/MS DOS. This is just a value I found to work comfortably for
> all my ordinary applications. I may try other values if you think
> this is important. BTW, I have 16 MB total memory in thi
Jeremy said:
>Does this happen for any size or what size do you create?
I only tested it with 4364KB, which is the same size I use under
DR/MS DOS. This is just a value I found to work comfortably for
all my ordinary applications. I may try other values if you think
this is important. BTW, I h
On Sun, Jun 21, 2009 at 2:14 AM, jasse...@itelefonica.com.br <
jasse...@itelefonica.com.br> wrote:
> FreeDOS (kernel=2038fat16, freecom=082pl3) reports a wrong
> (about 10% actual) size for a EMS ramdisk created with
> Frank Uberto FU_RD v.19i.
> ...
documentation says both have just one FAT. I
FreeDOS (kernel=2038fat16, freecom=082pl3) reports a wrong
(about 10% actual) size for a EMS ramdisk created with
Frank Uberto FU_RD v.19i.
Running CHKDSK on this disk reports a large number
of lost chains.
After some use, the dir command returns garbage,
albeit the files put in are still th
