iGuidance 2.1 3D Crash

**Rundell** · 09-20-2005, 09:03 PM

Did you install all the device drivers?

**PURDooM** · 09-20-2005, 09:07 PM

Your using a full install of windows right? Not one of those crippled optomized versions?

**ddn** · 09-20-2005, 09:25 PM

No, nLite sucks. Full windows. I'm not trying to be a dick, but please realize that it WORKS FINE up until a certain point...more information on that here:

I can re-create the situation, and now FIX it 100% of the time? The fix? Delete the LastHead, LastLat, or LastLon registry keys. If these are deleted, iGuidance launches and/or switches into 3D mode with no problem. Obviously this is with the com port set to the wrong port (port the GPS is not on). Now, as soon as I change the com port to the correct port (basically LastHead, LastLat, and LastLon get written) CRASH. Instant crash. Like I said, I can re-create this situation 100% of the time.

Before you say its the GPS, I've tried a different one, and it gives perfect NMEA data that works just fine in 2D mode (until the random routing crashes). The problem is not the GPS, serial, or the NMEA strings.

And yes, I installed the god damn device drivers.

I am ready to flip out.

**PURDooM** · 09-20-2005, 09:48 PM

Don't mean to be an ***, but if its crashing when writing to the registry, does it have access too? I mean you are running it as administrator, right? (I don't see why you wouldn't but its hard for me to think of other reasons why it behaves like it is)

**ddn** · 09-20-2005, 09:53 PM

Yeah, its not like a user permissions problem. Keep in mind I'm not suggesting that it crashes when actually writing the registry key, I'm just saying thats when it happens. Much more likely is that some code for calculating position is vomiting. Perhaps a routine that is only called when drawing the cursor on the screen when in 3D mode.

By the way, creating the registry key ShowWarning and setting it to 0 is a much better way to get rid of the iGuidance nag screen.

**0l33l** · 09-24-2005, 03:48 AM

Originally Posted by ddn

By the way, creating the registry key ShowWarning and setting it to 0 is a much better way to get rid of the iGuidance nag screen.

It doesn't work for all versions

**grepzen** · 09-24-2005, 04:54 AM

regmon may give some insight 'bout what's happening in the registry.

http://www.sysinternals.com/Utilities/Regmon.html

**ddn** · 09-25-2005, 05:42 PM

The problem isn't the registry, its iGuidance taking a **** all over itself whenever it gets GPS lock.

**Rundell** · 09-25-2005, 05:47 PM

hmmm... I wonder if this has anything to do with the GPS receiver

Are you able to test with a different one?

**ddn** · 09-26-2005, 04:16 PM

Come on, at least read the thread:

Originally Posted by ddn

Before you say its the GPS, I've tried a different one, and it gives perfect NMEA data that works just fine in 2D mode (until the random routing crashes). The problem is not the GPS, serial, or the NMEA strings.

At this point I'm ready to RMA the EPIA. I'm convinced it is defective.