Re: Portable Altap Salamander
Posted: 06 Dec 2009, 04:18
OK makes sense. I will start playing with standalone portables without the DLL and see if I notice any difference.
There is a tiny portable freeware program called finger weg (German, meaning "get your fingers off") showing you what is locking a file, offering to close down those locks, or even delete the file at next reboot. So far, it was very useful, stable and reliable. In several feature comparisions with other progs for the same purpose it turned out to have most features implemented.vld wrote:I don't think that is a good solution. I can't see installing application on someone elses system that is not needed. I can always kill the file after a reboot. I'd like to avoid doing that if possible.SelfMan wrote:Get Unlocker
I also run salamander from my thumb drive, where I've all applications in <ThumbDrive>:\PortableApps and made available with GeekMenu (improved PortableApps-Menu). As I often just quickly want to compare & copy/move files, I don't want to load a full-blown GeekMenu but just start Salamander. That's why I've the CMD in <ThumbDrive>:\ The CMD I posted is configured to that use case. The directory variable shall allow to once change the source at only one point and being done, and the relative path shall make it portable, i.e. independant of installation path.vld wrote:I finally got the chance to play with this. Here's where I see there is a problem:If you have to set the path in this file, you just cannot take the CMD file and drop it within the Salamander folder and make it a portable. What I do is carry Salamander with me on a thumbdrive and I may copy the folder to a desktop, D drive, or another location and then run it. If I have to have a variable, I need to edit the file each time. It really is not a universal CMD/application.
Code: Select all
rem Relative path to portable salamander directory (where portsal.reg and salamand.exe are). Do not add tailing \ set SalamanderPortableDir=.\PortableApps\SalamanderPortable
Code: Select all
Fine The advantage is that you only need to change a path once (where the set command is) instead of all locations where the path is used => less work for each user to adapt the paths to his/her needs, lower risk to have inconsistent changes (e.g. having a typo in only one of all the occurrences of one path may break the whole script as it does not find its own stuff any more). It's a very common method in programming.vld wrote:That did work [...] is there really a need for all the additional variables?
Code: Select all
for %%z in (salamand.ex?) do ( reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\app paths\%%~nxz" /ve /t REG_SZ /d "%%~dpnxz" reg ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\app paths\%%~nxz" /v Path /t REG_SZ /d "%%~dpzTools" )
Please excuse my ignorance as I haven't used scripts for a great long while.Georgd wrote:This is a really nice idea and very useful. I've worked through the code and made some changes that I wanna share with you; mainly it's improvements in avoiding and handling of errors. There are 2 TODOs that you might want to take care of And if you dislike to get status commands, be them pure information or errors, remove line 27 goto hide
Hi Jeff, that seems to be correct if your script is in the directory that also contains the directory Altap Salamander 2.5. You could also place the script in the root dir of your flash device and change the path in the quoted line to pint to your directory, e.g. set SalamanderPortableDir=".\Jeff\Programs\Altap Salamander 2.5" (the " are required due to the spaces in the path name). Cheers GeorgJeffin90620 wrote:I'm curious about the line
It seems that, for my application, the above script line should be changed to point to ".\Altap Salamander 2.5" (I copied it from Program Files without renaming it).
- set SalamanderPortableDir=.\PortableApps\SalamanderPortable
Once that is done, do I create a Shortcut pointing to the script and place it in the root directory of my flash drive?