> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] > On Behalf Of Michael Nordstr�m > Sent: Thursday, February 13, 2003 5:38 AM > To: [EMAIL PROTECTED] > Subject: Re: Plucker bug or problem on my device? > > > So the next question is "What does Plucker look at > > when it's enumerating files during an update > > operation?" > > It loops through the files in the directory opening > the files, accessing the database info (e.g. the type > and creator ID) and it checks the returned error code > when available.
That's what I assumed. > If the *OS* crash when you try to open > a corrupt file then there is nothing Plucker can do > about it. Palm OS is quite robust, but it has some > very bad parts, too, e.g. there is a function called > DmWriteCheck that according to the API docs could be > used to check the parameters for a write operation > (bad input parameters to DmWrite will result in a > fatal error). However, if you provide the DmWriteCheck > function with "bad" parameters it will also crash with > a fatal error... The symptom I saw was just a Fatal Error, requiring a reset, with no hint as to exactly _what_ failed. > > If Plucker needs anything, it may be more robust > > error handling when it runs into a bad file. > > It has a quite robust error handling; some parts can > probably be improved, but the enumerate code is not > one of those parts. Also, if the OS crash instead of > returning an error code there is no error for Plucker > to "handle" ;-) Agreed. I don't know what caused the crash. If it was a condition Plucker didn't know how to handle, that's one thing. If PalmOS crashes, I agree, there isn't anything Plucker can do about it. > > unfortunately too likely for FAT formatted expansion > > cards. > > I have never had any problems with the CF card in my > TRGpro, so either I have been very lucky or the > TRGpro's CF handling is of a higher quality than the > Visor's CF implementation (after all on the TRGpro it > is built-in and not a later add-on.) I don't have a HandEra device, so I have no way to compare. I've heard complaints about non-standard VFS implementation in both the TRGPro/HandEra 330, and PiTech MemPlugs, but I don't know for certain. I've generally been happy with the MemPlug. The only application I run that has real problems with it is PalmReader, which is guaranteed to crash and burn if you try to categorize documents on a card. PalmReader keeps the category _in_ the document PDB itself, and crashes trying to write that data to the document when it's on the card. > /Mike ______ Dennis _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
