|
Post by georgecg on May 11, 2023 19:13:42 GMT 1
Hi!
I have a .bat file that in version vDos 2021.05.01 and previous, when executed it did well.
Batch file: PRUEBA.BAT
CMD "XCOPY" VTZOCLAR.XLS %1\*.* /Y
I execute PRUEBA TEST
Then in the subdir labeled TEST copies VTZOCLAR.XLS
Now with the versions from May 2022 to the latest one 2023.05.01, it does it wrong.
Creates a directory with label %1 instead of the value of the parameter TEST,
and copies the XLS FIL
Thanks in Advance
|
|
|
Post by Jos on May 11, 2023 21:13:59 GMT 1
Passing on DOS variables to CMD seems rarely used: This mishap was already introduced in version 2022.05.01.
Expanding the command line (replacing variables) was moved (done later on if CMD etc.) because of inconsistency with using %% Windows variables and/or quoted strings. I’ll have to carefully look how to fix this (exceptional) use.
Will report when I figured out how to solve this w/o breaking current use of the command line.
Meanwhile stick with version 2021.
Jos
|
|
|
Post by martin on May 12, 2023 17:34:15 GMT 1
As a workaround, try
C:\command.com /c CMD "XCOPY" VTZOCLAR.XLS %1\*.* /Y
in PRUEBA.BAT.
Works for me to open textfiles in windows Notepad from vdos command line via a notepad.bat
HTH
Martin
|
|
|
Post by Jos on May 24, 2023 17:52:04 GMT 1
I’ll change passing on variables to CMD (and START):
If the variable is known/valid in DOS/vDos, it will be replaced by its value.
Else the variable will be passed on as-is, so replaced (or dropped) by CMD.
Jos
|
|