|
Post by emiliano on Mar 12, 2019 13:29:35 GMT 1
Hello, I have installed on a Windows Server 2008 the vdos, I wanted to know if it is normal that when running the system I use 100% of the CPU, which makes me run slow. I clarify that it uses shared files in a mini network. regards
|
|
|
Post by Jos on Mar 12, 2019 14:27:27 GMT 1
Your server CPU apparently only has one core, you could however lower the priority vDos.exe is running at. Better to run the DOS program at a workstation, that will most likely have better hardware specs.
Jos
|
|
VigoF
Guest
|
Post by VigoF on Mar 19, 2019 15:39:39 GMT 1
Also NTVDM on 32bit OS did the same most of the time, even in idle loop. It's possible by default NTVDM had a CPU limiter that kept CPU 90% for instance. You can get around it as Jos said.
|
|
|
Post by Jos on Mar 19, 2019 22:18:11 GMT 1
Besides the rarely used INT 28, there’s no method a DOS program can signal the OS it is idle. Not that surprising, most DOS programs were developed when there was no need for that. NTVDM just kept DOS programs running at 100% of one core. The utility TameDOS added several extensions to NTVDM, one of these idle detection. vDos has its own idle detection scheme. Although it will have a complete overhaul in the next version, it can still be fooled. Executing a DOS program at full speed while that isn’t doing anything useful.
If someone knows of a foolproof method to determine when a DOS program is actually idle, I’m open for suggestions…
Jos
|
|
|
Post by emiliano on Apr 4, 2019 20:43:35 GMT 1
Hello, is it to say that if I do not change the PC to one that contains more core, the system will continue using 100% of the CPU?
|
|
|
Post by Jos on Apr 5, 2019 0:36:21 GMT 1
If vDos is indeed fooled by your DOS program (being idle), all Windows programs will compete to get CPU usage of that same one core. vDos being an aggressive competitor, and Windows not actually multi-tasking. Just like we humans, only able to focus on one task, before dropping that and switching to another. At least vDos will try to fully utilize the core it’s running in, with only one core that is then also the CPU itself.
Jos
|
|