|
Post by ko on Apr 12, 2022 16:23:49 GMT 1
Apologies if this question has been posted before. I searched and did not find anything.
Installed vDos on a desktop running Windows 10, no prob.
Installed vDos on a SurfacePro 3 running Windows 10 (not networked), and get:
Unable to allocate the scratch files in the default directory.
Possible reasons are write protection, network restrictions, or directory
full. Options are:
1 - Change drive and/or directory for scratch files
2 - Retry using the current path
0 - Exit
I provided a filename for newly created folder not in the folder chain that included vDos install folder, changed that multiple times to different folders, even to D:\, and have tried changing permissions to the folders.
No joy.
Solutions graciously accepted.
Thanks in advance.
|
|
|
Post by Jos on Apr 12, 2022 17:40:50 GMT 1
So the problem is with installing your DOS program?
Either: Start vDos with the log option (….vDos.exe /log), and look in the generated vDos.log file for the incorrect path, or Just copy the DOS program off the desktop 10 PC.
Jos
|
|
|
Post by ko on Apr 12, 2022 18:59:21 GMT 1
Apologies for the lack of clarity. I click on vDossetup.exe following download, goes fine. Then, when I click on the desktop icon that says: "Vdos - Initial Test" icon, I get the error message reported above.
|
|
|
Post by Jos on Apr 12, 2022 19:35:54 GMT 1
Somewhat the same procedure: Right click the icon, Properties, Shortcut tab, Target: Append /log to the ….vDos.exe string.
Then have a look at the generated vDos.log file in the directory of vDos.exe. Would be a (write) permission issue of the DataPerfect 2.3 Testdrive creating a scratch file.
Jos
|
|
|
Post by ko on Apr 12, 2022 20:33:31 GMT 1
1. won't run if i put the /log inside the quotes 2. will run if i put the /log outside the quotes 3. can issue cmd prompt, go to the directory wherein vDos resides, then execute vDos /log. Same error message. Again, no log file in this directory or any subdirectory. Coda: I assumed at first it was the write permission to the folder in which vDos resides, so I tried changing it from Read Only attribute as admin, but any change would not persist past Apply. So, I indicated D:\ which was an SD drive without attributes. No joy. Question: I am indicating to this vDos tester the actual names of the folders, NOT being able to issue a USE command to vDos. I could rename autoexec.txt and execute vDos without the CALL DPTEST\STARTDP found in the autoexec.txt, and see what happens? Thanks for the guidance ...
|
|
|
Post by Jos on Apr 12, 2022 21:21:21 GMT 1
Omitting CALL DPTEST\STARTDP should get you at the vDos command prompt. But the vDos directory (and subs) being read-only seems a real issue.
What if you start vDos as admin, you’ll have to add a ADMIN=ON line to config.txt.
Jos
|
|
|
Post by ko on Apr 12, 2022 21:46:25 GMT 1
yea, i don't get it either. i have admin privs, and i specified the directory. I think I'm going to clobber this install, and install again ... updates tmrw. Again, many thanks.
|
|