Fatal alert

[Frank]

I have all my files on a MS. After making categogies and putting several files in to several categories I got a fatal alert.
I happened right after closing a file.
The message was:

fatal alert dataMgr.c,line:7394,DmWrite:DmwriteCheck failed

I had to perform a soft reset. After this all the categories I made were gone. Two standard categories apeared : 'personal' en 'business'

I use latest beta version on Sony Clie PEG-NX60/U

I hope this helps.

[iSilo]

This problem has been reported by others as well, but so far, we have not been able to reproduce it. Do you have an exact specific sequence of steps that when followed, always causes the problem? In the file that you close when the problem happens, did you do anything in the document other than reading it, such as changing any of the settings, categorizing, changing fonts, etc.?

[alex]

there seems to be a bug with the categories... I just deleted the business category, and suddenly some previously categorised items just lost their categories. Are the built-in categories not supposed to be deleted?
Alex

[Voltage Spike]

First of all, you are hijacking another thread. :o

Second, what version are you using? There was a bug present in 4.05 until Beta 3 similar to the problem you are describing.

[alex]

I'm using 4.05 beta 3, precisely.

[Frank]

The things I did are:

- Created several dirs and sub dirs
- Put several files in dirs and sub dirs
- Changed the name of several files in the 'Clie file data management' application. I did this because they were very long names. I do not remember if I had changed the name of the peticular file of which the fatal alert occured
- I did not change fonts or did anything else ( I think ... ?)
- When my battery is low I can not read/write from my MS stick any more, what if this 'just' happened on the moment I changed categories and closed the file ?

I hope this helps killing the bug !
Keep up the good work and may force be with you all ...

[iSilo]

There is an updated beta that hopefully addresses this issue.

However, due to corruption of the iSilo settings database resulting from the problem, you'll need to delete your existing settings database for version 4.05 by going into version 4.05's document list view and using the Delete Special command in the list menu. In the Delete Special form, tap "Delete Settings Database". You will then be returned to the application launcher, where you can restart iSilo and it will build a new settings database as if though you started it for the very first time.