Omnimaga
Calculator Community => Casio Calculators => Topic started by: DJ Omnimaga on February 13, 2011, 05:05:39 pm
-
It definitively seems that the Prizm has more bugs than we think. Some functions don't even work at all.
Here's the program I tried from the manual and a screenshot of what happens. SetG-Color doesn't appear to work at all. No matter if you use it with the right syntax, you will still get a Syntax error:
(http://www.omnimaga.org/index.php?action=dlattach;topic=6588.0;attach=6112;image)
(http://www.omnimaga.org/index.php?action=dlattach;topic=6588.0;attach=6113;image)
This was tested under fx-CG10/20 Manager PLUS and on a real calculator running the downloadable version of OS 1.02.0200.
Also there are still no news on the Locate glitch fix in the downloadable OS 1.02.
Someone will definitively have to do an OS patch or something when the calculator is jailbreaked.
-
What the hell is going on here. I swear that SetG-Color was working on my calc the other day.(No OS change since the other day). It is almost like some sort of Y2K bug. I have a gif posted but it is kind of hard to tell what is going on so I will explain it. Note: the program I tested using Plot/Line-Color which also used to work
1. you see a blank screen for a couple of seconds.
2. there is a flash from my school website. ([sarcasm]great now you all know where I go to school[/sarcasm])
3. You see the code for a prog that is supposed to draw text and lines in different colors.
4. I run the program and get an error.
5. For the rest of the video I angrly try to fix the program. :mad:
Notes: at the beginning of the program the first plot/line-color Blue does not generate an error, but the text from locate is still black.
Trying to draw text in this program now just generates errors, but the text command still works in other progs.
Sorry that the video is in black and white, I still need to figure out how to work calccapture.
(http://img.removedfromgame.com/imgs/PRIZMCOLOR.GIF)
-
/me sighs at Casio's error
I'll look through the OS, but I doubt I'll find anything.
-
I am trying to find the basic interpreter.
I think add-ins will play a big role in patching basic, and
give it some low level routines - like possibly peek, poke, Asm()
-
Sorry that the video is in black and white, I still need to figure out how to work calccapture.
I think in calccapture there's an option where you can record in 256 colors.
-
I am trying to find the basic interpreter.
I think add-ins will play a big role in patching basic, and
give it some low level routines - like possibly peek, poke, Asm()
lol. We definitely need ASM commands for BASIC. I may as well disassemble the entire OS while I'm at it.
-
Bsl this would definitively be a big plus. Doors CS7 and other apps have such BASIC extensions on the 83+ through parser hooks. I wouldn't be surprised if such parser hooks were possible on the Prizm. Some BASIC commands will need to be redone X.x
And yes, Asm() (both hex and prgm running support maybe), Sprite(), pxl-on/off/rectangle with no LCD update, an LCD update command, etc.
Z80man this sucks. Definitively Casio aren't much better than TI at fixing bugs, although so far I encountered no crash, unlike on the 83+ and Nspire.Sorry that the video is in black and white, I still need to figure out how to work calccapture.
I think in calccapture there's an option where you can record in 256 colors.
Yeah. I even posted a screenshot showing how to change options, but I can't find it anymore.
-
([sarcasm]great now you all know where I go to school[/sarcasm])
Yes, yes we do. ;-)
-
@DJ_O
Try "SetG-Color Green 1".
Edit: No, it is a bug. I have tested it with the emulator.
Seems as if the color commands are always expecting an additional argument...
-
Perhaps the ColorNormal or ColorLighter arguments?
EDIT: Actually it would be "SetG-Color <color> ,#" where # is the graph whose color you want to change (1-20). I just tested this and it works
It looks like the error is in the documentation of the command itself. :o
-
Well I tried that and the graph color went blue instead of green. ???
-
Blue??? What exactly did you type in as the command?
From what I know the statement SetG-Color Green ,1 should change the color of the first graph to green.
I tried variations on colors and graph numbers and they all worked as expected.
-
I typed the same things as in the manual screenshot above, but SetG-Color Green ,1 instead of SetG-Color Green.
EDIT: FOr some reasons it works now ???. I wonder if it just randomnly stops working...
-
EDIT: FOr some reasons it works now ???. I wonder if it just randomnly stops working...
I hope that it's not a random thing. If it is then Casio needs to fix that along with the documentation for the command itself.
-
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
-
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.
-
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).
-
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.
-
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:
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.
-
Oh this is not a bug, this is to accomodate the screen differences. Still annoying, though. I wish this could be turned ON/off
-
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.
-
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().
-
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 ;)
-
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.
-
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.
-
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.
-
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.
-
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.
-
[/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?
-
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.
-
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.
I wonder it they will come out with a color touch screen? That might be nice.
-
What would be nice is if they continued their trend of keeping their new calcs with the exact same GUI and interface as older ones. Someone switching from a 1996 CFX to a PRIZM would hardly have any issues getting used to the new calc, for example, because menus are similar. Of course they can improve stuff, though. More memory would be nice as well, although I wonder how much the ClassPad had...
-
USB is definitely bugged. It reset my calc when I attempted to disconnect a few times tonight,
-
Yes, USB is buggy: http://ourl.ca/11236/212655
-
Weird, I didn't have any issues. Are you sure that before disconnecting it you press ON/AC then wait until it finished loading and tells you to press EXIT? I do that everytime and never got a single problem.
One thing I noticed, however, is that when I drag'n'drop files on my prizm and they already exists there, it won't update them at all. When I go out of USB mode, they're still the same old files as prior trying to overwrite them. I have to delete them from the calc before resending updated versions.
-
Weird, I didn't have any issues. Are you sure that before disconnecting it you press ON/AC then wait until it finished loading and tells you to press EXIT? I do that everytime and never got a single problem.
No, it crashes WHEN you press the [AC/ON] key.
One thing I noticed, however, is that when I drag'n'drop files on my prizm and they already exists there, it won't update them at all. When I go out of USB mode, they're still the same old files as prior trying to overwrite them. I have to delete them from the calc before resending updated versions.
I do not have this problem.
-
Yeah, It will let me overwrite files just fine, but it will occasionally crash/reset when the AC/On key is pressed. There really isn't a warning either, because my Prizm had a ton of memory left.
-
Strange I haven't had any issues with that yet. I'm using windows 7 64 bit on a usb 2.0 port. Because some people are having more issues than others I assume it has to do with buggy driver software that doesn't work on all comps properly.
-
I'm using a Win 7 64 bit comp with USB 2.0 as well...
As for the driver, I'm fairly sure I'm using Casio's own drivers, because the Prizm installed them when I got it.
-
I haven't had any problems at all (except for when my calc couldn't be detected when using a TI cable >_>), and I'm using Windows XP 32-bit, with both USB 1.1 and 2.0.
-
Maybe different hardwares? ???
-
Maybe different hardwares? ???
The only real difference in hardware between Qwerty and I was the cpu manufacturer. I'm using AMD while he has Intel.
-
Ok, I wonder what could cause the USB bug to happen on some calcs and not others...
-
The "Prog Write" routine from the debug menu corrupts the file system:
http://ourl.ca/9404/220269
Some other file system options from the test menu may do as well...
Did you use such functionality, Qwerty.55?
-
Yeah, I used the flash write function several times.
-
Is that when the screen says NOR flash erase or is this something else.