OpenCPN Version 3.0.2 Release

[nohal]

Dave...
Did some testing. Changed the installer package to include and install msvcr100.dll and msvcp100.dll instead of including and running vc_redist.exe. Result is a smaller package which installs faster and runs on XP with SP2 or newer (confirmed).
It does not work on XP SP1 or earlier because of the runtime not working there (confirmed).
I would personally include this change in the trunk, but the decision is yours.

For me, the only thing that makes sense (by means of being worth the effort and time needed) to support older systems is to create VC2008 based build environment and do a (very slightly patched in the installer and libraries included) build (probably including the most common plugins to reduce the confusion on the download pages, which sure would come) advertised as "Package for legacy operating systems".

Cygwin is IMHO out of question - our codebase is perfectly portable, so there's no point in using a unix emulation layer, not talking about the problems you mentioned earlier.

Pavel

[sy_gilana]

Hi Pavel and Dave. You guys should not consider retrograding ever, you do enough work as it is. And great stuff too. All I need to know is: What does OpenCPN check before it bombs the installation. I will take my chances editing the registry, or putting null files with the correct filename in the right places. I am prepared to do the workaround until I find a newer 'puter, or change O/S to Linux, which is on the cards anyway...

[Jef & Marin, Netherlands]

OpenCPN's website states:
" it is not possible use the same port for all three of AIS, GPS, and A/P below, in Version 3.0."
Having this possibility is a long-standing wish of mine, and probably others. Could you tell me when you think this will be implemented?

Reason to require this:
I am using a Miniplex2-USB multiplexer for AIS, GPS and some other inputs, and output to the autopilot. The multiplexer has one USB, therefore AIS, GPS and A/P have to be on the same COM port.
Datarate of the NMEA signals of the multiplexer are configured in the multiplexer, so communication rate of openCPN over USB to the multiplexer (eg 38400) is decoupled from actual NMEA rate in/out of the multiplexer

[nohal]

Originally Posted by Jef & Marin, Netherlands

OpenCPN's website states:
" it is not possible use the same port for all three of AIS, GPS, and A/P below, in Version 3.0."
Having this possibility is a long-standing wish of mine, and probably others. Could you tell me when you think this will be implemented?

It's scheduled for this release cycle, the implementation should make it into the next beta.

Pavel

[Jef & Marin, Netherlands]

Pavel,
Thanks. Great! I'll install and try it, once it's there

[HappySeagull]

I like Pavel's idea for sure, because as it is, a full-install of O pops up in my firewall, which is unpleasant .

[bdbcat]

Pavel...

Why do we need VS2008 toolchain build if the manual install of msvcr100.dll and msvcp100.dll work OK on legacy systems?

Confused, again...
Dave

[sy_gilana]

Originally Posted by bdbcat

Pavel...

Why do we need VS2008 toolchain build if the manual install of msvcr100.dll and msvcp100.dll work OK on legacy systems?

Confused, again...
Dave

Is this all I have to do to make it work? I tried the MSVC++ install, and the OpenCPN installer still bombed.

What is OpenCPN looking for at install time? I'd rather hack it than ask you to re-write the installer...

[bdbcat]

sy_gilana...

The installer is using windows API GetVersionEx() to determine the SP level.

It may be possible to spoof this in the registry. Quick google shows some hits. Have a look.

Dave

[sy_gilana]

Originally Posted by bdbcat

sy_gilana...

The installer is using windows API GetVersionEx() to determine the SP level.

It may be possible to spoof this in the registry. Quick google shows some hits. Have a look.

Dave

Thanks Dave, I now have V3.02 running on Xp Sp 2!

Heres how, (usual disclaimers)
Open regedit, and navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Windows
Edit Key CSDVersion, Service Pack 2 has a value of 200
Change it to 300, save, restart and install V3.02

Thanks for the pointer...

[nohal]

Originally Posted by bdbcat

Pavel...

Why do we need VS2008 toolchain build if the manual install of msvcr100.dll and msvcp100.dll work OK on legacy systems?

Confused, again...
Dave

Dave...
msvcr100.dll does not work on anything older than XP SP2. If it's enough, we do not need VS2008 toolchain at all.

Pavel

[HappySeagull]

@sv_gilana- nice hack! My xp now reports itself as sp3! That can be useful!

[sy_gilana]

Originally Posted by HappySeagull

@sv_gilana- nice hack! My xp now reports itself as sp3! That can be useful!

Hi Happy, I would change it back to "200" after the install as the SP3 might flag automatic updates from Micro$oft that are not applicable to SP2....

[sy_gilana]

@ Pavel, @ Dave. Opinion...XP has 22% of the demographics out there.
SP1 and SP2 were released 11 months apart. SP2 was released August 2004.
I would say that its a safe bet to say that 95% of XP users are SP2 or later.
I watched the installation of 3.02 after the registry hack.
I would remove the MSVC from the installer, add the two files as Pavel suggested for a smaller faster install, or if there are Copyright issues, instruct users how/where to locate them. Then offer the Reg Spoof as a legacy system workaround for the 3 of us that are stuck on an old craptop until a better one comes along...

happy to be playing with 3.02, preparing for our next transatlantic end of year. Going to verify the Gibraltar harmonics as that is fundamental to a comfortable passage through the straits...

regards...

[sailorF54]

Originally Posted by sy_gilana

.

happy to be playing with 3.02, preparing for our next transatlantic end of year. Going to verify the Gibraltar harmonics as that is fundamental to a comfortable passage through the straits...

regards...

For tides in this area (Tarifa, Gib...), see my post
http://www.cruisersforum.com/forums/...ml#post1014780