paulrimmer

test123

If I could get the latest ibycus maps to support autorouting I'd dump City Navigator. On my Colorado 300 it fails to generate routes unless its using City Nav as the basemap.

Hi Dale, Should I hold off running an update for the latest road names/contours?

Great news Dale!!

hello world

So it seems that sometime this summer, we'll have road names for Alberta, BC, Nova Scotia and Yukon. w00t!

The creation of the registry keys is (intentionally) the last step. This is so that if mapupdate doesn't finish, it won't corrupt your mapsource install. Given that you're using just a subset of the IMGs, you probably don't want my TDB and IMG files anyways. You'll likely want to use something like MapSetToolKit to load them in to mapsource. (Haven't played with this much myself, but it doesn't seem too tough...) If you have trouble, drop me an e-mail and I'll see what I can do. Dale No worries, I'll copy all of the IMG files back onto the laptop, run the update to get the registry items then delete the IMG files I don't need to free up my limited HD space. I'm installing this on friends machines as well so I'll just use my main machine to keep up to date from your server then copy the files from there for a speedy install.

I just rebuilt my old 5GB HD laptop for speed and diskpace (nLite is a great package!) and was trying to just copy a subset of the IMG files over for Sask West. I did this and ran the mapupdater then killed it after it started downloading IMG files. Unfortunately it didn't create the registry keys like I was hoping for. Does it do this after downloading all the files (which I don't need)? Any chance of an updated regfix?

When was this version of MapUpdate downloaded? (before or after my revised 'I've found the problem' post) I just uploaded yet another new version. If you delete the families\NTDBData and Products\NTDBData Key, and then run this new version, it should put the right stuff in the registry. (the ID key should be 0x01F5 and it should be a Binary value and not a DWORD). It was late last night after that post. OK, I just downloaded and ran your new one after deleting the registry stuff and a single img. Now the paths don't have the extra '\' anymore and ID is a binary of value "f5 01". I'm assuming that matches your 0x1f5 as mapsource seems to start up OK and let me use the maps. Thanks for the great work!

Nope. Figured it was best not to go mucking about deleting registry settings on someone else's machine if they already existed (even if I put them there in the first place). If you want it under Families though, just go ahead and delete the key under products and re-run MapUpdate. I'm pretty sure I found the bug. No idea how it was working for me when I tested it (it was writing one of the keys as the wrong type). I think maybe I didn't save my code at one point and lost something. It should work for a fresh install now. Yep, had the same problem. Downloaded the new one and it creates a families folder in the registry however when I run mapsource it barfs on the ID key. ID is a double word and its set to 0xfffff501. Any idea what it should be? For now I'll just run that reg file again and delete the families folder. P.S. The paths for IDX and MDR had an extra slash after "Program Files".

lol! I don't remember where the bar was. I need to install it on another laptop so I'll pay attention. It did tell me it was a fresh install. Just installing on another and the progress bar is on the top and it did say fresh install again. Downloaded this one just now vs. the other day for the original attempt on the different PC. Cheers, Paul

I downloaded your latest updater this morning and did a fresh install. Couldn't see the maps in mapsource at first, then noticed that the installer didn't update the garmin product/registry entries. Ran your regfix and all is well. Great work!