|
Post by dominicraf on Jul 24, 2023 12:17:20 GMT 1
Does vDos offer loading configuration from files other than autoexec.txt and config.txt located in the same directory as vdos.exe? For instance command line switches like: vdos.exe /c config-for-prog1.txt /x autoexec-for-prog1.txt
vdos.exe /c config-for-prog2.txt /x autoexec-for-prog2.txt Or, for, configurations in a different directory:
vdos.exe /c "%TEMP%\config-for-prog3.txt" /x "%TEMP%\autoexec-for-prog3.txt"
|
|
|
Post by Jos on Jul 24, 2023 12:53:29 GMT 1
For a different configuration you create a separate directory (….\prog1), or just use the directory of the program. Copy config.txt and autoexec.txt to there. Create a copy of the vDos shortcut and set the Start in property to that directory. Eventually change the name of the shortcut to Prog1…
Jos
|
|
|
Post by dominicraf on Jul 24, 2023 16:18:32 GMT 1
ok thanks I can do it that way, it's rather inelegant though!
|
|
|
Post by Jos on Jul 24, 2023 16:27:33 GMT 1
Our opinions obviously differ!
Jos
|
|
|
Post by whathim on Jul 25, 2023 15:11:36 GMT 1
I’m actually running another instance of vDos directly (I mean programmatically) from my Open editor, that is itself running under vDos. At first, I thought, like dominicraf, that there should be command line switches for specifying the appropriate config/autoexec.txt files. Since there aren’t, I (programmatically) do the following:
1. Save current directory
2. Change to directory containing child config/autoexec.txt
3. Launch the child vDos instance
4. Change back to saved current directory.
This simulates the “Start in” property of a shortcut and is working fine.
|
|