Re: Setting config.txt directives in command line is now supported natively in vDos-lfn

["Wengier W" dmarc-noreply@xxxxxxxx (Redacted sender "wengierwu" for DMARC)]

Hi Carl,

Yes, I had already planned to add the ability to specify a config file other than config.txt. I will do it tomorrow since it is too late today. I will take looks at the other options you mentioned tomorrow too.

Wengier
 


 
 
 
 On Sunday, July 24, 2016 11:52 PM, Carl Distefano  wrote:


 
Reply to note from "Wengier W" mailto:dmarc-noreply@xxxxxxxx (Redacted
sender "wengierwu" for DMARC) Mon, 25 Jul 2016 02:51:23 +0000 (UTC)


Wengier,


Good idea to integrate vDosSet into vDos-lfn.exe. I wonder if you could also
add the ability to specify a config file other than config.txt; for example,
vDos-lfn /cfg config.new /set screen=2. In this example, config settings
would be taken from config.new, but any screen= setting in config.new would
be overridden with screen=2. Also, an /aut autoexec.new option to specify an
alternate autoexec file. I would find this very useful, as it would
duplicate and add to the functionality in VDOS.BAT, which I posted some time
ago to the vDos forum:
https://sourceforge.net/p/vdos/discussion/general/thread/5eeef395/#66b9

Also, a /def option, which would load vDos-lfn with all default options (no
config.txt, no autoexec.txt) might be useful for testing purposes.

--
Carl Distefano
mailto:cld@xxxxxxxx