Okay, that's weird.
I recently switched from a Palm Tungsten E device to a Tapwave Zodiac 2.
The Zodiac was an attempt to combine an advanced hand-held
multi-media/gaming platform with a PalmOS based PDA. It uses a 200 MHZ
Motorola ARM processor, with Garnet based PalmOS 5.27 OS, an ATI video chip
providing 320x480 SVGA, a Yamaha stereo sound chip, and includes built-in
Bluetooth radio. It has slots for two SD cards, one of which can be a WiFi
device. The Zodiac 2 has 128MB of internal RAM.
The manufacturer, Tapwave, is out of business and the device is no longer
supported, but that wasn't an issue for me.
With a few quirks due to a non standrd hard button layout
(http://static.flickr.com/33/44063955_beae02b4ca_o.jpg), everything worked
fine, including Plucker 1.8 Hi-res.
On the Palm Lifedrive, Palm implemented FAT32 file system support to handle
the 4GB internal hard drive the Lifedrive uses. A programmer figured out
how to patch the FAT32.PRC driver to get it to run on other devices, and
instruction were available on another board for getting it installed on the
Zodiac in place of the built-in FATFS driver. Among other incentives, the
FAT32 driver has better performance reading FAT16 cards.
I installed it, and verified the performance gains with VFSMark. Everything
worked fine, *except* Plucker.
I keep my Plucker documents (about 2,300 of them)in /Palm/Programs/Plucker
on a 512MB SD card. Any attempt to read a document on the card resulted in
a Cannot find document message. Rebuilding the Plucker document list did
not cure the error.
Every *other* application I have that accesses the card does not have a
problem.
After a bit of doing, I was able to revert to the built-in FATFS driver,
rebuild the doc list, and Plucker works again. What I don't understand is
why it had the problem in the first place.
One thing I noticed after installing the FAT32 driver was that the name of
the card changed from LEXAR MEDIA to External Card. Would the change in
volume name confuse Plucker? (I edited the VOLUME.NAM file to put it back to
what it was as part of the proccess of fixing Plucker.)
My PDA is mostly a Plucker engine, so a working Plucker is essential. I'll
live without the improved performance of the FAT32 driver. But I *am*
confused about what made Plucker unable to open documents on the card after
the change.
Comments?
__
Dennis
___
plucker-dev mailing list
plucker-dev@rubberchicken.org
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
