Creation of a U3 (portable) package
-
yes…yes…please…
-
what is the main difference between the standard pa and u3 version. Just curious as i can already use pa on a usb key.
-
U3 is emulating self contained system, once you eject it, all traces dissapear from host OS.
-
Here you go:
http://www.powerarchiver.com/test/release/powarc962u3.exeIt will be published later on the main pages…
-
Installation went just fine. Will be testing it tomorrow and report the results. :)
-
The installation couldn’t have gone smoother. I haven’t found a problem yet. The only thing that worries me is setting the file associations on the host computer. I’ll have to play around with this more tomorrow.
-
The installation couldn’t have gone smoother. I haven’t found a problem yet. The only thing that worries me is setting the file associations on the host computer. I’ll have to play around with this more tomorrow.
well thats the whole point of U3 version, that associations and shell extensions get removed properly…
-
i would guess everything is fine then? :-)
-
will development of the u3 package be on the same lines as powerarchiver desktop version. i.e as one version getts better so does the other
-
Yes, of course. As new PowerArchiver comes out, U3 version will come in at most 1-2 days after.
-
-
It seems that the Shell Extentions are not being removed when you exit the program. I have the regular version of PA installed on my system with Shell Extentions turned on. After running then exiting the U3 version, the context menu still displays 'PowerArchiver 2006 U3". The regular version of PA has also lost its file associations. I would have thought that PA U3 would save current system settings at startup and restore them when exiting.
-
It seems that the Shell Extentions are not being removed when you exit the program. I have the regular version of PA installed on my system with Shell Extentions turned on. After running then exiting the U3 version, the context menu still displays 'PowerArchiver 2006 U3". The regular version of PA has also lost its file associations. I would have thought that PA U3 would save current system settings at startup and restore them when exiting.
well, it does that actually. What OS are you using and what version of PA U3? I suggest that you try the latest version.
thanks,
-
Context menu should dissapear once you eject your U3 disk BTW, are you doing that or simply exiting PowerArchiver?
-
Win XP/SP2 and all of the patches from Microsoft. Both Desktop and U3 versions are 9.63.01. Even after ejecting my U3 the context menu still displays 'PowerArchiver 2006 U3".
-
Win XP/SP2 and all of the patches from Microsoft. Both Desktop and U3 versions are 9.63.01. Even after ejecting my U3 the context menu still displays 'PowerArchiver 2006 U3".
you have to eject it for it to do anything - if you simply close PA, it will do nothing.
With regards to not deleting U3 conext menu - does normal PA menu appear after you eject? If so, what happens when you restart?
It might be Explorer caching dlls which happens sometimes so only “cure” is restarting the explorer via restart (or closing and starting explorer.exe).
thanks,
-
I remember having an eject that failed. Perhaps this is what caused my problems. I reinstalled the desktop version to get the context menu sorted out. Now inserting the U3 and running PAU3 updates the context menu correctly. Ejecting the the U3 correctly restores the context menu.
Sorry for the confusion! :confused:
-
The same thing happened to me, I did the exact same thing as you did to fix the problem. Also thanks to Spywolf for helping understand the mysteries of U3…
-
Another problem I discovered is that after ejecting the flash drive, I lose the icons configured on the host system for associated files.
-
Another problem I discovered is that after ejecting the flash drive, I lose the icons configured on the host system for associated files.
PA returns associations as they were before (as long as you are using the latest version, we updated U3 version several times in past month).
Problem might be with icon caching in Explorer. Same goes with dll caching. Only way some of these things can be “fixed” is restarting explorer.exe or your computer.