By the way I heard the TI-Nspire CX will not be sold in France. Only the CAS CX will.

Do they do this for the normal Nspire too? If they do, the 84+ emu will become completely unavailable...

Or are they stuffing extra protections into the OS in response to TNOC breaking the anti-downgrade protection and the discovery of Lua?

This.

And I think they might be testing it a lot too, to avoid new problems...

I updated the link with new content.  It now includes a few working ROMS.  See the link at the end of the first post.

As you probably know, posting copyrighted ROMs is illegal.

(This also applies to copyrighted videos/music/stuff )

JosJuice, assembly programs will run at 6MHz by default on every calculator model. They are fully capable of running at either 6MHz or 15MHz on the 83+SE and newer, as chosen by the programmer.

Yes. What I was saying was that there was no way for the shell to prevent programs from running in 15 MHz.

Quote from: Qwerty.55 on May 08, 2011, 02:44:42 am

I've decided that a slight change of name is in order. The project is now officially the Khavi Virtual Machine Framework.

This name change is prompted by the fact that I have now added support for the instruction set of the Lua virtual machine. This will be included in the default release and will allow the framework to emulate both stack based and register based virtual machines.

So is Khavi a random name you invented?

Khavi means coffee in some language (I don't know which one), and coffee = java

The Prizm is coming up, but there is hardly any casio fx-xxxx development.

Hey, the Prizm is technically an fx- calc too
It's named fx-CG10 or fx-CG20 depending on your region.

First, I would like to thank Tari for his icon creation and extraction tools which helped me a lot when creating this topic, and everyone else involved in Prizm hacking for allowing us all to be able to do what we can do with the Prizm right now.

Icons are a part of Prizm add-ins that are usually considered unimportant. They don't affect the add-in itself, but it's still a good idea to create a nice set of icons for any program. Users will see it even when they aren't running the program, and if the Main Menu is full of icons that don't adhere to a few guidelines, navigating the menu can be confusing.

Style
The object that's the main focus of the icon shouldn't take up all of the 92x64 pixels that it has access to. It should generally be a bit smaller since the background and other elements also need a bit of space. The official icons from Casio are somewhat colorful, a bit 3D-looking, have shadows and are slightly translucent. You can follow the style of these if you want to, or create your own kind of icon. 2D sprites usually work fine if they aren't too similar to the backgrounds.

Example icons:


Selected/Unselected
In all add-ins, two icons must be provided - the selected icon, and the unselected icon. The two icons should show the same objects with different backgrounds - not objects that are completely different from each other or the same objects with minor variations. There is one exception, though. When placing text in the icon (this should only be done in special cases, not for writing the name of the add-in!), the text in the unselected icon should be white with a black outline and the text in the selected icon should be black with a white outline. Run-Matrix and Equation are examples of this. The unselected icon needs to have a pure black background, and the selected icon needs to have this background:



If no custom icon has been made for your program, the background with nothing on top of it should be used for the selected icon. Never make the selected icon pure black!

Areas drawn by the OS
The Prizm OS is a bit unusual when it comes to icons, as it draws on top of certain areas. Those areas are marked in red here:



The square on the top right area of the icon will always be completely unseen, and anything important shouldn't be placed there. However, hiding defects or other odd things there is not recommended, since some users might use something other than the OS to view the icons. The larger area on the bottom is where the name of the add-in will be placed. The main focus of the icon shouldn't be under it, but the area won't be completely covered, so things that aren't very important can be placed there. For example, a small part of the ruler in the icons of Conversion and Geometry is placed there, and an unimportant part of one of the images in the Picture Plot icon is also placed there. The name of the add-in should never be included in the icon since the OS takes care of including it.