VisorCentral.com - Issues with 8 MB Flash Module

VisorCentral.com >> Discussion >> Visor Related >> Springboard Modules
Issues with 8 MB Flash Module


	Post a New Thread \| Post A Reply

Last Thread Next Thread

Author

Topic: Issues with 8 MB Flash Module

imabug
Member

Registered: Jan 2001
Location: Misplaced Canuck in Charleston SC
Posts: 257

Issues with 8 MB Flash Module

Just got myself a Handspring 8 MB Flash Module v1.4 (one of the Office Depot clearance items) and have been happily moving things back and forth.

So far I've run into a few of issues.

First, my hardware setup:
Platinum 3.5.2H1.5
Hacks: Afterburner (only apps over/underclocked), Clockpop, McPhling, GreenlightHack, BatteryLog
used to use Launcher III 2.3b3, switched back to default launcher for debugging.

Every now and then when I'm moving stuff off the flash module, FileMover hangs. It's one of those pesky intermittent things that I haven't isolated yet. So FileMover hangs. No other message, nothing about compacting or anything else, and I'm forced to reset my Platinum. Then it reboots, and the flash module gets reformatted, wiping out everything I put onto it (thank goodness for that backup directory).

The second issue I've run into is that the sync process terminates prematurely when it tries to backup a file that used to be in RAM, but has been moved into Flash. I get this message in the log:

System synchronization failed
Protocol Error: Handheld file not found. (4003)
Now, I know that the sync process isn't supposed to backup the contents of the module, and I have no problems with that. However, with a bunch of the other files that I moved into Flash, Hotsync detected that they had been removed from RAM, and moved the files into the Archive directory as expected.

The third issue is that if I experience a reset while the module is in, I end up in a reset loop with the following error:

DataMgr.c, Line: 3362, Null dbID passed

which forces me to do a pin reset, since the reset button on the screen doesn't do anything. The only way I can get out of this is to pull the module out and reset.

So has anybody else run into these issues, or is it just me?

Aside from all this, the module works perfectly and has given me some much needed breathing room on my Platinum.

Thanks

__________________
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GS d-(+) s: a C++ UX++++V++S++ P+>+++ L>+++ E+>++ W++ N++(+++) o? K? w !O !M V-- PS PE Y+ PGP++ t++ 5++ X++ R+ tv++ b++(+++) DI++++ D+ G++ e+++>++++ h--- r+++ y?
-----END GEEK CODE BLOCK-----

01-10-2002 10:46 PM

MarkEagle
VisorCentral Staff

Registered: Dec 1999
Location: Connecticut USA
Posts: 2682

As for specific apps that do or don't run from the flash module, I can't help...

Not all apps can be run from the flash module. Some apps (especially older ones) are hard-coded to be run only from "memory card 0" (main RAM). Also, some apps want their associated data files in the same memory space as themselves... again, these won't work from the module. Lastly, no file that needs to be written to (data files) can be stored on the module.

__________________

God bless America, my home sweet home...

01-11-2002 12:01 AM

imabug
Member

Registered: Jan 2001
Location: Misplaced Canuck in Charleston SC
Posts: 257

ya, i'm aware of all of those. the problems i've been running into don't seem to be related what's on the module. not quite sure what they're related to.

I've figured out what programs will work and which won't on the module. I don't run into these problems running or accessing data on the module. it's just when i'm moving to or from the module, or if i experience a reset with the module in.

right now i'm experimenting to see if maybe it's a FileMover 1.4 vs HSUpdate 1.5 issue.

01-11-2002 12:20 AM

imabug
Member

Registered: Jan 2001
Location: Misplaced Canuck in Charleston SC
Posts: 257

Re: Issues with 8 MB Flash Module

quote:
Originally posted by imabug

The third issue is that if I experience a reset while the module is in, I end up in a reset loop with the following error:

DataMgr.c, Line: 3362, Null dbID passed

which forces me to do a pin reset, since the reset button on the screen doesn't do anything. The only way I can get out of this is to pull the module out and reset.

Well, after much file deleting and resetting, I've discovered the culprit behind this problem. Turns out that while one program I have, WordComp, works from the Flash module, the OS just doesn't like it when the Visor resets while WordComp in Flash. When WordComp is in RAM, the Visor is happy. I guess WordComp must hook into the OS in some funny way that causes this behaviour.

01-11-2002 12:58 AM