MoveFile does unintended 'dos 8.3 names', now reproducible

[Dick99999]

My earlier report was about copy. This one is about move. Why does it produce what looks like a DOS 8.3 name instead of the intended file rename name?

There also seems to be an issue with the base directory. From which directory should relative paths work in file operations?

Code: Select all

**BREAKPOINT**
Let>MF_RENAME=1
let>sailMaindir=\a\a\Sailmain
let>CWD=sailMaindir
let>moniUmtsFileName=temp\umtssignalfile
mdl>%sailMaindir%\%moniUmtsFileName%.tmp,%sailMaindir%\%moniUmtsFileName%.txt
MoveFile>%sailMaindir%\%moniUmtsFileName%.tmp,%sailMaindir%\%moniUmtsFileName%.txt
MoveFile>%sailMaindir%\%moniUmtsFileName%.tmp,%moniUmtsFileName%.txt

This produces:
- MDL message: \a\a\Sailmain\temp\umtssignalfile.tmp,\a\a\Sailmain\temp\umtssignalfile.txt
- Directory after 2 executions
C:\a\a\sailMain\temp\save (a directory)
C:\a\a\sailMain\temp\umtssig1.tmp
C:\a\a\sailMain\temp\umtssign.tmp
C:\a\a\sailMain\temp\umtssignalfile.tmp

- before execution CWD=c:\a\a\Sailmain
- The file to be renamed still exists even though Let>MF_RENAME=1
- the new files get dos 8.3 naming
- the second rename does nothing

I have specified absolute paths, relative did not work for me. Running MS 12.0.5 july 2010 on XP SP3, execute in debug mode.
ComSpec is %SystemRoot%\system32\cmd.exe