Are you using v.2.60? If you are, you probably forgot to install zlib (in v.2.60 an alert resource was missing from the English version, so instead of a warning dialog you got a crash).
Please update to the latest beta and/or install zlib.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a similar problem ... but it doesn't crash on the first send. The first send does nothing. When I choose "Send' again, it crashes.
It does not matter if I use the DiddleBug 2.60 included with Snapper, or the DiddleBug 2.90.3.b available here. They both crash, with (from CrashPro log) Preferences.c, Line:271, PrefDB Open Error" while running "DiddleBug 2.60" (or "DiddleBug 2.90.b.3") ... And while the first time I "Send" it does nothing, the Palm often will reset in a bit by itself when I don't do a second "Send".
I tried uninstalling and looking through both the saved and unsaved preferences using SysTool but couldn't find anything left over by DiddleBug (DIDB).
I always install the DiddleBug program (english) and the arm ZLIB, and unistall them both. I don't install DiddleSnap (altho I did at first) because I can't access the controls on the Treo600. Is this program required to make the "Send" work properly?
I also have a Sprint Treo600 w/ update 1.20,
and SnapperMail Enterprise 2.0.4.01
Any suggestions?
Thanks for your time.
Jack
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I used BackupBuddy VFS to back it up before I did that, and it was a quasi disaster ... LauncherX wasn't registered ... etc. Ikes! So I put the unsaved preferences database back on the Treo. Whew.
But I do remember (vaguely) what you were talking about. Long ago and far away I had (or read about?) a similar problem due to specific unsaved preference record(s) left over from a prior SnapperMail beta or some such (maybe some other app, I don't remember).
So I used PalmDump to dump the unsaved preferences and tried deleting one suspicious unsaved preference record at a time using SysTool. I finally found it.
In SysTool, the unsaved preference record shows up in the list as
After I deleted that record, Presto! Changeo! Fixo!
When I'm in DiddleBug v2.90.b.3, and viewing a drawing, and I choose menu / send, I get a listbox titled "PrintMe" with choices of:
Beam
PrintMe
SnapperMail
VeriChat
and when I choose SnapperMail, I get a new message with an attachment. YEAH!
Thanks for the pointer. And good luck with your Thesis! I also look forward to your next binary of DiddleBug.
Also: I'm willing to beta-test any builds you have before you post them. Just let me know.
Thanks.
Jack
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am experiencing a similar phenemonon occurrence on my Treo 650, but _only_ when utilizing VeriChat 2.58b as the "sending agent" (as opposed to Versamail, SnapperMail, messaging, etc.)
I am able to invoke VeriChat and send the picture to them, and get the modal box that says the transfer has occurred, but as soon as I hit 'OK' or the menu key, I am rebooted.
I'm not 100% sure this is Diddlebug's problem, but was curious to see if anyone else is experiencing this as an attempt on my part to try and decide where the problem lies (VeriChat or Diddlebug or maybe just the Treo 650).
Any commentary anyone has on this would be much appreciated..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My Treo600 crashes the second I try to send a diddlebug message via email.
I have the same problem. Instant crash.
Anyone have any suggestions?
Are you using v.2.60? If you are, you probably forgot to install zlib (in v.2.60 an alert resource was missing from the English version, so instead of a warning dialog you got a crash).
Please update to the latest beta and/or install zlib.
I have a similar problem ... but it doesn't crash on the first send. The first send does nothing. When I choose "Send' again, it crashes.
It does not matter if I use the DiddleBug 2.60 included with Snapper, or the DiddleBug 2.90.3.b available here. They both crash, with (from CrashPro log) Preferences.c, Line:271, PrefDB Open Error" while running "DiddleBug 2.60" (or "DiddleBug 2.90.b.3") ... And while the first time I "Send" it does nothing, the Palm often will reset in a bit by itself when I don't do a second "Send".
I tried uninstalling and looking through both the saved and unsaved preferences using SysTool but couldn't find anything left over by DiddleBug (DIDB).
I always install the DiddleBug program (english) and the arm ZLIB, and unistall them both. I don't install DiddleSnap (altho I did at first) because I can't access the controls on the Treo600. Is this program required to make the "Send" work properly?
I also have a Sprint Treo600 w/ update 1.20,
and SnapperMail Enterprise 2.0.4.01
Any suggestions?
Thanks for your time.
Jack
From what I've read elsewhere, I gather that the "PrefDB" error may have got something to do with SnapperMail instead of DiddleBug.
The solution seems to be to delete the Unsaved Preferences database.
The whole thing? Oy.
I used BackupBuddy VFS to back it up before I did that, and it was a quasi disaster ... LauncherX wasn't registered ... etc. Ikes! So I put the unsaved preferences database back on the Treo. Whew.
But I do remember (vaguely) what you were talking about. Long ago and far away I had (or read about?) a similar problem due to specific unsaved preference record(s) left over from a prior SnapperMail beta or some such (maybe some other app, I don't remember).
So I used PalmDump to dump the unsaved preferences and tried deleting one suspicious unsaved preference record at a time using SysTool. I finally found it.
In SysTool, the unsaved preference record shows up in the list as
HsMx MailExchange-HsMx
The content looks like this:
Creator: 'HsMx'[65532]
Program: MailExchange-HsMx
Size: 10 bytes
00 00 09 5F 73 65 6E 64 ..._send
00 00 ..
After I deleted that record, Presto! Changeo! Fixo!
When I'm in DiddleBug v2.90.b.3, and viewing a drawing, and I choose menu / send, I get a listbox titled "PrintMe" with choices of:
Beam
PrintMe
SnapperMail
VeriChat
and when I choose SnapperMail, I get a new message with an attachment. YEAH!
Thanks for the pointer. And good luck with your Thesis! I also look forward to your next binary of DiddleBug.
Also: I'm willing to beta-test any builds you have before you post them. Just let me know.
Thanks.
Jack
I am experiencing a similar phenemonon occurrence on my Treo 650, but _only_ when utilizing VeriChat 2.58b as the "sending agent" (as opposed to Versamail, SnapperMail, messaging, etc.)
I am able to invoke VeriChat and send the picture to them, and get the modal box that says the transfer has occurred, but as soon as I hit 'OK' or the menu key, I am rebooted.
I'm not 100% sure this is Diddlebug's problem, but was curious to see if anyone else is experiencing this as an attempt on my part to try and decide where the problem lies (VeriChat or Diddlebug or maybe just the Treo 650).
Any commentary anyone has on this would be much appreciated..