Author Topic: More PRIZM bugs?  (Read 18645 times)

0 Members and 1 Guest are viewing this topic.

Offline JosJuice

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1344
  • Rating: +66/-14
    • View Profile
Re: More PRIZM bugs?
« Reply #15 on: February 21, 2011, 05:38:43 am »
Now with the TI-Nspire CX they'll need to work harder or faster to fix the bugs, otherwise they'll have a bigger reputation of producing buggy products and people will go with TI calcs even more. X.x
It won't surprise me if people will buy the CX instead of the Prizm even if the Prizm isn't buggy... Just because of TI's monoploy.

Offline m1ac4

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 106
  • Rating: +8/-0
    • View Profile
Re: More PRIZM bugs?
« Reply #16 on: February 21, 2011, 07:21:41 pm »
Best case scenario:  Casio continues to try to bust TI's monopoly by improving their calculators and services.  TI tries to keep their customers with the same methods (that is to say, improving their calculators and services also) and in the end their competition will produce better calculators of higher quality for everybody.  (Or at least more frequent bug-fixes for the calculators that they already have).

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55942
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: More PRIZM bugs?
« Reply #17 on: February 23, 2011, 04:50:28 pm »
Yeah that could work. Personally I am not confident the Prizm will take over TI, but there will still be a decent userbase online. After all, the Casio community isn't that dead, because I checked Planète Casio and it was a bit active compared to all other Casio forums.
Now active at https://discord.gg/cuZcfcF (CodeWalrus server)

Offline m1ac4

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 106
  • Rating: +8/-0
    • View Profile
Re: More PRIZM bugs?
« Reply #18 on: June 06, 2011, 08:15:08 am »
I found another bug, this time dealing with sending programs to a .g2m memory file.
In order to make more space in main memory for the RPG that I was working on, I took most of my other programs and backed them up in storage memory.  However, I accidentally set output to g2m.  When I restored those programs to main memory I tried to run one of them only to have it draw badly.  Checking the code, I realized that the paramaters for the Text commands had been multiplied by 3 so as to look like this:
Code: [Select]
Text (169)x3,(180)x3,Str 4This was the only program in the memory file that used the Text command.  Its as if the OS did not convert the program when it was stored but assumed that it was when it extracted the program and multiplied the paramaters by three to make it draw properly.  Its really a minor annoyance but still a problem nevertheless.

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55942
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: More PRIZM bugs?
« Reply #19 on: June 06, 2011, 05:18:52 pm »
Oh this is not a bug, this is to accomodate the screen differences. Still annoying, though. I wish this could be turned ON/off
Now active at https://discord.gg/cuZcfcF (CodeWalrus server)

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: More PRIZM bugs?
« Reply #20 on: June 07, 2011, 01:24:06 am »
What it should of done was divide the coordinates by 3 and convert to an integer, but Casio isn't perfect :P
One thing to watch out for that I saw today was if you use an input make sure to close your quotes otherwise it will read the entire program as one line of text.

List of stuff I need to do before September:
1. Finish the Emulator of the Casio Prizm (in active development)
2. Finish the the SH3 asm IDE/assembler/linker program (in active development)
3. Create a partial Java virtual machine  for the Prizm (not started)
4. Create Axe for the Prizm with an Axe legacy mode (in planning phase)
5. Develop a large set of C and asm libraries for the Prizm (some progress)
6. Create an emulator of the 83+ for the Prizm (not started)
7. Create a well polished game that showcases the ability of the Casio Prizm (not started)

Offline AngelFish

  • Is this my custom title?
  • Administrator
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3242
  • Rating: +270/-27
  • I'm a Fishbot
    • View Profile
Re: More PRIZM bugs?
« Reply #21 on: June 07, 2011, 01:32:46 am »
On a related note, the routine responsible for displaying the hex in Simon's Insight appears to be the routine responsible for the Locate bug. From what I can tell in the source, that looks like a syscall named PrintLine().
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: More PRIZM bugs?
« Reply #22 on: June 07, 2011, 03:25:21 am »
On a related note, the routine responsible for displaying the hex in Simon's Insight appears to be the routine responsible for the Locate bug. From what I can tell in the source, that looks like a syscall named PrintLine().
So the plan of action will be too disassemble that call, find the bug, then write a program that modifies the flash and fixes it. Doesn't sound to hard ;)

List of stuff I need to do before September:
1. Finish the Emulator of the Casio Prizm (in active development)
2. Finish the the SH3 asm IDE/assembler/linker program (in active development)
3. Create a partial Java virtual machine  for the Prizm (not started)
4. Create Axe for the Prizm with an Axe legacy mode (in planning phase)
5. Develop a large set of C and asm libraries for the Prizm (some progress)
6. Create an emulator of the 83+ for the Prizm (not started)
7. Create a well polished game that showcases the ability of the Casio Prizm (not started)

Offline m1ac4

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 106
  • Rating: +8/-0
    • View Profile
Re: More PRIZM bugs?
« Reply #23 on: June 07, 2011, 07:35:11 am »
I hope that it isn't too hard.  Being able to use special chars in games would be really handy.  It would also be nice if the printline routine could be written so it ran faster.
As for using ending quotation marks, I think I have spent an inordinate amount of time searching through code to realize that all I did was miss one ".  Its unbelievable how much something like that can mess up a routine.

Offline JosJuice

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1344
  • Rating: +66/-14
    • View Profile
Re: More PRIZM bugs?
« Reply #24 on: June 07, 2011, 09:01:50 am »
On a related note, the routine responsible for displaying the hex in Simon's Insight appears to be the routine responsible for the Locate bug. From what I can tell in the source, that looks like a syscall named PrintLine().
So the plan of action will be too disassemble that call, find the bug, then write a program that modifies the flash and fixes it. Doesn't sound to hard ;)
Or maybe we can tell Casio about it? An OS mod wouldn't be very useful for this, since everyone who wants to play the games that we make would need to install it, which they might not want to.

Offline z80man

  • Casio Traitor
  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 977
  • Rating: +85/-3
    • View Profile
Re: More PRIZM bugs?
« Reply #25 on: June 07, 2011, 10:44:57 am »
On a related note, the routine responsible for displaying the hex in Simon's Insight appears to be the routine responsible for the Locate bug. From what I can tell in the source, that looks like a syscall named PrintLine().
So the plan of action will be too disassemble that call, find the bug, then write a program that modifies the flash and fixes it. Doesn't sound to hard ;)
Or maybe we can tell Casio about it? An OS mod wouldn't be very useful for this, since everyone who wants to play the games that we make would need to install it, which they might not want to.
It would still be optional. Sort of like the lcd fixer for the 84+. It would just fix some pre-existing bugs. Casio is already aware of this and they will hopefully fix the bug in the next OS update. But for now this could temporarily fix the issue.

List of stuff I need to do before September:
1. Finish the Emulator of the Casio Prizm (in active development)
2. Finish the the SH3 asm IDE/assembler/linker program (in active development)
3. Create a partial Java virtual machine  for the Prizm (not started)
4. Create Axe for the Prizm with an Axe legacy mode (in planning phase)
5. Develop a large set of C and asm libraries for the Prizm (some progress)
6. Create an emulator of the 83+ for the Prizm (not started)
7. Create a well polished game that showcases the ability of the Casio Prizm (not started)

Offline Dingus

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 129
  • Rating: +19/-6
    • View Profile
Re: More PRIZM bugs?
« Reply #26 on: June 07, 2011, 02:04:20 pm »
Yeah that could work. Personally I am not confident the Prizm will take over TI, but there will still be a decent userbase online.

Ti has the nspire cx and the nspire cx cas.  Casio has the Prizm and the ?  I think that when the ? is known then the TI and Casio offerings can be fairly compared.  Surely Casio is working on an improved version if its Classpad with color screen.  I am looking forward to what the Prizm CAS model will be and I suspect that it might come with some developer tools to.   

Offline JosJuice

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1344
  • Rating: +66/-14
    • View Profile
Re: More PRIZM bugs?
« Reply #27 on: June 07, 2011, 02:19:35 pm »
Yeah that could work. Personally I am not confident the Prizm will take over TI, but there will still be a decent userbase online.

Ti has the nspire cx and the nspire cx cas.  Casio has the Prizm and the ?  I think that when the ? is known then the TI and Casio offerings can be fairly compared.  Surely Casio is working on an improved version if its Classpad with color screen.  I am looking forward to what the Prizm CAS model will be and I suspect that it might come with some developer tools to.   
I don't believe that they're working on a color Classpad or a CAS Prizm... They don't really have any reason to do it so soon after releasing the Prizm, which was a huge step.

Offline Dingus

  • LV4 Regular (Next: 200)
  • ****
  • Posts: 129
  • Rating: +19/-6
    • View Profile
Re: More PRIZM bugs?
« Reply #28 on: June 07, 2011, 08:18:17 pm »
 
[/quote]I don't believe that they're working on a color Classpad or a CAS Prizm... They don't really have any reason to do it so soon after releasing the Prizm, which was a huge step.
[/quote]

Perhaps you are right but having completed the Prizm which is a non-cas calculator, what would be more appropriate for them to work on next?  The cx cas has a color screen and the Classpad does not so I believe that Casio has to address this new competition with a color screen cas model of their own and I suspect they will do so around the end of the year or early next year which is not that far off.  Am I missing something here?   

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55942
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: More PRIZM bugs?
« Reply #29 on: June 07, 2011, 08:43:54 pm »
I agree. Also the CP330 series is old. I think an update would be nice. It would also make it attracting for people who like the ipod touch style, since the classpad had a touchscreen.
Now active at https://discord.gg/cuZcfcF (CodeWalrus server)