just a few notes,per my own experience
I find that naming the text file to start OpenCPN
portable , ".cmd
" can work
better in some instances than ".bat
you find on win7, for instance, that "bat" or"cmd" doesn't work
All you have to do is open the registry (argh!)and deletete this key:
also per .cmd key
's fault but portable can be not-so-portable if you are wanting to open someone else's
machine up to hack the registry. sigh.
I found I wanted the "msvcp120.dll" and "msvcr120.dll" files also. OpenCPN
installs these on a "proper install" because Not every Windows machine has all the background system files required.(XP for instance?)
I even went so far as to copy all the wx widget files in too but I can't remember why I did this-!!! argh. It's been awhile since I did Windows) or if
the portable version on a usb stick will actually "call" on these if it doesn't find them on the host machine.
Try without the widgets I guess, but I'm really
sure the msvcp120 and msvcr120 files will be very useful to include.
Edit-add: per widget files it might
have been to run Windows O
portable on a Linux
machine via Wine. Probably did this to compare versions...or something like that!