A decompression error has been detected.

[NewsArchive]

A customer had this error.

A decompression error has been detected.

File: C:\Users\Public\Documets\My Path\Myfile.exe[#-200000003]"

I found out the folder that should have been created did not get created along with 3 others, but 5
other folders were created. They were created in script sequence. This script is the same script
used when a server install is selected.

So when the installer was copying files and it got to the above file with no folder it crashed.

So what would cause it to not create a folder? This was the Workstaion install. The Server installer
is in the same exe and the Server created all the folders properly.

You posted

If an internal error code is reported (unzip error 8 seems to be
"uncompressed size differs from recorded") then it's 1.) the anti-virus or
spyware is buggy and crashes the system (stack corruption, etc.) -or- 2.)
the ZIP archive is damaged.

Jimmy Rogers

[NewsArchive]

Jimmy,

> A decompression error has been detected.
>
> File: C:\Users\Public\Documets\My Path\Myfile.exe[#-200000003]"

This is Windows GetLastError code "ERROR_PATH_NOT_FOUND 3 (0x3) The system
cannot find the path specified".

This is not related to what I posted regarding "Error 8" because Error
#-200000003 is not a "real" decompression error. The decompression library
just returned this error code (the CreateFile Windows API returned
ERROR_PATH_NOT_FOUND) and so it is treated as a decompression type error.

Is "Documets" a typo in this thread or did you really specify "Documets"
(and not "Documents")?

Friedrich

[NewsArchive]

> So what would cause it to not create a folder?

BTW, if a folder is not created then in 99.99% of all cases this is caused
by a permission issue.

Friedrich

[NewsArchive]

Just checked this and even with "Documets" it's not a problem. And if you
do not create "Public\Documets" and/or "Public\Documets\My Path" then the
install will automatically do it for you.

Install to: "C:\Users\Public\Documets\My Path"

|004|C:\Users\Public\Documets
|004|C:\Users\Public\Documets\My Path
|006|_0000_|C:\Users\Public\Documets\Myfile.exe\li mit.ini|1|2012/03/08|11:17:48||6010|5C29E77F||0|

And if you install to: "%_CSIDL_COMMON_DOCUMENTS%\My Path" then the
uninstall .log looks like this:

|004|C:\Users\Public\Documents\My Path
|006|_0000_|C:\Users\Public\Documents\My
Path\limit.ini|1|2012/03/08|11:17:48||6010|5C29E77F||0|

I would suggest to check the uninstall .log to see what the install created.

Friedrich

[NewsArchive]

Customer sent me this. I use %_CSIDL_COMMON_DOCUMENTS%\My Path in my script. So something changed
Documents to Documets. He could have typed it incorrectly, I copied from my email. This script code
to create first a main folder and then subfolder's works for both Server and Workstation selections.
It is set to "Always Install". So there must be a permissions issue or maybe a hardware problem on
his computer. Installed fine on my xp,win7/8 computers.

My script first creates a main folder then the subfolders. Then adds to the main folder the Shared
Resource and then Grant File Access.

I will get my customer to send me the uninstall.log

He has MS Essentials installed. I have been wanting to develope a script to adivse if MSS is
installed. I will send a test SB8 install to him to see how this will work for me.

Thanks for your help and your time spent testing. If only I could reply back to my customers as fast
as you do.

Jim