|
|
Post by jjjoseph on Jun 28, 2019 8:27:55 GMT 1
My 64-bit Windows 7 is approaching end-of-life as of the January 2020, so I'm looking to move our VP-Info tools to new Windows 10 PCs. Is there anything I need to know before making the move?
Thanks!
JJ
|
|
|
|
Post by Jos on Jun 28, 2019 9:31:23 GMT 1
The only condition for vDos is that it needs Windows 7 or later to run. If speed is a concern, the number of CPU cores doesn’t matter since vDos uses only one core. Though the faster a single core…
Jos
|
|
|
|
Post by steve on Jun 30, 2019 12:05:10 GMT 1
Re Number of CPU cores. Surely, if you can dedicate one CPU core to vDos then the (DOS program) performance would be better? I have found how to set the processor affinity within Windows but am not sure if Windows10 can 'discourage' other processes from using that processor!
|
|
|
|
Post by Jos on Jun 30, 2019 13:43:39 GMT 1
Windows will spread the running processes over the available cores.
For as I know, a program cannot claim a core exclusively for itself.
Jos
|
|
|
|
Post by steve on Jun 30, 2019 17:52:31 GMT 1
Hi Jos, What happens if you also set the vDos process priority to either High or RealTime? I am hoping that Windows will not attempt to share that processor with lower priority processes.
|
|
|
|
Post by Jos on Jun 30, 2019 18:33:48 GMT 1
In general very little to nothing. If you have a look at the Task Manager, you’ll notice vDos already ties up the core for (almost) 100% when it (your DOS program) is busy.
Probably most effective would be to limit the competing Windows programs accessing the drive or network when your DOS program also does so.
At the moment I have for instance Notepad++ open with 8 files. It constantly probes if one of those are changed externally. I know this degrades vDos (also addressing the drive) performance by a few percent. The same for FreeCommander, Opera, Word…
When I really want to accurately test vDos performance after some changes, I just close all other Windows programs, and have a peek if some Windows process is by change real busy.
Jos
|
|
|
|
Post by jjjoseph on Jul 1, 2019 9:53:47 GMT 1
" The only condition for vDos is that it needs Windows 7 or later to run." The speed and reliability of vDOS is no concern. Both are excellent. For me, it's enough that it's light-years ahead of the older DOS setups of long ago. I was more concerned about vDOS going upmarket to 64-bit Windows, leaving 32-bit Windows behind. Is this a problem? |
|
|
|
Post by Jos on Jul 1, 2019 11:09:49 GMT 1
The next vDos release will also have a 64-bit version (vDos64), of course only running on Windows 64. But that is more a precaution for if MS would release a Windows (server?) edition only supporting 64-bit software. vDos 32-bit will remain the main distribution since it runs on 32 and 64-bit Windows. And it’s smaller and faster than vDos64  . Jos |
|
.