0 Members and 3 Guests are viewing this topic.
Yeah that would be cool. However, didn't the 9860SD only come out in Australia? I remember one model came out there only and if I remember it was the SD one. But yeah it would be funny if people used stuff like Firefox Portable on that.
executable assembly code can run without crashing! I modified the conversion app to accept some looping code and the calc finally doesn't crash. Everything appears to still be working, so my calc isn't bricked. * Qwerty.55 is happy
* Qwerty.55 thanks Z80 for clarifying how to defeat the 32 bit checksum.
Quote from: DJ Omnimaga on January 20, 2011, 12:49:26 amYeah that would be cool. However, didn't the 9860SD only come out in Australia? I remember one model came out there only and if I remember it was the SD one. But yeah it would be funny if people used stuff like Firefox Portable on that. The fx-9860G AU which only came out in Australia has a fx-9860G hardware (no SD card) but an OS which only uses 800Kb of storage memory instead of 1.5Mb.The fx-9860G AU+ is the same thing with a fx-9860Gii hardware (no SD card).
Well, DJ kind of ninja'd my Wabbit discovery, which I also coincidentally made last night On the other hand, I cracked the .g3m program format as well, so I'll stick with that. It's a very simple format, with three sections of security bytes that were slightly annoying to figure out. Here are the rules governing each of the sections. Numbers of the form 0xNNh refer to addresses offset from the starting address of the file while $NN refers to hex numbers.0x14h - 0x13h = $480x1C - 0x1Dh = $1D0x14h - 0x1Dh = $C30x13h - 0x1Ch = $5E0x0Eh + 0x48h = $72$38 - 0x48h = 0x1Dh0x48h = (Length of the rest of the data) - $3. There are always 13 00 bytes following 0x48h.Algorithm for computing the security sequences:$38 - 0x48h -> 0x1Dh$72 - 0x48h -> 0x0Eh0x1Dh + $C3 -> 0x14h0x14h - $48 -> 0x13h0x13h - $5E -> 0x1Ch0x00h through 0x0Dh:AA AC BD AF 90 88 9A 8D 8A FF EF FF EF FF0x0Fh through 0x12h:FF FF FF0x15h through 0x1Bh:01 00 00 00 00 00 000x1Eh through 0x3Bh:FF FE 50 52 4F 47 52 41 4D 00 00 00 00 00 00 00 00 00 00 00 00 01 73 79 73 74 65 6D 00 000x3Ch through 0x43h:8 byte ASCII code for file name.0x44h through 0x47h: 01 00 00 000x49h through 0x55h:00 00 00 00 00 00 00 00 00 00 00 00 00EDIT: I also wrote a program by hand to test it. Thus, I introduce the new Prizm programming language: Hex BASIC. All the complexity of Hex, all the power of BASIC
Oh I see. Wow, so they actually got fewer memory in Australia. X.x