Although Michael locked topic http://www.installaware.com/forums/view ... 5110#15110 (strange way to give support), the bug still exists. We are using NEWest version of InstallAware (version . We started using InstallAware only 4 months ago so we even had no possibility to use old version. Nevertheless, our customers get this error. Moreover. manual fix for problem was to use account without non standard letters, what was the bug in the beginning. So I guess bug is still there or it was introduced back in updates (we know how software bugs reappear after you fix something else).
So answer when the bug will be fixed or how we can get arround it in installer would be really nice to get.
Also please specify the exact version of the operation system and the code page used on the problem machines, as well as an exact user account name string and user access rights, this might help us re-create the problem sooner and possibly without requiring a VM upload.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
MichaelNesmith wrote:Also please specify the exact version of the operation system and the code page used on the problem machines, as well as an exact user account name string and user access rights, this might help us re-create the problem sooner and possibly without requiring a VM upload.
Operating system: WinXP (with SP3)
Locale: Lithuania
Language: Lithuanian
User name that had problem: Kristinukė
User access rights: administrator
I do not have possibility to get VM snapshot as this is private client.
Please let me know if you will manage to reproduce the problem.
It was very easy to reproduce the problem:
1. change your locale to Lithuanian and add Lithuanian language
2. Create user Kristinukė (with ė in the end) choose it to be system administrator.
3. Log in as Kristinukė
4. Run installer.
As you can see in screen shot, when compressed build tries to uncompress itself, error comes up.
Let me know if you will manage to reproduce it on your side and when we could expect the fix..
Funny, to see these comments from company representative on public forum... I thought i was helping to identify and fix one more bug for you that you can propagate to ALL your customers...
p.s. I never mentioned that this was an urgent bug. I asked: when is planned to be fixed.
One of our customers also reported “Setup resource decompression failure” error. We use InstallAware 9 R2 (Build Moya.sp3.070910)
Support found out that the problem was that his temp folder was huge (more then 1,7 Gb).
Simply emptied the temp folder using the Windows Disk Cleanup (Start -> ALll programs -> Accessories -> System Tools -> Disk Cleanup) and after that the installation went through with no problems.
. We started using InstallAware only 4 months ago so we even had no possibility to use old version. Nevertheless, our customers get this error. Moreover. manual fix for problem was to use account without non standard letters, what was the bug in the beginning. So I guess bug is still there or it was introduced back in updates (we know how software bugs reappear after you fix something else).