lst2str not always works with COM-files

[Flint]

It was found that lst2str cannot work correctly with .COM files (e.g. command.com). For example, I tested such a situation:
1. Create a file C:\list.txt that contains only one line of text - *.*
2. Copy lst2str.exe in the root folder of C: (to avoid long paths).
3. Execute the following line:

Code: Select all

lst2str.exe /X:command.com /S:"/K dir" /L:list.txt

4. A new console window for command.com is opened and the following error is written there:

Parameter format not correct - "*.*"

If the same line is executed with cmd.exe instead of command.com, all works correctly - the list of files in C:\ is printed.

[JackFoo]

The problem is actually with command.com, as it doesn't expand *.* when it's enclosed in quotes.

command.com /k dir "my documents"
returns a similar error, it says that [Parameter format not correct - "my] -> it ignores quotes in short try using the 8.3 old dos names when you pass the list file to lst2str.

Cheers.

[nsp]

I noticed the same and it is worse when you have accentuated characters...
this is for this purpose i develloped a standalone lst2multi replacement called TcBatlnc

=> What it does :
build a bat file with one expression per file
( allow you to edit before launch or stop if it is in test mode )
change the codepage to the default windows codepage
launch the bat file

=> where :
http://www.geocities.com/nospam0123456/forTC

if you find it usefull, i can add an exclusive $l switch that can replace each file by one occurence
of the listfile.