Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

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

posted by jadoxa Homepage E-mail, Queensland, Australia, 15.04.2022, 09:34

> 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.

> Talking about xCOPY...
> - the computer locks up (~~ half way through). According to Windows, C:\
> drive contains 6986 items (6602 files + 385 folders) size 463 MB (size on
> disk 471 MB).

Is that your FreeDOS install? Curious, according to dir/s/a mine is 9642 files, 1842 dirs, 439M total (1.3 installed on top of 1.2, I think it was). Worked fine under VirtualBox, to a 500Mi FAT32 drive. I'll try it in real DOS tomorrow.

> 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), and run comparisons. Hence why I was so interested in removing the
> blank line before "Elapsed time:..."

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.

 

Complete thread:

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