VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- Springboard Modules (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=10)
-- MiniLoader fatal exceptions (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=20816)

MiniLoader fatal exceptions

Hey all!

My Visor Solo died recently and I got a new Platinum. On the Solo, everything worked great with my MiniJam (am I the only one?!). MiniLoader, MJLoader, the MiniJam, and my Win2000 setup -- all good.

So I restored the Solo backup to the new Platinum and proceeded to download some tunes to the MJ. Everything but the new Visor remained unchanged.

Now I get the following error when starting up MiniLoader on the Visor:

quote:

---

../Src/FttDriver.c
Line:636
SysLibFind(usbLibName)
failed

---

quote:

---

The application associated with this button cannot be launched.

Please check the association in the preferences or assign a different application.

---

__________________
Cheers,
Rob Lund
The Rob Pages
[email protected]

may have answered it myself...

I think I answered my own question, though it raises another:

I tried my VisorPhone and it gave me a Fatal Exception error. So this is now two modules that don't work at all. So on a whim, I did an "Oh Crap Reset" (the power button + reset = erase all data) and started from scratch.

Now VisorPhone and the MiniJam work fine, and I'm uploading songs as we speak.

So my backup module image was bad or something. Maybe it contained too many hacks or crap from the Solo.

Oh, that brings me to another hypothesis. Yes, you read that right -- I went from a Solo (2MB) to a Platinum (8MB) with the same backup module. "How" you ask? Well, I hacked my Solo some time ago and replaced the 2MB internal DRAM chip with an 8MB.

That was about 6 months ago and until recently, all was well. But it died. But before it did, I was able to backup the Visor with the backup module. I guess the databases were just too screwed up by then.

You think?

__________________
Cheers,
Rob Lund
The Rob Pages
[email protected]

Actually, your problem was probably due to the fact that the Visor Solo uses Palm OS v3.1, whereas the Platinum uses 3.5.2. Your backup probably had some of Handspring's OS extensions for 3.1, which don't sit well with 3.5.2. This is something that happens a lot to people who upgrade from one of the older (and now discontinued) Visor modesl to the newer ones.

another error...

After syncing all my data and reinstalling everything, Visorphone is still crashing. The messaging program crashes. It gives me a Fatal Error message with some C function. Software reset doesn't work, have to do a soft reset.

The phone works fine, just the messaging doesn't. Weird. So, again, I backed up my data on a Backup module and did a hard reset and erased all data. The messaging program works fine, so it's not the hardware.

I then deleted some message records from SilverScreen, which is nice for displaying all the databases present on the Visor. This didn't help, unfortunately.

How do I know what data is corrupting the Visorphone messaging program? What's really strange is that this bad data is also coming from my Palm desktop. Because I synced it from there, not from the original Solo backup.

__________________
Cheers,
Rob Lund
The Rob Pages
[email protected]