It turned out that the user's HDD died and after he reinstalled the system everything came back to normal, so I guess we need to close this ticket as we won't be able to verify the fix.
One of our end users just hit a strange problem. Unfortunately to fully explain it I will need to briefly describe our installer, so please bare with me ;-).
So, our installer consists of two parts. One (let's call it Core) contains all the binaries, and the other (let's call it Product ...
Did you manage to verify that string? I am asking because the string is still visible in the updater-res.dll from version 6.2 and gives me pain upgrading to this version.
Thanks so much. I was beginning to worry that there is something utterly wrong with me ;-).
I hope you'll implement the Unicode bootstrapper soon as this problem together with http://www.advancedinstaller.com/forums/viewtopic.php?t=4986 forces us to do quite a lot of hackery to allow ...
The installer runs ok when invoked by double clicking on it (i.e. with long path), but it gives me msiexec help dialog when invoked from command line using command:
I'm getting the same effects on Japanese Windows Vista Home Premium.
For example, the bootstrapper is launched with the short path "C:\EFC3~1\setup.exe" instead of "C:\サダィデスクトップ\setup.exe".
I think here lies the problem. On my PCs when I create folder c:\サダィデスクトップ\ then its short path is c:\サダィデ~1 . I also have the opposite effects. The installer ...
I've spoken to my colleague which started using CreateProcess with path as a second argument. Apparently he hasn't got much choice as according to Microsoft ( http://support.microsoft.com/kb/175986 ) using only second argument or both arguments (cases 2 and 3) are the only ways of ...
I've tried this on another PC. I've installed Japanese Windows XP SP2, installed all recommended updates from Windows Update and:
Copied the installer (sample.exe - description on how to create it are in my original post) onto Desktop of a user which has Japanese username (with some ...
A thought has just stroke me. If I remove Extract Location entirely then a temp path will be assumed. If you're using GetTempPath API function to get path to TEMP directory, then you get short path, which doesn't contain any wide chars in which case the bootstrapper is in a way Unicode ...
FOLLOW US
Get the latest news in Application Packaging