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 tom Homepage, Germany (West), 15.04.2022, 11:32

> Okay, those times are a bit more reasonable (although 18s is still a lot,
> but a cache would help with that). Of course, that's assuming RT is right
> and the prompt is wrong. Or if they're both right, where's the extra time
> coming from?
it might be cool to have an option -Z (time) to also display the DOS time:

Elapsed time: 04:02:09.88-04.02.10.22: 0.336 seconds

where the former is the 'official' DosGetTime time, and the latter your (more precise?) time.

in addition, RT has a couple of different ways to time things.
it would be cool to know if the times behave consistently or not

'-1', 'use the standard timer tick (55ms, 24 hours; default)', NL
'-[1]+', ' as above, but can time across days', NL
'-2', 'use the CMOS timer (1ms, 48« days)', NL
'-2+', ' as above, but restarts the timer if BIOS turns it off', NL
'-3', 'use the hi-res timer (1æs, 1 hour)', NL
'-t', 'display only the time', NL
'-r', 'display only the ticks (raw)', NL
'-w', 'write timing information to stderr', NL
'-c', 'compact, no blank line before output', NL
'-e', 'execute the program directly, rather than loading first', NL

Post reply
 

Complete thread:

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