Bug extracting from ZIP etc using Extract here with PA 22.00.09

[PA_Fan]

When I attempt to extract a file or a selection of files from my zip archive, I receive error message:
Access viloation at address 005BB02E in module “powerarc.exe”. Read of address 00000000.
Can’t get beyond this.

Win XP SP2 on Dell Dimension

[spwolf]

seems to work here…can you provide more specific on what exactly are you doing?

Can you also try with some other file?

thanks!

[PA_Fan]

This happens whenever I attempt to extract files from an ordinary ZIP archive-either by selecting one or two (or more) or selecting all.
However, if I use the dropdown zip list on the extract button, then it will immediately extract all of the files in that archive, but without asking me where I want them to go and whether to keep folder paths etc.

The big problem is that every time I go from V2006 to v2007 and the problem arises, I then have to revert to 2006 to be able to extract my files. I then also have to re-enter a paid-up user code! This limits testing for the error somewhat.

[TBGBe]

@PA_Fan:

When I attempt to extract a file or a selection of files from my zip archive, I receive error message:
Access viloation at address 005BB02E in module “powerarc.exe”. Read of address 00000000.

This works OK for me both extracting selected files or CTRL-A :confused:
@PA_Fan:

However, if I use the dropdown zip list on the extract button, then it will immediately extract all of the files in that archive, but without asking me where I want them to go and whether to keep folder paths etc.

The drop down list selects the destination folder.
For me, it extracts with folder paths.

[spwolf]

We need a bit more specifics on how exactly it happens and what exactly are you doing…

thanks,

[PA_Fan]

I have removed PA 2006, and installed 2007 1000b6. I then open one of my zip archives (which work fine under V 2006) and select a file or group of files or all files to extract. So far so good.
Then hit the extract button, and encounter the error I mentioned at the outset.
I have downloaded the new version about 3 times and reinstalled it as many. I have also checked that there are no instances of the .exe running i.e. failed to unload.
As far as I can tell, everything else works and looks OK.

[spwolf]

can you send us one of the zips?

thanks

[PA_Fan]

@spwolf:

can you send us one of the zips?

thanks

Certainly-here is one (reduced by 1 item for upload).

[spwolf]

Can you please save your PA registry settings and send them to support @ conexware . com?

That way I will be able to test with same settings as you. I cant reproduce it with default settings.

thanks,

[welhaux]

spwolf & ivan: does the PA 2007 install force a user to uninstall older (pre-2007) versions first? What about even older versions of PA? Did they also force installation? If it turns out this is another registry issue, I’m wondering if this is happening because the PA 2007 installation leaves old, incompatible registry entries when it encounters them (i.e. the PA 2007 install finds that a key it needs already exists, so it goes ahead and uses it, without regard for whether the entries or permissions are valid or not). Maybe that’s why another poster indicated he found a bunch of orphaned PA registry keys he had to delete before his PA 2007 installation would succeed?

I’m guessing the PA 2007 installation routine needs to do a clean-up routine conditioned on the keys it’s removing having been created by a “major” prior version – that way PA does not indiscriminately remove keys and keep forcing users to reenter keys and reconfigure PA on minor updates.

[spwolf]

@welhaux:

spwolf & ivan: does the PA 2007 install force a user to uninstall older (pre-2007) versions first? What about even older versions of PA? Did they also force installation? If it turns out this is another registry issue, I’m wondering if this is happening because the PA 2007 installation leaves old, incompatible registry entries when it encounters them (i.e. the PA 2007 install finds that a key it needs already exists, so it goes ahead and uses it, without regard for whether the entries or permissions are valid or not). Maybe that’s why another poster indicated he found a bunch of orphaned PA registry keys he had to delete before his PA 2007 installation would succeed?

I’m guessing the PA 2007 installation routine needs to do a clean-up routine conditioned on the keys it’s removing having been created by a “major” prior version – that way PA does not indiscriminately remove keys and keep forcing users to reenter keys and reconfigure PA on minor updates.

no, it does not. It has nothing to do with pre-2007 versions, it doesnt know of them.

They were not orphaned keys, they were PowerArchiver file association keys.

Are you sure you are posting this question in correct thread?

[welhaux]

@spwolf:

…Are you sure you are posting this question in correct thread?

Yes I am. All that I’m saying is that, should this be another one of those registry-related issues, and the solution you implement involves cleaning out all old PA entries prior to an install, please remember to not b0rk PA settings where the install is merely for a minor version. ;)

[spwolf]

@welhaux:

Yes I am. All that I’m saying is that, should this be another one of those registry-related issues, and the solution you implement involves cleaning out all old PA entries prior to an install, please remember to not b0rk PA settings where the install is merely for a minor version. ;)

this has nothing to do with registry, nor we will ever clean out old PA entries on purpose, without good reason (which currently dont exist).

Good enough? :-).

Only reason I asked for registry settings is because it is easiest way to duplicate exact settings that are used in PA.

[spwolf]

@PA_Fan:

Certainly-here is one (reduced by 1 item for upload).

can you please send you PA registry settings zipped to support @ conexware . com ?

That way we can use same settings as you, since archive itself extracts fine here.

thank you!

[PA_Fan]

Sorry for delay in sending registry stuff to you-attached

[spwolf]

B10 should fix this, please check it out when it comes out (Friday probably).

thank you,

[spwolf]

please check in B10…

thanks

[PA_Fan]

Downloaded B10 Saturday am UK time. This problem has been fixed.
Thanks.