12.00.49 Bug report

drteeth

I can reproduce this.

Open archive, click on extract, and try to click on the drop down MRU box. PA locks for 5-10 secs, then a black rectangle appears for a further 5-10 secs - it is the shape and size of the expected MRU list. Then the list appears and the rest of the extract box disappears. One is then left with the PA window with the extract box hidden underneath it.

The previous version (RC3?) worked fine, my 12.00.49 on my netbook is unaffected, just my main PC.

Patchbeam reported the update as the release version, but RC4 is available on the site. I need the previous version to be able to use PA again. Please let me know where I can get it from.

Tnx.

Guy

Socrates

I cannot reproduce this on either my desktop or laptop. Makes me think something else is clashing with this feature.

drteeth

@Socrates:

I cannot reproduce this on either my desktop or laptop. Makes me think something else is clashing with this feature.

Since rebooting this PC for something else, all is well. None of my other PCs (3) had this issue at all. Cancel the brown trousers <g>!

Guy</g>

spwolf

what AV do you use?

spwolf

we didnt do any changes that would cause this function to behave differently… but you never know… and also since we recompiled, some AV might have reset their pa.exe whitelist.

someone reporting PA starting slowly, but that also happened only once.

drteeth

I use eset NOD 32. As I said, all is well after a reboot…damn computers making me look like a schmendrick<g>. very strange.

guy</g>

drteeth

This post is deleted!

drteeth

Had to go back to 12.00.41 (RC3) as RC4 is totally unusable. So far, RC3 is okay. I did notice, with RC4, it took noticeably longer to the extract dialogue to appear after pressing ‘extract’ than with RC3.

Guy

spwolf

so what happens? What OS?

spwolf

maybe save your settings and send it over to us via support at conexware dot com. So we can try exactly the same settings.

And this happens only with extract window location MRU?

spwolf

also that suggests that MRU had some specific folder that for some reason PA did not like… do you use maybe network folders, network drives, removable drives, etc? anything similar that would cause you to think about?

drteeth

@spwolf:

so what happens? What OS?

Same as in my original message, Win 7 32 bit.

Guy

drteeth

@spwolf:

maybe save your settings and send it over to us via support at conexware dot com. So we can try exactly the same settings.

And this happens only with extract window location MRU?

Yes. All settings have been deleted as I could not do in inplace downgrade…had to manually uninstall first.

Guy

drteeth

@spwolf:

also that suggests that MRU had some specific folder that for some reason PA did not like… do you use maybe network folders, network drives, removable drives, etc? anything similar that would cause you to think about?

I thought of that but one moment RC3 was working, the next RC4 was not. Also, RC4 seemed to work one minute and not the next - the change happening after a reboot.

I have just ‘patchbeamed’ my RC3 to RC4 and all is well so far. MRU is empty so far and I’ll do some experimenting later.

Thanks

Guy

spwolf

just save that mru so we will see when it happens again… it happens only with the mru there, right?

drteeth

The problem is apparent the moment I click ‘extract’ as there is a delay before the dialogue box appears.

Only one setup has been affected, it is okay so far, will update if it occurs. Please let me know of the location where the MRU is stored.

Cheers

Guy

spwolf

just use options> save settings to a file… and send it over…

that way we have everything in case it is connected to another option as well.

drteeth

Will do.

Guy

spwolf

did you get it happen again?

drteeth

Hi,

No I did not…sorry for not posing earlier. I deliberately set a folder to my external drive in the MRU and them turned off that drive…no problems.

I’ll keep monitoring…

regards

guy

spwolf

patchbeam to .50.

We made some changes which we thought could optimize this… but we couldnt reproduce it, so it might or might not help :-)

drteeth

@spwolf:

patchbeam to .50.

We made some changes which we thought could optimize this… but we couldnt reproduce it, so it might or might not help :-)

Thanks. I cannot reproduce it now either (before the update) ;).

Regards

DrT