![]() |
Show 20 posts from this thread on one page |
VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- How To / Troubleshooting (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=2)
-- 8Meg Flash Module Update (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=2357)
I am planning to install the update to the 8meg Flash module but has a couple of quesiton before proceeding. In the readme file, there is a "extra" step to do (optional)... it reads:
Note: if you are updating in response to Fatal Errors when attempting to view the contents of the module from the File Mover... After the update, tap the File Mover in the Launcher and select Format Module from the Option menu...
My question is: are they referring to Fatal Errors when one try to view a database type file (pdb in Jfile, Doc), that gets updated and has been incompatible in the Flash Module, or are they talking about something else? I know I haven't been able to store pdb type files in there for this specific reason but would like to know if this is what they have fixed?
It also mention that one needs to reinstall all the "corrupted" files that caused the fatal error, but these .pdb files that caused the fatal error, when I move them back to the main unit, they seem to work fine.. does a reformat of the module erases the entire module then?
A few things:
*Make sure your Springboard doesn't already have Version 1.1 of File Mover in it. (Look at the sticker on the back, or tap on the File Mover icon, tap Menu, and choose Options/About File Mover.)
*What they are referring to is this: When you tap the File Mover icon, the screen shows you the contents of RAM (so you can copy/move to flash). If you tap where it says "Flash" or "Module" at the top right, it will either display the contents of the module or give you the fatal error message.
*Copy or move the contents of the module (apps, docs, etc.) to RAM (if you have room) before reformatting or installing the update. That way, these files won't get corrupted in the process. (Reformatting the module does clear it out.)
Thx for the explanation. Sorry if I am asking a redundant question but the point of the REFORMAT is purely for people who had the fatal error when the are viewing the Ram and trying to switch from module to internal? So bottom line is if I dont' get that error in that specific way, don't reformat it?
Also does the 1.1 update fix the problems with .pdb (Jfile/Doc files) not being able to be resident in the flash module for the respective reader to read?
| All times are GMT. The time now is 02:18 AM. | Show 20 posts from this thread on one page |
Powered by: vBulletin Version 2.3.4
Copyright © Jelsoft Enterprises Limited 2000 - 2016.