BETA: PowerArchiver 2023 - 22.10.02

[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.