Decompression error #4 [Archive] - Indigo Rose Software Forums

jassing

03-07-2007, 12:23 AM

Leigh W

03-07-2007, 04:52 PM

I have a client that is installing to a virtual machine to test the installer I created for them.

On one file, everytime, he's getting a decompression error #4.

What can I do to solve this?

On the system, there is plenty of memory & disk space available...

Try this: Get your client to copy the installer to another folder on the virtual machine, e.g. c:\temp. Then run the installer from there.

Regards,
Leigh

jassing

03-07-2007, 05:00 PM

Try this: Get your client to copy the installer to another folder on the virtual machine, e.g. c:\temp. Then run the installer from there.

Already did that; as well as created a new hard drive to run it from; run it from teh host drive; log in as a different user adjust the amount of available ram and restart the system, reboot the host; run multiple copies to foce loading in different memory area.....
Each and every time.... same file.

File is identical (usin crc32 & md5 hash) to the one I have here.

Leigh W

03-07-2007, 05:18 PM

Already did that; as well as created a new hard drive to run it from; run it from teh host drive; log in as a different user adjust the amount of available ram and restart the system, reboot the host; run multiple copies to foce loading in different memory area.....
Each and every time.... same file.

File is identical (usin crc32 & md5 hash) to the one I have here.

I saw that message recently when testing installer on Vista + Virtual PC 2007, but ignored it. Sorry I can't suggest anything else.

Adam

03-08-2007, 12:46 PM

Unless you can replicate this on a non virtual machine there is not much I can suggest. We use virtual machines in house for some things but they are not always completely accurate.

Adam Kapilik

jassing

03-08-2007, 12:49 PM

Unless you can replicate this on a non virtual machine there is not much I can suggest. We use virtual machines in house for some things but they are not always completely accurate.

Adam Kapilik

I cannot -- but on this vritual machine it's 100% replicatable.

What does error #4 mean? Perhaps with some more info I can dig into myself

JXBURNS

03-09-2007, 09:32 AM

There was something with this particular .net assembly and Windows 2000 but its been so long since I used that I cannot remember what the reason was. Vaguely I seem to remermber it was trying to be self-registered but did not need to be.

What OS is the VM machine being used to host and what VM software is being used (VMWare, Virtual PC/Server etc?).

As you say would be nice to know what Error #4 does really mean.

John

Adam

03-09-2007, 11:40 AM

That error is the default error message when no other message could be set. So the unknown error part is accurate.

Adam Kapilik

jassing

03-09-2007, 11:48 AM

That error is the default error message when no other message could be set. So the unknown error part is accurate.

Well; at least for me; I've seen multiple "unknown" errors -- #4 & #5 come to mind as the common ones. I know I've seen others.

if "no other message" -- then what is #5? since #4 is "no other message" surely #5 then must have a meaning.....? See my point?

At what point in the code, ie: what triggers #4 ? because something triggers #4 and something triggers #5

jassing

03-09-2007, 11:52 AM

There was something with this particular .net assembly and Windows 2000 but its been so long since I used that I cannot remember what the reason was. Vaguely I seem to remermber it was trying to be self-registered but did not need to be.

Interesting - this is a dll but this dll is not being registered...

What OS is the VM machine being used to host and what VM software is being used (VMWare, Virtual PC/Server etc?).

HOST: winxp pro, virtualpc
VIRT: win2000 server
.net/both: 2.0 & 3.0

JXBURNS

03-11-2007, 05:45 AM

Interesting as it was Win2000 I remember was the cause of the DLL problem. As you stated it should not be registered but was attempting to be. I found this when I was using a rival package to SUF7. But then I moved to Win2003 server and problem never returned.

How about trying to run it under Virtual Server rather than Virtual PC? The VHD files should be interchangeable to some extent.

Rgds John

jassing

03-11-2007, 09:36 AM

How about trying to run it under Virtual Server rather than Virtual PC? The VHD files should be interchangeable to some extent.

Sadly; I can't tell the client to go install something different and "maybe it'll go away" -- he's hardfast that virtual pc is a perfect test environment, and "the installer you created fails testing".

-j

JXBURNS

03-11-2007, 11:39 AM

Yeah I know the sort. Is he using Virtual PC 2004 or the newly released 2007 version?

The latter certainly fixed a load of problems I was experiencing on the former although still does not support USB, hardware acceleration on graphic cards etc. Did fix the ability to install a Linux build I have been struggling with on VPC 2004 which was not something I expected in a Microsoft product.

John

jassing

03-11-2007, 01:01 PM

Yeah I know the sort. Is he using Virtual PC 2004 or the newly released 2007 version?

Just found out it's the latest vritual server....

Did fix the ability to install a Linux build I have been struggling with on VPC 2004 which was not something I expected in a Microsoft product.

Interesting that it now works -- I'd have expected the opposite; considering the 2004 version was close to it's purchase and linux worked on it before ms bought it....

JXBURNS

03-11-2007, 01:51 PM

the latest vritual server....

JUst to clarify did you mean Virtual PC 2007 or Virtual Server 2005 R2?

The official Microsoft statement is that VPC2007/2004 only supports Windows 2000 workstation, not server, whereas the VS2005 does support the server version.

Perhaps you could try that as a reason for him to try a different virtual environment. Not saying will help but at least one more thing to cross off the list.

Another way is for him to send you VHD file and see whether you have same problem. That is how I often work on problems with my colleagues so we are both working on exactly the same environment.

John

jassing

03-11-2007, 02:11 PM

Virtual Server....

I use vpc here & have no problems with running win2k server, 2003 server, NT4 server....

"officially" microsoft doesn't support "non ms os's" in either virtual pc or server....

JXBURNS

03-12-2007, 06:52 AM

True. I was thinking of the official line such as running VPC on top of a server host, such as Win2003, and expecting the guest client OS (eg XP) to be able to talk to the host at domain level. Certainly that is something I have had to use Virtual Server for although it does to work in fashion with VPC.

As for Linux yes not official in VPC but then their own staff use it to test applications written during the old DOS days. But still does not explain your original problem of course.

As a thought you may want to ask the question at http://blogs.msdn.com/Virtual_PC_Guy/ His items about Virtual Technology have been very useful in the past.

John