|
Post by hondacub on Mar 8, 2022 19:06:10 GMT 1
Hello,
I am running a old dos point of sale program on a network running windows xp computers. I would like to add in a new windows 10 to the network and map to the computer running the old dos program so it will run on the new windows 10 computer Not sure how do that... Any help would be appreciated Thanks for your time
Mike
|
|
|
Post by Jos on Mar 8, 2022 19:35:20 GMT 1
If the POS program runs at one PC and the data is only locally stored there: Copy its folder(s) to the folder (C:\vDos?) you installed vDos to. Then modify autoexec.txt so your program is started with vDos.
If the data and eventually the program is on a server, or a PC acting as one: Assign the designated DOS drive letter to the network share by USE DOS_Drive_Letter: \\servername\sharename and put in autoexec.txt and add the commands you used before to start the program.
Jos
|
|
|
Post by hondacub on Mar 18, 2022 17:27:11 GMT 1
Hello,
Here is what I have in the autoexec...
use M: \\dell200parts\inv\
M:
inv.exe
exit
It loads and runs the program.. One small issue is the time it takes to run a report from the DOS program... It takes around 10 to 15 seconds on the main computer when I run it through VDOS it takes 2 to 3 mins Is there some setting I should change?
Thanks Mike
|
|
|
Post by Jos on Mar 18, 2022 17:59:30 GMT 1
The relative slowness would be caused by: 1. The main PC gets the data off a fast hard drive, and since that Windows instance controls it, Windows can also cache the disk operations. In contrast to the workstation that has to do with a relatively slow network connection, and cannot do any caching. 2. If the report involves an large amount of CPU operations, like calculations on data, the slowness of the emulated CPU adds some extra lag.
You could have a look at TaskManager if vDos actually running at peak performance during the report. There’s then no setting to improve that.
Jos
|
|