Printable View
We're having quite a few clients get a "Decompression Error #1" on one particular file in our installation. In all these cases our Support has had the client recopy or redownload the install package but they keep getting the same error. If they skip the feature (it's optional) containing the file then the install proceeds. What causes this error, what should I be looking for?
Attachment 4732
Just for fun, what happens when you set the setup.exe compression level to, say, "Fast". This will generate a different binary contents. Perhaps the file (or a magic combination of bytes in this file) triggers a file-lock (false-positive).
Can you reproduce this on your machine? Are you using the latest SB build? Is the setup.exe (and SS.EXE) code-signed?
Friedrich
No we haven't been able to reproduce it. No we're not on the latest build of SB as it was released when we were partway through this project and we don't update mid-stream, we'll update our SB build for the next release. Yes SS.exe was digitally signed, as was the installer.
So, is error #1 a file lock?
Mark,
this is an unspecified error. I would suggest to change the compression level to test it. Set it to FAST and see what happens. Does this make any difference?
Friedrich