Omnimaga
Calculator Community => Casio Calculators => Topic started by: DJ Omnimaga on February 01, 2011, 04:14:41 am
-
To track down which calculator batches got the Locate glitch with non-ASCII tokens, I think we should all post our calc serial number here along with other info:
(Serial number is on white label on the back of the calc)
Serial: 755AW0XMA005355
OS pre-loaded on calc on buying: 01.01.0200
OS 01.01.0200: Bug present
OS 01.02.0200: Bug present
If we notice a pattern, then this is IMPORTANT that those who plan to buy a Prizm ONLINE asks the buyer what is the serial on the back of the calc and if it's impossible, then not buy the calc, because otherwise it might be defective and contain the Locate glitch.
-
It might be a good idea to describe what the locate bug is and how to test it in case someone wants to check their calc.
-
Non-ASCII chars will not display properly. Far to the right of the screen they often don't appear at all until later, sometimes chars appears out of nowhere and colors are wrong.
-
Serial: 755AW0XMA005493
preloaded OS: 01.01.200
OS 01.01.200: untested
OS 01.02.200: Bug present
test program
For 0->A To 7
For 1->B to 21
Locate B,A,"€" ;any special char will work
Next
NextI'm guessing that the bug comes from special chars being 2 bytes instead of one. That might cause the OS to misinterpret them in its lookup table when drawing.
-
Serial: 755AW0ZMA020716
preloaded OS: 01.02.200
OS 01.01.200: Not present
OS 01.02.200: Bug present
-
Serial: 755AW0ZMA020716
preloaded OS: 01.02.200
OS 01.01.200: Not present
OS 01.02.200: Bug present
The difference between the X and the Z in the serial number looks interesting. So if your calc serial number has a Z in the seventh space "do not update your OS". And for OS 01.01.200 we still don't have a dump of that yet so once again "do not update".
-
Serial: 755AW0XMA005493
preloaded OS: 01.01.200
OS 01.01.200: untested
OS 01.02.200: Bug present
test program
For 0->A To 7
For 1->B to 21
Locate B,A,"€" ;any special char will work
Next
NextI'm guessing that the bug comes from special chars being 2 bytes instead of one. That might cause the OS to misinterpret them in its lookup table when drawing.
No, because when I change the character to an ASCII one such as a digit the program still remains 68 bytes large.
-
No, because when I change the character to an ASCII one such as a digit the program still remains 68 bytes large.
Actually no because program size is only represented as numbers divisble by four. I had one program that read 100 bytes (actually 97) It then took four ascii digits to add before the OS registered the program as 104 bytes. Then It took two special chars for the program size to increase to 108. So I think that means that ascii chars are one byte and special chars are two bytes.
-
Oh wow that's why then. This is weird ???
-
Probaly because the SH3 loads chunks of data in longword format. So if a program is 102 bytes the OS might fill the last two bytes with the BASIC version of the NOP operator.
-
Yeah most likely. Oh well at least it's not chunks of 16384 bytes like add-ins/apps on the 83+ O.O
-
Oops, I made a mistake:
Serial: 755AW0ZMA020716
preloaded OS: 01.02.200
OS 01.02.200: Not present
OS 01.02.200: Bug present
-
I'm not sure but I think any calc that had 01.01.0200 pre-loaded had the bug but not the others.
-
I have OS 01.02.0200 preloaded onto my calc and it does have the bug.
Serial Number: 755AW0ZMA017594
-
I have OS 01.02.0200 preloaded onto my calc and it does have the bug.
Serial Number: 755AW0ZMA017594
Hey a new member! And look he has a Prizm too!! ;D
What ever you do, do NOT download OS 01.02.0200 from Casio's website.
There are actually two versions of OS 01.02.0200, one preloaded on calcs (no glitch) and the one downloadable (glitched). You can tell you have the unglitched version because you have a 'Z' in your serial number.
btw are you are a Casio programmer/hacker because we could use some help in that area. Right now we only have about 5 members involved in this and it isn't enough.
-
There are actually two versions of OS 01.02.0200, one preloaded on calcs (no glitch) and the one downloadable (glitched). You can tell you have the unglitched version because you have a 'Z' in your serial number.
Unfortunately, I still have the pre-loaded OS and it definitely has the glitch.
btw are you are a Casio programmer/hacker because we could use some help in that area. Right now we only have about 5 members involved in this and it isn't enough.
I just got my Prizm about a month ago. Before that I had an 84+. Sorry, no prior Casio experience.
I'd love to help with development but my hands are tied right now (virtually all of my computer time is at my school and that is rather limiting).
For now, I have to stick to on-calc programming.
-
There are actually two versions of OS 01.02.0200, one preloaded on calcs (no glitch) and the one downloadable (glitched). You can tell you have the unglitched version because you have a 'Z' in your serial number.
Unfortunately, I still have the pre-loaded OS and it definitely has the glitch.
Maybe 01.02.0200 "new" was pre-loaded instead of 01.02.0200 "old"?
-
Thats what it looks like to me... :banghead: :banghead: :banghead:
-
I would love to help hacking, but reading ASM and the like causes my brain to melt, so I will probably stick to on-calc programming too. After all, that's what I did on the TI-83 Plus for 9 years. ;D
-
There are actually two versions of OS 01.02.0200, one preloaded on calcs (no glitch) and the one downloadable (glitched). You can tell you have the unglitched version because you have a 'Z' in your serial number.
Unfortunately, I still have the pre-loaded OS and it definitely has the glitch.
btw are you are a Casio programmer/hacker because we could use some help in that area. Right now we only have about 5 members involved in this and it isn't enough.
I just got my Prizm about a month ago. Before that I had an 84+. Sorry, no prior Casio experience.
I'd love to help with development but my hands are tied right now (virtually all of my computer time is at my school and that is rather limiting).
For now, I have to stick to on-calc programming.
Seems strange because qwerty's calc which was manufactured a short time after yours (due to the serial number) was preloaded without he glitch.
Also you could learn SH3 asm. As long as you know z80 asm Sh3 will just be a little harder. In fact when I first got my Prizm I had no prior Casio experience at all.
-
Yeah and a bunch of other people didn't have the glitch either, if I remember. Maybe his calc was part of a 3rd batch?
-
Also you could learn SH3 asm. As long as you know z80 asm Sh3 will just be a little harder. In fact when I first got my Prizm I had no prior Casio experience at all.
I do know some z80 already. I just haven't done anything with it at all due to lack of available time.
Yeah and a bunch of other people didn't have the glitch either, if I remember. Maybe his calc was part of a 3rd batch?
Maybe Casio discovered the glitch in the OS and fixed it before qwerty's calc was manufactured? If so, then why didn't they update the OS version number?
Edit: Here is my speculation on what happened in timeline form.
Serial #
755AW0XMA005355 (DJ's) These calculator had OS 1.01.0200 on it.
Casio updates OS to 1.02.0200 (glitched)
755AW0ZMA017594 (Mine) Now calculators have the 1.02.0200 (glitched) OS preloaded.
Casio catches the Locate bug and fixes it. However, they do not update the OS version number.
755AW0ZMA020716 (Qwerty's) By this point, calculators come with 1.02.0200 (fixed)
Casio releases OS on the internet. However, they upload 1.02.0200 (glitched) instead of 1.02.0200 (fixed)
This should mean that any calc with a serial # later than qwerty's should definitely have the fixed OS preloaded. With more serial #s we should be able to confirm this.
-
Oh, that might be that. Maybe some calcs got a fixed version of 1.02.0200, but for odd reasons Casio released the glitched version online. I don't know why they didn't change the version number, though...
-
There actually might be another problem here.
I was looking at the calculator memory through Insight and found this.
Address 0x80020020: "01.02.0000"
What does this mean? Do I actually have OS 01.02.0000 on my calc instead of the one it says it has?
It says the same thing at 0xA0020020 also (Isn't that supposed to be where the backup state is stored?)
-
I was looking at the calculator memory through Insight and found this.
Address 0x80020020: "01.02.0000"
What does this mean? Do I actually have OS 01.02.0000 on my calc instead of the one it says it has?
The last four digits are computed on-calc depending on some boot code information.
On the fx-9860G and all GII's it looks at 0x80000300 for this purpose.
-
On mine at 0x80000300 I see 37353541005AFFFF0000000000000000 (755A.Z ........)
Looking at my serial # now I can see that it looks like the first 4 characters of my serial # followed by that Z. (On DJ's calc I think it would be an X because his is older)
Would the 7th character on the serial # tell what the pre-installed boot code is?
-
On the fx-9860G the first four bytes are significant only.
Would the 7th character on the serial # tell what the pre-installed boot code is?
The boot code version (date) is stored at 0x8000FFB0 (again, on an fx-9860G).
-
Is it important to study the boot code version to figure out why this glitch happens? Isn't the glitch part of the OS?
-
Well, the boot code might contain information about the OS version that would reveal a way to determine which OSes have the problem. To be honest, I'm not sure I did the test correctly, so I'd like to see someone with a later serial number test theirs.
-
Serial number : 755DW11MA022115
Service ID : dpQGFKzx
OS version : 01.02.0200
OS time stamp : 2010.1122.2053
BIOS time stamp : 2010.0916.0917
Locate bug : PRESENT
-
Serial number : 755DW11MA022115
Service ID : dpQGFKzx
OS version : 01.02.0200
OS time stamp : 2010.1122.2053
BIOS time stamp : 2010.0916.0917
Locate bug : PRESENT
Is that a Prizm serial #? (I honestly have no clue since all of them I have seen start with 755A so far and I know next to nothing about Casio's products)
If so then where did you get the service ID and time stamps from?
-
Yeah it would be nice to know how to access that stuff easily, especially those with no knowledge about reading OS data. :P
-
Well... I expect that this information will come from the OS data.
If anyone wants to be able to read OS data (and the on-calc memory in general) from the comfort of their calculator they can download this add-in:
http://www.omnimaga.org/index.php?action=dlattach;topic=5610.0;attach=6267 (http://www.omnimaga.org/index.php?action=dlattach;topic=5610.0;attach=6267)
Its a basic hex viewer for the Prizm. You just follow the instructions provided and navigate to the address specified in order to report any relevant information (when those addresses are revealed-I don't know them).
-
If so then where did you get the service ID and time stamps from?
Press [OPTN]+[EXP]+[AC/ON] to turn on your calculator. Then press [F1] followed by [9].
- The Service menu displays the service ID
- The Version menu displays the OS version and the OS+BIOS time stamps (DateO+DateA)
-
Great!
Serial number : 755AW0ZMA017594
Service ID : 2sDQMK7V
OS Version : 1.02.0200
OS Time Stamp : 2010.1122.2053
BIOS Time Stamp : 2010.0910.1720
Locate Glitch : PRESENTI especially like the "Delete all data?" part of the first menu. :o
-
Thanks for the program m1ac4. I always forget add-ins are possible, lol. I'M probably so used to the Nspire not allowing third-party apps for 3 years. :P
And thanks for the tip cfxm. Here's mine:
Service ID: 12NOKKDt
OS version: 1.02.0200
OS Time stamp/DateO: 2010.1122.2053
BIOS Time stamp/DateA: 2010.0910.1720
Locate bug: PRESENT
Also there are some weird test options there O.O
-
Just to clarify, that was SimonLothar's program-not mine (I thought I would clarify that since I used a direct link instead of a link to the post itself)
Also there are some weird test options there O.O
I spent a long time playing around with those options yesterday. ;D My favorites are switching the display between 3 and 16 bits (for the test patterns and the amazing forest picture) and shutting off the backlight entirely (just to see what it looked like).
It automatically initializes the LCD settings after you leave the test menu but I suppose that is a good thing for now.
-
Yeah. I am certain some special effects could be used in games by changing these values. We better be careful, though.. And yeah I know it was Simon's program, I was thanking you for posting the link to it :D
-
I just got a prizm :D
service ID: khXQMK5x
OS version: 1.02.2000
OS timestamp: 2010.1122.2053
BIOS timestamp: 2010.0910.1720
bug: PRESENT D:
-
Congrats on your purchase!
-
Serial Number: 755AW0XMA008704
OS Version: 01.01.200
OS Timestamp: 2010.1005.1420
BIOS Timestamp: 2010.0910.1720
Service ID=KFGPKKR7
What? Mine came old???
How can i see that of the bug?
-
If so then where did you get the service ID and time stamps from?
[/s]nvm, got it. I guess emphasize "keep the buttons held down until something happens" :P
Press [OPTN]+[EXP]+[AC/ON] to turn on your calculator. Then press [F1] followed by [9].
- The Service menu displays the service ID
- The Version menu displays the OS version and the OS+BIOS time stamps (DateO+DateA)
For some reason I can't get that menu.. D: Where do I get to it from? the "homescreen", the menu? Do I hold F1 and 9 together?[/s]
Also what constitutes for Locate being glitched? I tried the code on the first page (tho having both loop going from 1-6, b/c 0 gave a domain err) and it worked fine, then I put "Green" in front of the Locate and only the left half of chars was green, the other black (until it ended, then it all turned green at once)...
I'm guessing that's glitched :P
Edit:
Serial: 755aw14ma072301
OS: 01.02.0200
DateO: 2010.1122.2053
DateA: 2010.0916.0917
Service ID: DbBEELI9
Has glitch.
Just bought it today.
-
You need to be in RUN-MAT mode. Locate being glitched is like if you try displaying a special chat such as the copyright symbol, sometimes it won't even show up correctly. However, maybe you don't have this glitch.
-
755DW13MA043730
Preloaded with 1.02.0200 with locate bug
Now with 1.03.0000 without lbug...
YAY!
-
Hey, i'm new to the forum
Here is my serial
Serial number : 755DW19MA120501
OS version : 01.03.0200
Model: CG20
btw, anybody could link me to some games to the prizm?
-
www.planet-casio.com/Fr/programmes/programme1856-1-gravityduck-pierrotll-projet.html (http://www.planet-casio.com/Fr/programmes/programme1856-1-gravityduck-pierrotll-projet.html)
-
www.planet-casio.com/Fr/programmes/programme1856-1-gravityduck-pierrotll-projet.html (http://www.planet-casio.com/Fr/programmes/programme1856-1-gravityduck-pierrotll-projet.html)
???
-
www.planet-casio.com/Fr/programmes/programme1856-1-gravityduck-pierrotll-projet.html (http://www.planet-casio.com/Fr/programmes/programme1856-1-gravityduck-pierrotll-projet.html)
???
That link is for me XP
-
www.planet-casio.com/Fr/programmes/programme1856-1-gravityduck-pierrotll-projet.html (http://www.planet-casio.com/Fr/programmes/programme1856-1-gravityduck-pierrotll-projet.html)
???
That link is for me XP
Oooooh Ok :)
-
Heya and welcome here dicamarques. :)
-
Thanks,
btw is there any tutorial for programming on the calculator? I've already tried to learn watching others programs source code.
-
Not that I know of, but I,m sure there are some FX-9860G tutorials that can be useful for PRIZM BASIC programming. For machine language there is http://prizmwiki.omnimaga.org/wiki/Main_Page and http://prizm.cemetech.net/index.php?title=Main_Page for now I think, but otherwise it might be best to check this forum area for more info.
-
How about casiokingdom.org? Last time I remember it was down, but it was a great website lots of games to download and you could learn from all these games on the website.
EDIT: Oh sorry I'm not sure if it has Prizm stuff. Hmm.. But there are still some nice tutorials.
-
Yeah, casiokingdom had problems (it's impossible to log in/register because the Captchas broke and can't be seen) last April, when the Prizm had only been out for around three months.
-
I think it's perfectly fine now. Just checked yesterday.
-
deleted