Pages: 1
RSS
Plungins and Voyager, How to use relative Paths?
 
Hi, everybody!
I am using Voyager on my USB-stick and would like to use plugins. Unfortunately Voyager save the absolute path (e.g. G:\Plugins). But it is the nature of a USB-stick that the drive letter changes, thus the plugin is not found.

So, is it possible to use relative paths?

Thanks
Sönke
 
you can use the DOS SUBST command to have one more fixed drive letter assigned to the stick (along with the random drive letter it gets when attached)

Pick a drive letter that will be surely free everywhere, like T:
Make the path T:\Plugins

Once you attach the stick and see its letter (say it's G:) , on the command prompt type
subst T: G:\

now you'll have a virtual drive T:\ identical to G:\, and the path T:\Plugins will be valid

To make it easier, put a .bat file on your stick with the following command

subst T: %~d0\

%~d0\ automatically expands to the letter of the drive on which the .bat file is stored, so it doesn't matter which letter is assigned to the stick

Make also a second .bat file with a command

subst T: /d

to remove T: drive when you're finished (nothing will be actually deleted). BTW SUBST's are not permanent, T: will disappear after a reboot even if you forget to remove it.

--
I don't use Voyager, but there should be a better way - can't believe app designed to run from a stick uses absolute paths.
Try \Plugins or .\Plugins first
Edited: bigg one - 13 September 2008 00:11:14
 
Thanks, that's a good idea. Sounds like cheating, but it seems to work .As long as meet a computer where the "surley free" letter is not free. On my computer at work "T:" is not free... :-))

Quote
bigg one writes:
I don't use Voyager, but there should be a better way - can't believe app designed to run from a stick uses absolute paths.Try \Plugins or .\Plugins first

That was my first reaction too. But if you want to add a plugins you have to select the path in a dialog an Voyager saves the absolute path. I have no idea where the path is saved, otherwise I would have tried to chance it manually.

Thanks again, but I still hope that there is a better solution...
 
you can open Voyager, change that path, save changes  and then check which file on the stick was just changed. Open the file with a text editor and see if you can find what has to be changed. You can also compare the file with a previously saved version, to see what exactly changed.
(but this will not help if the data in the file is somehow encrypted)

You can also save a couple of versions of that config file which store different abs. paths. Then automatically replace the active version with a one storing the current stick letter. Could be several other solutions too, more or less complicated.
But I think you should contact Ritlabs support with this question instead of looking for workaround 'hacks'.
 
actually the problem lies with the plugin mostly and not Voyager.
For example the Extended Macro Plugin (XMP) does not need its path stored in Voyager to work. Or one of the anti-spam-plugins (AntiSpam sniper) does also not need the full path mentioned but specifically asks whether Voyager is being used on installation.
Pages: 1