|
Hi,
Thanks MAHSTAH for the reply. I spent some time with my new 8Gb CF card and did a full backup as well as a PIM, just to get the hang of the system - easy enough. I've had great pleasure in deleting them as well. The A12 ROM, and I'm imagining the hard resets (numerous) have cleaned out the system and it is running quite well. I've yet to reinstall tomtom 6 though and get down to business with it.
I'd like to relate my update experience incase it helps other newbies to do it a little more efficiently that I managed to.
After Mahstah's reply I decided to make as full an activesync archive of my system as was possible. Activesync is both a blessing and a curse in the body of this update saga...
The exe from Dell is accompanied by some scant instructions that outline the sequence of events that should follow once the update is innitiated. It would be handy if these had a few more details regarding the HTML popup that launches the first 'handshake' with the axim.
For some reason my desktop machine has both Mozilla-Firefox and IE as browsers. Firefox was default and tries to take control of the process from then on. The issue is that firefox (this incarnation at least) insists on downloading to disc instead of running from site, as is required for the ROM update. O.K change default browsers for the HTML instructions...
After insisting, obviously, that an activesync connection must be established for the update to proceed the instructions say to close all programs on the host computer. It would be good for the instructions to include that this should also apply to activesync. It took 3 goes, with activesync closing by itself partway through the first handshake, and the system reporting a USB error and requiring a 'reset' of the axim (each time back to my old A06 ROM state, with activesync then trying to initiate a firstime sync with my newly reborn old system) and the Host as it has frozen and can't be woken by the presence of a USB connection. At least I cleaned out my desktop and resolved some other hardware issues while searching for a nonexistant host computer issue with the USB.
O.K, when prompted, this time, close all programs including activesync.
Things start to run through quite well with the 10min intervals passing uneventfully, until activesync wakes up again part way through a step and its screen obscures the warning not to use your partly complete system for fear that it will be rendered inoperable... A minor hicup, but could cause some grief unless some more details are provided in a help file.
Side stepping this one the rest of the resets go smoothly and the final screen asking to check the system info on the axim is a welcome sight. Ofcourse you have to go through the innitial setup pages and name your axim (as per the old incarnation) in order to get to the system info section, but it is indeed a welcome sight to see A12 proudly displayed.
Now activesync becomes more the hero and less the villan (my innexperience not withstanding). After renaming the axim to its old name activesync goes to work and puts practically everything back, but in a much more efficient fashion, so there must be less fragmentation or something. I had a small issue with a series of dates and appointments comming across from Outlook 2003, but it is easy enough to edit this on the host, with the axim connected, and it all clears up nicely.
Is there a maintenance utility that can help with this 'defragmenting' of the axim? I didn't realize how clogged my system had become prior to the hard resets.
I use a PDA because I have an issue with a focal distonia that prevents me from writing, but it's easy enough to copy and paste most of the info that is overwritten in the ROM update to a word mobile doc and then sync that to your computer. Network passwords are another story, but we all have our own methods of archiving and rediscovering these, not to mention helpfull IT administrators at work.
Thanks for letting me rave on about my first up ROM update. If I've missed any threads that deal with this I'm sorry to have taken up so much space.
Let's see if it has helped with the tomtom 6 issue, or if there is some USB thing here I need help in comming to terms with.
bye,
Shuei.
|
