|
Post by bradyb on Jan 4, 2022 20:01:26 GMT 1
Hi, I'm trying to setup some old DOS programs that rely on the directories they were installed with. Such as the F:\ drive which I have changed in vDOS. But I am having trouble with placing the application in the vDOS directory. I still run into the error where I cannot open the application, without the directory's correct.
Example: I open an application called FLTDATA.EXE It gives me this error "Cannot Create FLTDATA.DAT" This is my data file that keeps everything. So to troubleshoot, I add the files to vDOS directory. Then I receive this error, " Cannot Share F:\flt_ops\TIMEDUTY\PILOTS.DAT.
Does anyone have any good ideas to help me troubleshoot?
Thanks
|
|
|
Post by Jos on Jan 4, 2022 20:29:19 GMT 1
Shouldn’t be that hard.
If your program expects the directory F:\flt_ops\, create (and copy the files and subdirectories) flt_ops to any_location you desire. Then in autoexec.txt:
USE F: any_location\
So your program will actually get/see F:\flt_ops.
If F: is a Windows mapped drive letter to a network share, it could of course be:
USE F: \\server\share_name\
Jos
|
|
|
Post by bradyb on Jan 5, 2022 21:18:44 GMT 1
Thanks, What exactly do I need to add to my autoexec file? Is it limited to "any_location" Also does vDOS need to be in the same directory as the program?
Thanks.
edit: I also run into this error. "cannot share F:\FLT_OPS\TIMEDUTY\PILOTS.DAT"
This is what I have in my autoexec file:
Use: F:\FLT_OPS\TIMEDUTY\
|
|
|
Post by Jos on Jan 5, 2022 22:26:54 GMT 1
Use: F:\FLT_OPS\TIMEDUTY\ is incorrect, the general syntax is (somewhat like Windows SUBST/NET USE): USE <DOS_Drive_Letter>: <Windows_path> So it should be: USE F: \\FLT_OPS\TIMEDUTY\ Don’t get “Is it limited to any_location”. “any_location” just means any Windows path. It’s advised to have only one copy of vDos.exe around, even in a network with many workstations. So it doesn’t have to be in the same directory as the program(s). You just have to set/assign the DOS drive letter(s) (by USE...) to what the program(s) expects. See www.vdos.info/faqs.html. Eventually add a line with PAUSE to autoexec.txt before that starting your program. So you'll see errors with for instance USE. Jos
|
|
|
Post by bradyb on Jan 6, 2022 18:48:01 GMT 1
Jos, Thanks for al of your help. Where do I need to place vDOS, does it need to be in a folder with all of the programs? Also I put this into the autoexec file: USE F: \\FLT_OPS\TIMEDUTY\
PAUSE It still does not work. Note: The vDOS is in the C: drive on my windows PC. My programs are on an F: drive on the same PC.
|
|
|
Post by Jos on Jan 6, 2022 19:32:41 GMT 1
It doesn’t matter where vDos (vDos.exe) is located, though it is by default installed in C:\vDos.
You have to realize that vDos/DOS drive letters also by default are not those of Windows. You only get a DOS C: that is assigned to the directory of vDos.exe. Or the “Start in” directory of the shortcut used to start vDos.exe.
So if you have a local Windows F: drive, and that is expected to be addressed as DOS F:, you have to add that assignment by:
USE F: F:\
At the start of autoexec.txt.
Adding a line with PAUSE before and after your program is started should show you what is actually going on (wrong).
Did you have a look at the vDos FAQs.pdf document?
Jos
|
|