Decompression Errors #4 and -200000032

[NewsArchive]

I've seen both these errors recently. Care to explain the significance
of these particular error numbers?

Mike Hanson
www.boxsoft.net

[NewsArchive]

Also, would it be too much to ask for these error messages to be more
informative. For example, rather than just getting an obscure error
number, it would be better to learn that it was "access denied". The
user attempting the install could more likely solve it themselves.

Mike Hanson
www.boxsoft.net

[NewsArchive]

Hi Mike,

> Also, would it be too much to ask for these error messages to be more
> informative. For example, rather than just getting an obscure error
> number, it would be better to learn that it was "access denied". The
> user attempting the install could more likely solve it themselves.

see attached screenshot.

Unfortunately, there are thousands of different error codes in Windows. The
common ones are in the help file.

Friedrich

[NewsArchive]

Friedrich,

> Unfortunately, there are thousands of different error codes in Windows.

Just include a copy of winerror.h with every install!<g>

--
Lee White

RPM Report Viewer.: http://www.cwaddons.com/products/rpm/
Report Faxing.....: http://www.cwaddons.com/products/afe/
---Enroll Today---: http://CWaddons.com

Creative Reporting: http://www.CreativeReporting.com

Product Release & Update Notices
http://twitter.com/DeveloperPLUS

Hydrogen, the only CLEAN fuel and the future of clean air.

[NewsArchive]

Lee,

>> Unfortunately, there are thousands of different error codes in Windows.
>
> Just include a copy of winerror.h with every install!<g>

If it would be that easy <g>. SetupBuilder makes use of quite a few
external components. All with its own set of individual error codes.

Error #4 tells us that it is a WriteFile error during the decompression
process. Error -200000032 tells us exactly where (and why) it happens in
the installer runtime code. The last part of the number (32) is (in this
specific case) the GetLastError code -- only this can be found in winerror.h
<g>. It's a VERY complex beast.

Friedrich

[NewsArchive]

Maybe a URL?

https://docs.microsoft.com/en-us/win...-codes--0-499-

--
Richard
--
Richard

[NewsArchive]

Hi Richard,

> Maybe a URL?
>
> https://docs.microsoft.com/en-us/win...-codes--0-499-

Yes, for system error codes this would work. But not for the error codes
from external components.

That's why we only have the common errors in the online help. For exotic
error codes, I have to start investigation and check the manuals (and pray
<g>). There are literally thousands of error codes - SetupBuilder makes use
of at least 30 components.

Friedrich

[NewsArchive]

Friedrich,

> Error -200000032 tells us exactly where (and why) it happens in
> the installer runtime code. The last part of the number (32) is (in this
> specific case) the GetLastError code -- only this can be found in winerror.h

I use something similar in AFE wrapping the Clarion errorcode with a
negative value such as -11000 + ERRORCODE() so I know what the error
is and where it occurred.

--
Lee White

RPM Report Viewer.: http://www.cwaddons.com/products/rpm/
Report Faxing.....: http://www.cwaddons.com/products/afe/
---Enroll Today---: http://CWaddons.com

Creative Reporting: http://www.CreativeReporting.com

Product Release & Update Notices
http://twitter.com/DeveloperPLUS

Hydrogen, the only CLEAN fuel and the future of clean air.

[NewsArchive]

Thanks, Friedrich. I understand the complexity, but that doesn't stop
the grumbling from my team members. <sigh>

Mike Hanson
www.boxsoft.net

[NewsArchive]

Mike,

> Thanks, Friedrich. I understand the complexity, but that doesn't stop
> the grumbling from my team members. <sigh>

Yes, I feel your pain <g>.

Perhaps a link to a list of (well known) runtime error codes could make life
easier.

Something like this:

https://www.setupbuilder.com/errorcodes.htm

Unfortunately, it is absolutely impossible to display the cause of a problem
in human readable form within the installer.

Friedrich