Stephan Rose wrote:
I've been playing around with the supreme commander install most of today trying to figure out why it does not want to install. Running with +file,+msgbox and noticed the following error for virtually all files:
warn:file:wine_nt_to_unix_file_name L"TUB500.xsb" not found in /home/stephan/.wine/dosdevices/c:/Program Files/THQ/Gas Powered Games/Supreme Commander/sounds/Voice/fr/Tutorials
This is the file being copied when I get the "Error 87" message from Install shield.
Also, pretty much every file, if not every file, gives the same trace in the debug log. It's weird that install shield will copy hundreds of files with that warning in their trace and not complain until it is 80% through.
So then I wondered, is that really the cause or not? I think yes. Install shield appears to be kind enough to not re-copy the files if they already exist, so I killed the process to keep all files already copied and added the one missing file above from my windows install and then ran install shield again.
This time around, the file was processed correctly and no error. Instead it gives the error now on the next file, which is TUB500.xwb.
Some more trace below:
trace:file:GetFileAttributesW L"c:\Program Files\THQ\Gas Powered Games\Supreme Commander\sounds\Voice\fr\Tutorials\TUB500.xwb" trace:file:RtlDosPathNameToNtPathName_U (L"c:\Program Files\THQ\Gas Powered Games\Supreme Commander\sounds\Voice\fr\Tutorials\ \TUB500.xwb",0x334b84,(nil),(nil)) trace:file:RtlGetFullPathName_U (L"c:\Program Files\THQ\Gas Powered Games\Supreme Commander\sounds\Voice\fr\Tutorials\TUB500.xwb" 520 0x3348f8 (nil)) warn:file:wine_nt_to_unix_file_name L"TUB500.xwb" not found in /home/stephan/.wine/dosdevices/c:/Program Files/THQ/Gas Powered Games/Supreme Commander/sounds/Voice/fr/Tutorials
These messages are normal. GetFileAttributes is often used by programs to check for the existence of a file.
trace:file:MoveFileWithProgressW (L"",(null),(nil),(nil),0004) trace:file:RtlDosPathNameToNtPathName_U (L"",0x3348b8,(nil),(nil))
This is not. Moving a file with a blank name isn't going to work properly. Probably a test case is needed to see what happens on Windows. However, my guess is that there is a bug elsewhere that causes the installer to not get the correct filename.