|
Post by jpinewoods on Jan 2, 2019 18:43:02 GMT 1
We have been running a DOS programme under Windows XP without problem. However the PC has died and we now have to migrate it to a Windows 10 system. The programme resides on a local drive and the data on a network drive. In a parameters screen we need to give the name of the data file and the drive letter on which it resides. Previously we have achieved this simply by mapping the Network drive to a the letter P and this has worked smoothly.
Using VS DOS and running both the programme (called issue.exe) and sample data in the C:\vDos folder and starting it with an autoexec file containing just the word "issue" using drive C in the parameters file it works fine. However if I try to access the live data by putting the mapped drive P in the parameters file it fails to find it. I am sure I need to do something clever in the autoexec file, but my memory of DOS is too sketchy to remember. Can you help?
|
|
|
Post by Jos on Jan 2, 2019 19:10:50 GMT 1
From the original autoexec.txt file:
rem vDos drive letters don't have to match those of Windows. rem It's even adviced they don't, to limit access to the Windows file system.
rem The USE command assigns vDos drive letters to Windows drives, folders, rem or network shares. The command syntax is: rem USE <vDos drive letter:> <Windows drive:|folder|network share>\ rem Examples: USE C: D:\dosprog\, USE F: \\server\share\dosprog\.
So something like: USE P: \\server\share\ issue exit
|
|
|
Post by jpinewoods on Jan 2, 2019 19:17:42 GMT 1
Jos,
Many thanks - it is pretty obvious really and I don't know why I didn't figure that out sooner - but I just did before reading your reply, so I am sorry for wasting your time.. It seems to work faultlessly.
Many thanks
|
|