Wengier,
For XyWin, start.exe should be command.com to work out of the box. Works
well when you "go to DOS" from XyWin.
The cmds.lst has "internal" (DIR etc.) and "external" commands (XCOPY
etc.). What are the technical issues involved? Does this version add any
real additional functionality to what was already present in vDosPlus
(in case one would substitute this version for the old one)?
BTW, maybe this would be a better way to rename files (in case you are
willing to do such a thing):
cmds.lst => start.lst
readme.txt => start.txt
start.exe could perhaps also recognise internally "command.lst" as an
alternative to cmds.lst, then one could delete start.exe from the setup,
giving a setup like this:
command.com
command.lst
All this may seem like a lot of fuss, but my concern is to keep setups
as easily overseeable as possible by any user.
Best regards,
Kari Eveli
LEXITEC Book Publishing (Finland)
lexitec@xxxxxxxxxx*** Lexitec Online ***
Lexitec in English:
http://www.lexitec.fi/english.htmlHome page in Finnish:
http://www.lexitec.fi/> Wengier,
>
> Would you consider changing the filenames a bit to make it easier to
> locate the files that belong together and to enable a drag-and-drop
> install over existing setups. This way:
> cmds.lst => start_cmds.lst
> readme.txt => start_readme.txt
> start.exe
>
> Best regards,
>
> Kari Eveli
> LEXITEC Book Publishing (Finland)
>
lexitec@xxxxxxxxxx>
> *** Lexitec Online ***
> Lexitec in English:
http://www.lexitec.fi/english.html> Home page in Finnish:
http://www.lexitec.fi/>
>
>> I have uploaded a new version of start.exe, which will (hopefully)
>> handle both URLs and inputs like "start.exe dir/p". It also improved
>> support for the FOR command. The file are still downloadable from:
>>
>>
http://vdosplus.org/files/start.zip>