Palm crashes (with a message: Fatal Alert: DataMgr.c,
Line: 7025, DmWrite: DmWriteCheck failed) when I try to
rename a database to merge it with another
Un-repeatable bugs are the bane of my existance. I'm not
sure what to say here. I've attached the successful merge
that I performed, and I'll look into this and see if I can
figure out what happened. (DataMgr.c is in the PalmOS API)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks.
This happened with the previous version on a Samsung i500,
and now with the new version on both a Treo 300 and a
Tungstem E2 (this time error is in Line:8872). The touch
screen freezes, so one needs to use the pin, in all cases.
FYI: free memory is 5/16, 3.6/16 and 9.4/32M on these
devices respectively. The OS's is 3.5, 4.0 and 5.0.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm also experiencing odd behavior with database merges:
Palm Vx OS 3.5.0. Hard reset and installed Twinkle 1.0.1.
Create two databases and try to merge them:
Fatal Exception (no info). No confirmation question.
Requires pin-in-back reset. Both Databases still usable and untouched.
I've not found a work around. 0 cards, 1 card, multiple, all causes the crash. Renaming by itself seems fine.
PalmIIIe (OS 3.1.1)
This is weird. I can avoid the crash, but not forever.
The crash only happens if I have "deleted" cards in the database that I am trying to rename. e.g.
0 cards + 0 cards = 0 cards. OK
1 card + 1 card = 2 cards. OK
1 card + (1card + 1 deleted) = 2cards + 1 deleted
but
(1 card + 1 deleted) + (0 or 1) card = confirm merge? Then crash.
MemoryMgrNew.c Line 2982, Nil ID.
The databases have been merged, but is corrupted somehow and results in Twinkle crashing upon start.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
file 1
file 2 (I attempt to rename this db to heisig27)
Logged In: YES
user_id=1336289
Un-repeatable bugs are the bane of my existance. I'm not
sure what to say here. I've attached the successful merge
that I performed, and I'll look into this and see if I can
figure out what happened. (DataMgr.c is in the PalmOS API)
successful merge of 28-56 into 27
Logged In: YES
user_id=1012636
Thanks.
This happened with the previous version on a Samsung i500,
and now with the new version on both a Treo 300 and a
Tungstem E2 (this time error is in Line:8872). The touch
screen freezes, so one needs to use the pin, in all cases.
FYI: free memory is 5/16, 3.6/16 and 9.4/32M on these
devices respectively. The OS's is 3.5, 4.0 and 5.0.
Logged In: YES
user_id=1964573
Originator: NO
I'm also experiencing odd behavior with database merges:
Palm Vx OS 3.5.0. Hard reset and installed Twinkle 1.0.1.
Create two databases and try to merge them:
Fatal Exception (no info). No confirmation question.
Requires pin-in-back reset. Both Databases still usable and untouched.
I've not found a work around. 0 cards, 1 card, multiple, all causes the crash. Renaming by itself seems fine.
PalmIIIe (OS 3.1.1)
This is weird. I can avoid the crash, but not forever.
The crash only happens if I have "deleted" cards in the database that I am trying to rename. e.g.
0 cards + 0 cards = 0 cards. OK
1 card + 1 card = 2 cards. OK
1 card + (1card + 1 deleted) = 2cards + 1 deleted
but
(1 card + 1 deleted) + (0 or 1) card = confirm merge? Then crash.
MemoryMgrNew.c Line 2982, Nil ID.
The databases have been merged, but is corrupted somehow and results in Twinkle crashing upon start.