At least for my bricked PRIZM's, you can totally rule overclocking out, since the last one broke with the exact same behavior that the other ones did, and I never overclocked it and only had a couple addins on it.

My personal theory is that each time I sent a broken calc in they either replaced it with one from the same batch, or they just repaired it and sent it back. It just seems like too much of a coincidence that all three broke the exact same way.

[quote="flyingfisch"][quote="merthsoft"]I think the bricking was almost exclusively due to overclocking, wasn't it? I think if avoid that (or addins that do that) you should be okay.[/quote]

At least for my bricked PRIZM's, you can totally rule overclocking out, since the last one broke with the exact same behavior that the other ones did, and I never overclocked it and only had a couple addins on it.

My personal theory is that each time I sent a broken calc in they either replaced it with one from the same batch, or they just repaired it and sent it back. It just seems like too much of a coincidence that all three broke the exact same way.[/quote]

Have you tried to request another replacement or were out of warranty or gave up on it now?

I tried to request another but since I got my calc free through the promo I had no proof of purchase. I am not really sure how it worked but from what Nathan Austin (Casio rep) said, it sounds like he was not sending me real replacements but was giving them away as "gift" calculators. And apparently he did not feel that he could send me any more, and he started to think I was breaking them by voiding the warranty.

I really don't understand the whole thing but since I am out of high school now and I still have an fx9750 (hacked though, so it is actually an fx9860), I just kind of gave up on trying to get another one.

Thanks for your kind help before.

I started fresh in C:\Casio folder, put original PrizmSDK-0.3 content there, then wrote over with https://github.com/gbl08ma/libfxcg. Copied libc and libfxcg into the projects folder and replaced first 6 lines of makefile for libc project so it looks like this now:

Code:


When I run make.bat for it I get the following error:


Code:


Please kindly help me with fixing this please

I do not use windows but I believe it means that it cannot find sh3eb-elf-gcc. Also you may need to end it with .exe so it will run on windows. To fix this set the path to contain the compiler. Just make a bat file that sets the path then runs make. It should work. Also you know you can google these error messages? That is what I did and I am now in effect writing a summary of what I just read.

Thank you very much. I assume you suggested to modify make.bat to the following:

Code:


It does move the things further I think but now I get the following errors for libc
Code:

and in case of lifxcg the following

Code:

I have tried to google those errors but cannot figure out anything from the search results I get. So sorry for being slow (and on Windows) - any help you can give will be very much appreciated.

I got stuck on the problems in the above post and in meantime decided to give libc.a and libfxcg.a a try from http://jenkins.taricorp.net/job/libfxcg/lastSuccessfulBuild/ Build #27 (Sep 14, 2014 8:33:08 PM). There were also examples attached with them so I decided to trie them out too - managed to compile and test HelloWorld, input, hourglass and progressbar ok but with starfield I get the following problem:

Code:

What could it be that despite of me not having a folder /home/jenkins/workspace/libfxcg/libc/ the libc.a refers to it multiple times above?

Please help to get setup with the binaries for windows any possible way you can - many thanks in advance.

Just a side-note: Keep an eye on the elf binary support for the prizm as this should, once it is stable, allow a much more complete libraries from being distributed and used with Prizm addins. The current issue preventing these libraries from being accepted for use is the linking clause. If shared linking is made to work, a lot of these missing headers and library code should be able to be used more widely.

Thank you all for your kind help. Can anybody recommend someone who would be able to help me get setup properly on Windows. So far I was able to only compile basic examples but as soon as I try any examples with TScrollbar (like scrollbar demo from INSIGHT project) or anything more advanced the compiler stops with errors like unknown type name 'TScrollbar' etc just to give one example.

Is there anybody who was able to compile more advanced add-ins on Windows and be willing to help me with this please?

Can you post the error you get with TScrollbar? I'm guessing that has to do with it not being typedef'd in libfxcg, it's just a matter of changing the code to use it in another way, but for that I need to make sure it's actually a type error.

Thanks for looking at this - here is the complete make.bat output and I can post a copy of the scrollbar demo code from INSIGHT too if you wish - many thanks in advance:

Code:

Try putting

Code:

in your code. That should let you use TScrollbar. Also copying code from Simon's INSIGHT (or any code not meant to build with libfxcg, for that matter) is not a very good idea as he uses a very different SDK, where even the syscall names differ.

Thank you very much for your help. I think my problem is that something like library binaries or some other parts are not working on Windows. If I put the above and even comment out other parts out I still get for that line "error: unknown type name 'scrollbar'" so I am very lost. I was trying many of your examples but kept getting compiler error similar to the above so went back to the HelloWorld, input, hourglass, progressbar and other simple examples which compile and run ok but anything more advanced like yours do not. Is this because I don't have windows versions of library binaries? Has anyone ever managed to compile those on Windows please? Or is it some other problem? Many thanks in advance