Dear Forums,
I added an additional drive to my machine. The new drive C:\ holds the Windows system partition and, of course, the PortableApps directory (C:\PortableApps).
The new drive C:\ is a copy or clone of the former system drive, which is now known as F:\.
Whenever I download and install a new PortableApp on my system, it wants to install into the old system drive F:\PortableApps, not the new C:\ location.
Could you please point me into a direction how to fix this?
Thanks alot,
NiM
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
What method are you using to install the PortableApps:
1. Using the built-in updater that comes with the platform 2.0 beta 5?
2. By choosing Options>Install a New App or Manage_Apps>Install a New App from the platform?
3. Just downloading and double-clicking the exe file?
Are you sure that the PortableApps menu you are starting is the one on the C: drive?
If F: is a clone of C:, and you have left copies of Windows and PortableApps on F:, it could be causing confusion. Have you deleted the old Windows and PortableApps from the old drive?
I made this half-pony, half-monkey monster to please you.
Hey solanus,
depends
I have not yet had the chance to try whether the updater shows the same behaviour, simply because no updates were released after installing the new drive.
I encountered the problem with method 3., just downloading and double-clicking the exe file.
I must confess that I do not use the PortableApps menu. I have linked the applications in my Windows start menu. However, of course, the links point to the C:\ drive.
Please let me know if you need more information. E. g. my operating system, it's Windows 7, 64 bit.
Edit: I have not yet deleted anything from the old drive. First I want to be sure that everything works correctly. However, anything else works except installing PortableApps.
Thanks,
NiM
I think Solanus' last comment is the key.
Rename F:\PortableApps to anything else, say F:\PortableApps-old or something like that.
I'm not inside the install programs, but if I have a USB stick plugged in with \PortableApps on it, that's what gets picked up, but if the stick isn't present, it defaults to my existing "local" subdirectory of C:\PortableApps
neutron1132 (at) usa (dot) com
When you just double click an installer, it searches all drives for a portableapps directory. Highest letter with one gets picked.
You could use the pa.c menu installed to c to do the installs and updates to make it easier and then just use the apps from windows regularly.
Sometimes, the impossible can become possible, if you're awesome!
So, I assume that's coded into the installer, with the assumption that the menu is installed on an external drive, and that the external drive would naturally have the highest drive letter?
I'd be interested to see what happens if you never install the menu and install all your apps to a different folder name.
I made this half-pony, half-monkey monster to please you.
You get just the default of \AppNamePortable which is not a valid install location, so you have to manually browse in order to install.
Before anyone asks why we don't use $INSTALLERCURRENTLOCATION\AppNamePortable, it's to avoid people accidentally just extracting it to their current location (often their desktop) when they mean to install it somewhere specific.
Sometimes, the impossible can become possible, if you're awesome!
yours and Neutron's hint did the trick. I renamed the folder, now everything seems to work perfectly.
Thank you!
As for swapping Windows around partitions, I used Acronis True Image 2011 to clone partition C:\ of my hard disk into an image file and restore it on a new partition on a Solid State Drive. This partition is assigned drive letter C:\, too, so everything works as expected, only 1.6 points faster in the Windows performance measurement than before
So in fact, there was no swapping. However, to make C:\ free for the SSD, I needed to rename the old C partition to F:\.
Thanks again,
NiM
The standard comment related to path/drive changes is:
PortableApps apps can and will handle drive letter changes without any problems, however changes in the path (using a different folder structure) may result in some PortableApps breaking. So, in other words if you just did a straight copy/clone and didn't change any folders around then this should just have worked. Something else has occurred.
Was your Windows installation on "drive F"? Because as far as I know, Windows absolutely does not like to be moved around from drive letter to drive letter. This may undoubtedly cause problems.
If you answer Solanus's questions then the community will be able to provide you with additional support.
Darkbee,
thanks; please see my answer in my post above yours.
NiM