Plugin Installation Problems

[yachtvalhalla]

Both the Climatology and WeatherFax plugins are installed by default to the path C:\Program Files (x86)\OpenCPN. This might be true for other plugins?

But when installed to that directory they don't work with OpenCPN.

Attempting to direct the installation to the Plugin folder under OpenCPN installs an 'OpenCPN' folder there.

What is the correct procedure to install these plugins?

This may be a case of a 'loose nut on the operator control knob'.

Terry

[rgleason]

Paul, What I do is backspace at the prompt which brings up various opencpn installations, then I pick.

[yachtvalhalla]

Originally Posted by rgleason

Paul, What I do is backspace at the prompt which brings up various opencpn installations, then I pick.

Ummm ... it's 'Terry'

Which installation do you pick for the Weatherfax plugin?

For Climatology I have copied the .pi and .dll files into the Plugins folder to make it work. But that is very cumbersome for the novice.

The Weatherfax has other files that need to be installed, but I don't know where.

I would hope these can be made to do a seamless installation but that may be asking for too much?

Terry

[Hakan]

Terry..
Have you tried the installation packages at PlugIns for OpenCPN 4.2 and 4.4 | Official OpenCPN Homepage
For example "weatherfax_pi-1.5001-win32.exe" works fine for me at the default directory c:\...\program..........\opencpn.

[yachtvalhalla]

Originally Posted by Hakan

Terry..
Have you tried the installation packages at PlugIns for OpenCPN 4.2 and 4.4 | Official OpenCPN Homepage
For example "weatherfax_pi-1.5001-win32.exe" works fine for me at the default directory c:\...\program..........\opencpn.

AHA! Yes I am using that installation program BUT ...

Do you have the OpenCPN program version in a folder on the C: drive labeled 'OpenCPN'? i.e. C:\OpenCPN\OpenCPN 4.4.0

I have it installed as C:\OpenCPN 4.4.0 ... no intervening folder which is where it was installed by the OpenCPN installation program.

I suspect this is the problem ??

Terry

[CarCode]

First rule for any user nevermind which operating system is used:
Never install something in root folder which is C:\ for Windows systems.

Gerhard

[Hakan]

Terry
No I've OCPN at the default location, c:\Programfiles.....\opencpn\
But what if you change the plugin suggested location to the OCPN location you want to use like C:\OpenCPN 4.4.0\
But I also think Gerhard has a point. So why not only use the default location for OCPN?
Håkan

[yachtvalhalla]

Originally Posted by CarCode

First rule for any user nevermind which operating system is used:
Never install something in root folder which is C:\ for Windows systems.

Gerhard

Sorry .. finger fart! I meant C:\Program Files (x86)\Open CPN 4.4.0 which is where it was installed by the OpenCPN program. An intermediate folder was not created. Perhaps it makes a difference if it is a new installation or an upgrade?

BTW, shouting in bold did not add anything to your comment.

Terry

[Hakan]

Terry
re: "C:\Program Files (x86)\Open CPN 4.4.0 which is where it was installed by the OpenCPN program"
That I didn't know since I build my versions from source and always install them at the same location. (I've no problem switching between different versions.)

[yachtvalhalla]

Originally Posted by Hakan

Terry
re: "C:\Program Files (x86)\Open CPN 4.4.0 which is where it was installed by the OpenCPN program"
That I didn't know since I build my versions from source and always install them at the same location. (I've no problem switching between different versions.)

OK I understand we work in a different way. I try to emulate what the newbie encounters since I have over a hundred folks asking for help.

I just moved the OpenCPN 4.4.0 program to an intermediate folder (OpenCPN) on the C:Program....\ drive and it still doesn't work. Here's what got installed automatically. GRRR

Terry

[rgleason]

Terry, I am sure while you are installing, you take a moment to read the prompts and particular the one which says where it is installing. If that is wrong backup and try again.
Some plugins automatically add a directory so watch that too. You can also just let it install knowing where it is going and then move the installation to the right folder.

My win machine often has multiple versions, with the primary one at programfiles (x86)/opencpn and the rest of them at programfiles (x86)/opencpn4.0. Etc.

When installing plugins it usually wants to install to openpn so it just hit backspace and a list of opencp... choices come up.

I would clean up those loose opencpn and plugins of course at it creates confusion

[yachtvalhalla]

Originally Posted by rgleason

I would clean up those loose opencpn and plugins of course at it creates confusion

Already uninstalled the extraneous junk.

I tried making the target folder for installation the Plugins folder under the existing OpenCPN program. That doesn't work even after deleting the 'OpenCPN' folder it tried to create. What it did was create a Plugins folder under the Plugins folder! See image.

Screw it! Not worth my time trying to sort it out.

Terry

[rgleason]

Frustrating. Which plugin exactly? Do you notice slightly different behavior between plugins with respect to the install routine? Maybe this should be put into Tracker (with specific details) so that they at least perform the same way?

[yachtvalhalla]

I've discovered why I was having trouble installing the Climatology and Weatherfax plugins.

Somewhere along the line prior to attempting these plugin installations I had installed the OpenCPN program folder directly under Program Files (x86). Not sure why but that had been done.

Previously I manually created an OpenCPN folder between the Program Files (x86) and the OpenCPN 4.4.0 folder with the suspicion that was the problem since that was the default location for the plugin installation programs. The installations did not work correctly.

I have now uninstalled OpenCPN then re-installed it which created the OpenCPN folder between the Program Files (x86) and the OpenCPN 4.4.0 folder.

Both plugins installed correctly following the re-installation.

Sorry for the bother and thanks for the unnecessary help.

Terry