Quote Originally Posted by Neil View Post
I get a bit paranoid when the term clear and erase are used interchangeably regarding non-volatile memory btw. It can create the impression that they are one and the same, but it depends on context what's meant. The usual interpretation of 'clear nonvol' is in the sense of that which is done in the hidden menu accessible via the speedo, and that's relatively harmless, just a comprehensive hard reset if you like. Erasing rgn41 of NV is a big deal as you found out, particularly if there is no good or repairable backup available. It's a method of last resort generally.
So true, Neil! That's precisely the impression I got from reading the related threads, and the reason I so blithely went ahead with erasing my rgn41. The good news is that with kunix's assistance, my system seems to be fully functional and that, even in hindsight, erasing the NV does seem to be the only solution that would have resolved my problem.
Realizing that what's commonly referred to as "clearing" and "erasing" are indeed very different in their effects is precisely what led me to ask of a way to "clear" a non-bootable NV without resorting to erasing it.

Perhaps a thread with a "menu" of Nuvi issue resolution steps would be of help? It could list various steps be taken in the even of a problem, linking to the relevant threads for details. The steps could be listed along with their potential side-effects, arranged in the order of said side-effects' increasing severity. So, for instance:

1) BACK UP your NV / relevant file-system files [link to relevant thread]
2) Clear user data (all tracks, etc. will be lost. Can be restored from backup taken in step 1) [link to relevant thread]
3) Clear NV (side-effects) [link to relevant thread]
4) Delete GUpdate.GCD[link to relevant thread]
...
7) Erase NV (side-effects) [link to relevant thread]
8) Contact caty or kunix via PM [link to relevant thread]

Then responding to members' issues would consist mainly of referring them to the "menu" thread along with suggesting the items relevant to their problem. So for instance, for a non-booting 24xx, try 1&2, then 4, etc.
I realize getting a detailed response specifically tailored to one's problem greatly enhances readability for the asking member (particularly if she's new to online forums), but I think the "menu" approach would go a long way toward maintaining a cohesive troubleshooting framework. It would minimize duplication of effort and would greatly condense the sources of relevant information, facilitating searches. So for instance, if user MyGPSIsDead hits a snag with Step 2, he can post to the relevant thread and potentially benefit user GPSSOS who also needs to perform Step 2, despite the fact that user GPSSOS is experiencing entirely different symptoms and would never have found MyGPSIsDead's original thread.

My apologies if my proposal seems presumptuous, as I'm sure the veterans of this forum have far more experience (and success) with assisting members with their issues.