iGuidance 2009 and V 4.02 NOT WINDOWS 7 Compatible
Warning to all users.
I have traded notes with the official vendor of the Digital Rights Management Software (Nalperion) that is used by iNav on the above products.
Nalperion have confirmed that iNav have not upgraded their Nalperion for 2 major releases and their version currently shipping with their products IS NOT WINDOWS 7 compatible.
The real problem is, the products will install, AND APPEAR TO WORK, and then mysteriously fail.
DO NOT USE iGuidance (any version) until they specifically mark it as Windows 7 compatible with a warranty!
Here are the symptoms:
iGuidance will install properly --- however, the ancient version of Nalperion will work for a time.
However, Windows 7 uses a very sophisticated anti-piracy measure including periodically verifying its "Windows Genuine Advantage" status and confirming that your copy is legit.
Somehow, the old Nalperion is not set up to deal with the ongoing validation process by Windows 7, and after a while, for no apparent reasons, it will cause a hiccup.
Each time it "hiccups", the Nalperion verified install is fried.
Sometimes, you can start the program, but then it cannot be restarted again.
Other times, iGuidance cannot be started at all.
Worse of all, an attempt to "return" the license to iNav or "move" it via the SD card will fail.
The only way out is --- iNav can (at their discretion) reset the counter to allow another install --- however it is not known how long it would work even if reset.
At this time, I have narrowed it down to Windows Genuine Advantage generating a new encrypted key that Nalperion relies on. On the older versions, this key is "fixed". On the new ones, it is not.
One way the key can be trashed is if someone else has entered your Windows 7 "Product ID" on another machine, and the WGA notice that there are 2 activations on 2 different machines --- and it somehow, wipes out the validation data that Nalperion relies on and ask you to revalidate.
In any case, until iNav comes out with a firm, definite, confirmed and tested fix for this issue --- using iGuidance (any current version) is bound to get you into trouble eventually.