Omnimaga
Calculator Community => Casio Calculators => Topic started by: fxdev on May 25, 2011, 06:20:18 pm
-
Sometimes when I disconnect from USB, my Prizm will automatically reboot and reset all settings. So far, this happened about 10-15 times. I guess, this is some kind of file system bug, because I'm sending a lot of add-in files to my device - sometimes 5 at once and only with minor modifications (just to test some stuff).
Did anybody experience something similar?
My PC has USB 1.1, runs Windows XP SP3 and I'm always disconnecting via [AC/ON].
-
I haven't encountered this, but I usually only send one file at once.
-
I sent everything in a backup once (in other words, a whole main/storage memory's worth of files). I had no problems.
Usually when I try to terminate the connection with the eject option I always get an error message saying that "an error occured when attempting to eject". Despite that error ejecting always works.
-
Since I did a flash memory optimization, it no longer happens. So, this may have been caused by a high degree of fragmentation.
-
I didn't either. Maybe it was fragmentation. On the 83+ when the memory is fragmented, it takes a long while to move stuff to the flash.
-
It does sound like a file system bug. How much memory are you using? It may crash while trying to allocate the physical memory for the file.
-
How much memory are you using?
About 1 MB, but I often replace the same files with newer ones.
-
This is definitely a bug, because I can now reproduce it after a full device reset. :P
Just connect, replace the same file (but with a different size and timestamp) disconnect and repeat this for about 39 times.
After the crash your log file should look like this:
---- LOG INFO ----
[0]:USB PD, 79
[1]:VBUS DC, 77
[2]:VBUS DC, 75
[3]:VBUS DC, 73
[4]:VBUS DC, 71
[5]:VBUS DC, 69
[6]:VBUS DC, 67
[7]:VBUS DC, 65
[8]:VBUS DC, 63
[9]:VBUS DC, 61
[10]:VBUS DC, 59
[11]:VBUS DC, 57
[12]:VBUS DC, 55
[13]:VBUS DC, 53
[14]:VBUS DC, 51
[15]:VBUS DC, 49
[16]:VBUS DC, 47
[17]:VBUS DC, 45
[18]:VBUS DC, 43
[19]:VBUS DC, 41
[20]:VBUS DC, 39
[21]:VBUS DC, 37
[22]:VBUS DC, 35
[23]:VBUS DC, 33
[24]:VBUS DC, 31
[25]:VBUS DC, 29
[26]:VBUS DC, 27
[27]:VBUS DC, 25
[28]:VBUS DC, 23
[29]:VBUS DC, 21
[30]:VBUS DC, 19
[31]:VBUS DC, 17
[32]:VBUS DC, 15
[33]:VBUS DC, 13
[34]:VBUS DC, 11
[35]:VBUS DC, 9
[36]:VBUS DC, 7
[37]:VBUS DC, 5
[38]:VBUS DC, 3
I already informed Casio about it.
-
Great, you can have the even numbers...
-
Interesting find. If the flash is horribly fragmented, does the OS prompt to optimize/defragment it, or is it just silently failing? (Just wondering if the OS does this at all)
-
I think silently...
-
Interesting find. If the flash is horribly fragmented, does the OS prompt to optimize/defragment it, or is it just silently failing? (Just wondering if the OS does this at all)
On legacy models, you sometimes see a "Fragmentation ERROR". I didn't spot it on the Prizm yet.
-
I tried for hours to find an exact (and simpler) pattern to reproduce this, but I give up on this.
The OS is full of small little issues and I no longer have the patience and time to keep struggling with the Casio support, which seems to be unable to understand my technical reports.
I don't care what they do with the Prizm or fx-9860G.
Someday, I will throw away the entire OS and put a custom one on them. :P
-
Fragmentation Error... Never saw that!
Anyway, we should develop as fast as possible our own OS, just for the screen cap for example
-
I tried for hours to find an exact (and simpler) pattern to reproduce this, but I give up on this.
The OS is full of small little issues and I no longer have the patience and time to keep struggling with the Casio support, which seems to be unable to understand my technical reports.
I don't care what they do with the Prizm or fx-9860G.
Someday, I will throw away the entire OS and put a custom one on them. :P
I personally would not bother with them. When I e-mailed them once about the Locate bug, they were not even able to open a Youtube video to see a demo of the problem and they barely understood what I meant.
And lol a new OS would rule :D