|
|
Post by aveprint on Aug 15, 2018 21:51:42 GMT 1
I'm just starting out, thinking I have everything set up correctly, but when I try to start program I get "End of File Error in File #001 (C)ontinue or (S)top" When I try to use the autoexec.txt it opens an endless succession of dos windows with the same message. :0
|
|
|
|
Post by Jos on Aug 15, 2018 22:02:39 GMT 1
"End of File Error in File #001 (C)ontinue or (S)top" is no error message of vDos. While an endless number of (NotePad?) windows when opening autoexec.txt would indicate a Windows problem.
What version of vDos do you use. Eventually download the latest (2018.05.01) version and test on another PC.
Jos
|
|
|
|
Post by aveprint on Aug 15, 2018 22:22:55 GMT 1
The message seems to be generated by my program, it IS in the vDos window, and opens many more of the same as it tries to execute repeatedly. I am running the latest (2018.05.01) version. I don't usually run this dos program from the CMD prompt, but simply click on the file (not a shortcut!) where it resides in a folder (in Windows XP) Sorry I don't know more about how these things work, but I'm trying!  Thank you for your understanding! |
|
|
|
Post by Jos on Aug 15, 2018 22:35:11 GMT 1
If you run Windows XP: vDos doesn’t support that anymore, it won’t start!
It won’t even install on that, so no idea how you accomplished installing vDos.
It’s not only for the obvious reason: Windows XP was mostly 32-bit and able to run DOS programs. Starting those at the CMD prompt, or double clicking the files. Windows XP however is not ‘future proof’, you need at least Windows 7 to run vDos.
So if you have a Windows 7 or 10 PC, install vDos on that.
Jos
|
|
|
|
Post by aveprint on Aug 17, 2018 22:49:35 GMT 1
I'm sorry, you misunderstood. I'm not trying to run vDos in XP, I'm trying to run it in Windows 10. I have had to upgrade and still need this program to work. To be clear, I'm running the latest version of vDos on the latest version of Windows 10. When I try to execute the program from the C: prompt in vDos, the program generates the error in the vDos window. "End of File Error in File #001 (C)ontinue or (S)top" If I press (C) the message repeats, if I press (S) the C: prompt returns. (Let's leave the autoexec.txt out of the equation for now! ) The file is FE.COM and it is in a folder called FE2 where all related files also reside, all in the vDos folder. Would you type the proper sequence, so I know I'm doing it correctly, in case that is the problem? Thank you! |
|
|
|
Post by Jos on Aug 18, 2018 7:08:57 GMT 1
Since you started FE.COM in Windows XP by double clicking it, the sequence would be:
CD FE2
FE.COM
If that starts your program correctly, the same lines have to be in autoexec.txt with a last EXIT.
Jos
|
|
|
|
Post by aveprint on Aug 27, 2018 18:34:54 GMT 1
Thank you Jos! That did it.  I wish I understood how.... If you don't mind a stupid question... What does the "CD" signify? |
|
|
|
Post by Jos on Aug 27, 2018 18:52:35 GMT 1
DOS has a current (active) directory: If you don’t specify some (other) directory, a program you execute is expected in this directory (we forget about the PATH environment varible).
FE.COM is however not located in the DOS C:\ directory, but in C:\FE2, it also expects to be started from there. So you first have to set by C(hange)D(irectory) the current directory to C:\FE2.
By double clicking FE.COM in Windows, Windows first sets its current directory to that where FE.COM is located, then starts FE.COM (by NTVDM).
Jos
|
|
|
|
Post by aveprint on Aug 27, 2018 19:34:48 GMT 1
Got it Thanks so much for all of your help! |
|
Thank you for your understanding!