|
|
Post by chaineskrug on Jul 5, 2022 13:36:43 GMT 1
My program keeps returning a OPENFILE error because the file its looking for does not exist. It also doesnt exist on the virtual machine and runs fine without it so im wondering if its created and deleted instantaneously. does vDos have permission to write to the computer?
This is the error code if it helps:
3.06 Clipper assumed, slow pasting
INT 2F unhandled call 4010
4.03 OPENFILE failed: PDMAIN\CONF1\ADMIN\PD1MENU.CDX(2) => \\jordan\pdmain\PDMAIN\CONF1\ADMIN\PD1MENU.CDX(2)
4.20 INT 00 => original
|
|
|
|
Post by Jos on Jul 5, 2022 14:42:43 GMT 1
Basically vDos does no file operations of its own. Like deleting a file if not instructed to do so by a DOS API call.
No corresponding CREATEFILE failed: …, suggests your program doesn’t create that file, or at another location.
Could it instead be that file is copied from another folder or file by calling the command processor with COPY and that failed due to an incorrect path?
Jos
|
|
|
|
Post by chaineskrug on Jul 5, 2022 14:49:38 GMT 1
Basically vDos does no file operations of its own. Like deleting a file if not instructed to do so by a DOS API call. No corresponding CREATEFILE failed: …, suggests your program doesn’t create that file, or at another location. Could it instead be that file is copied from another folder or file by calling the command processor with COPY and that failed due to an incorrect path? Jos I have a very strong feeling that its because im using cd PDMAIN\COMP1 and then running the batch file. The program then seems to run its call for the file AFTER this so it goes off of the already mounted PDMAIN\COMP1 and then adds on \PDMAIN\COMP1 AGAIN so it cant find the file. So it runs PDMAIN\COMP1\PDMAIN\COMP1......... Is there a way I can launch the program without using cd and launching the batch file on my network drive? |
|
|
|
Post by Jos on Jul 5, 2022 15:22:27 GMT 1
If you started the batch file by for instance double clicking in File explorer or a link, realize Windows then set the current work directory to that folder.
Selects that drive (F:?) and does a CD folder, so NTVDM starts in F:\folder.
In vDos you would have to select that drive and do CD folder.
Jos
|
|
|
|
Post by chaineskrug on Jul 5, 2022 16:00:38 GMT 1
If you started the batch file by for instance double clicking in File explorer or a link, realize Windows then set the current work directory to that folder. Selects that drive (F:?) and does a CD folder, so NTVDM starts in F:\folder. In vDos you would have to select that drive and do CD folder. Jos I cant figure out why its searching for a file that doesn't even seem to exist or ever exist. I have the program running in a Virtual Machine perfectly fine but it refuses to Run properly in VDOS. Record Locking Verified for DOS F: CLIPPER ASSUMED, SLOW PASTING. What do these mean? |
|
|
|
Post by Jos on Jul 5, 2022 17:03:51 GMT 1
Again, ensure you have the same drive and working directory in vDos as in NTVDM. Eventually add:
CD
PAUSE
To the top of your batch file to verify.
"Record locking verified for DOS F:" means your program requested a file region lock for a file on DOS F:. And vDos verified the lock was actually applied by Windows or the OS managing the remote drive. It’s of course only once reported for a (DOS) drive letter.
"Clipper assumed, slow pasting": vDos detected a Clipper program is executed. Those have a mechanism of maintaining a separate keyboard buffer. That is updated/filled by constantly pulling characters out of the regular BIOS keyboard buffer. With the mishap that this pulling doesn’t stop as the separate keyboard buffer fills up. So characters get lost if more than the size of that buffer is pasted. To circumvent, vDos then inserts pauses at pasting text.
Jos
|
|
