AWMoore
Guest
|
Post by AWMoore on Jul 11, 2018 19:07:37 GMT 1
By default, I have vDOS installed at C:\vDOS\ as per the installation default. I have an existing program that likes running from C:\AppWorkarea, but it can generated hundreds of thousands of files in a month. Is it possible to set a "bin"-like PATH within vDOS so that I can keep my App Executables in a separate location like C:\vDOS\bin and then be able to call those executables from any other directory (such that I can set autoexec.txt to start me in C:\AppWorkarea)?
|
|
|
Post by Jos on Jul 11, 2018 19:49:32 GMT 1
Did you have a look at the FAQs page of www.vdos.info?What about creating (Windows) C:\vDos\AppWorkarea and C:\vDos\bin? So in vDos/DOS you’ll get C:\AppWorkarea (C:\AppWor~1) and C:\bin. You can do PATH=C:\AppWor~1, I doubt your program can handle something like AppWorkarea as a directory name. Jos
|
|
AWMoore
Guest
|
Post by AWMoore on Jul 12, 2018 21:36:20 GMT 1
I did check the FAQs, but they didn't seem to answer my frame of the situation.
Is that PATH= a setting for config.txt? Or are you referring to the Windows System PATH?
Does vDOS fully load the Windows PATH locations?
|
|
|
Post by emendelson on Jul 12, 2018 21:56:39 GMT 1
You can add that PATH line to vDos's autoexec.txt along with the other lines in Jos's post.
vDos does not import Windows variables unless you specifically import them in autoexec.txt, putting %% around the name of the Windows variable, like this:
set userpath=%%userprofile%% set sysdrive=%%SystemDrive%%
|
|
|
Post by Jos on Jul 12, 2018 22:00:20 GMT 1
PATH=, or SET PATH= is a DOS command line instruction, so it belongs in a batch file. Eventually vDos autoexec.txt, the equivalent of DOS autoexec.bat.
vDos doesn’t inherit Windows PATH setting, its PATH is blank at startup. My Windows PATH is 572 characters with several LFN folder names. How is that supposed to fit in DOS PATH limited to 127 characters.
Jos
|
|
AWMoore
Guest
|
Post by AWMoore on Jul 12, 2018 23:57:52 GMT 1
Thanks for the help Jos & emendelson! The situation worked with the following:
1. Executables in C:\vDOS\bin 2. Workfiles in C:\workarea 3. autoexec.txt: @echo OFF SET PATH=C:\bin USE W: C:\workarea W:
Now my executables are separated from the work files. Process tested successfully.
|
|