|
Post by johnw on Nov 16, 2020 21:52:10 GMT 1
Greetings!
We are test driving our legacy DOS based point of sale system on vDos 2020.03.01, running on a Windows 10 Pro 64bit workstation with 8GBs of memory. We have two CSV files that we import into the POS application daily, under native Windows 7 Pro 32bit it takes maybe a minute to process. In vDos it is easily taking all of 20 minutes to process the CSV files. Is there anything that can be done to improve performance, config.nt file? Any suggestions would be much appreciated.
Thanks
|
|
|
Post by Jos on Nov 16, 2020 23:29:42 GMT 1
I have to disappoint you, reading/importing those CSV files won’t be the issue. Will be the DOS POS program processing the data.
Although the emulated vDos CPU is slow compared to the actual one of NTVDM, a 20x seems extraordinary.
Start TaskManager to observe vDos is running at peak performance while your program is processing a CSV file. If it isn’t, move the mouse, or tap for instance the Shift key. Let me know of the results…
Jos
|
|
|
Post by johnw on Nov 20, 2020 1:40:13 GMT 1
Hi Jos,
I will do some testing tomorrow, 11/20 and report back to you. We have custom settings in the config.nt file, is vDos able to read files in the "system32" dir?
dos=high, umb device=%SystemRoot%\system32\himem.sys files=100 buffers=80 Shell=C:\windows\system32\command.com /E:4096
|
|
|
Post by Jos on Nov 20, 2020 7:25:14 GMT 1
Config.nt (and config.sys) doesn’t apply to vDos. See www.vdos.info/faqs.html - Miscellaneous - FILES= and other directives, once in config.sys. Jos
|
|