Back to home page

DOS ain't dead

Forum index page

Log in | Register

Search:  
Back to the forum
Board view  Mix view

about to fix the "final" doslfn bug (Announce)

posted by Richard, 17.04.2022, 09:11

> > The long term goal is to work "off memory" (either CACHE or most likely
> a
> > RAMdrive - for all programs - where is best (assuming RAM drive) -
> > XMSFAT16, XMSFAT32, SXMSFAT16, SXMSFAT32 - or doesn't it matter?
>
> SX would let you keep 4Gi for normal usage. FAT32 would be better for
> drives over 512Mi. Otherwise I don't think it much matters.
>
>
> > For the next rerun of doslfn(MS) possibilities - I plan to
> simultaneously
> > on screen captures, show timings w/o SMARTdrv installed, then on same
> > capture, install SMARTdrv (won't be optimal element/buffer size values
> just
> > yet)
>
> Released RT 1.02, which adds -c to remove the blank line. You
> could just redirect the entire batch: command /c 1.bat >
> 1.txt; vecho will still write to the screen.


Your RT -c option seems to work perfectly for me (so far). Thanks.


So I was preparing code for SMARTDRV vs nonSMARTDRV and I came across the error


There is insufficient XMS memory to load SMARTDRV


OK so I reduced my XMS RAM drives (FAT16 + FAT32) from the approximately 741M each down to ~500M each and still gives the same error message.

My FDauto.bat has the lines


xmsdsk.exe 500000 I: /y
rdrvx32.exe 500M

and 1.bat etc has

SMARTDRV C D E 8192 1024 1024


Is my SMARTDRV (attempt) as above too big? (I would have thought reducing both XMS RAMdrives down by ~ 240M each should have been plenty to cover for SMARTDRV).

Maybe I am over looking something - the only changes to my program is "tacking" the SMARTDRV setup at the end of in 1.bat etc and "repeating the code set for without SMARTDRV.

Post reply
 

Complete thread:

Back to the forum
Board view  Mix view
22632 Postings in 2109 Threads, 402 registered users, 390 users online (0 registered, 390 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum