Re: VDL problems

[Carl Distefano cld@xxxxxxxx]

Harry,
OK, let's take a step back. Before you use VDL.BAT, you've first got
to understand the native command-line syntax for vDos-lfn.exe.

Grok these examples:
To start a vDos-lfn session using your current config.txt and
autoexec.txt files:
vDos-lfn.exe
To start a vDos-lfn session taking config settings from config.new
(not config.txt) and using your usual autoexec.txt file:
vDos-lfn.exe /cfg config.new
To start a vDos-lfn session using your current config.txt and
autoexec.txt files, but overriding the frame= and showital settings in
config.txt:
vDos-lfn.exe /set frame=on; showital=off
To start a vDos-lfn session taking config settings from config.new
(not config.txt) and using your usual autoexec.txt file, but
overriding the frame= and showital= settings in **config.new**:
vDos-lfn.exe /cfg config.new /set frame=on; showital=off
To start a vDos-lfn session using your current config.txt file but
autoexec.new instead of autoexec.txt:
vDos-lfn.exe /set autoexec=autoexec.new

To start a vDos-lfn session using config.new and autoexec.new:
vDos-lfn.exe /cfg config.new /set autoexec=autoexec.new
Once you know how to use vDos-lfn.exe on the command line, then
understand that VDL.BAT takes all of the same arguments. No difference
whatsoever! VDL.BAT's value-added is in the ability to create one-word
aliases for long vDos-lfn command lines. To do that, you need to
follow the models in VDL.BAT *****EXACTLY*****. None of your posted
examples is correct, I'm afraid.

Hope this helps.

--
Carl Distefano
cld@xxxxxxxx