2012/3/28, Bernd Blaauw :
> In-app profiling, or using a debugger maybe, could help.
> Otherwise, run DOS and your program inside an emulator
> (QEMU/Bochs/DosEMU) and get detailed output (timestamped logfiles) from
> that.
But of course using debugger I can check this in its every detail. But
ha
Op 29-3-2012 1:20, Zbigniew schreef:
> Ability to detect heavy CPU load can be important information for me,
> that e.g. I did something wrong (for example, some loop has to be done
> differently).
In-app profiling, or using a debugger maybe, could help.
Otherwise, run DOS and your program inside
2012/3/28, Michael Robinson :
> Since DOS environments typically don't multitask, there's no need to
> time applications as they consume CPU resources and preempt them to let
> other applications run. [..]
Ability to detect heavy CPU load can be important information for me,
that e.g. I did
Since DOS environments typically don't multitask, there's no need to
time applications as they consume CPU resources and preempt them to let
other applications run. Modern multi core processors can do real
multitasking and don't have to simulate process concurrency. In DOS
environments, t
