Maybe they want to make sure that OS 3.0 works only on boot2 3.0...
so keep your 3.0 copy save if you have on already.

ninja'd...

It should also be noted that a new boot 2 version is present in these files.  In addition, nspire_emu will not run the OS.

it doesn't run the new boot ether...

As a closing note, it is probably best to hold off on upgrading the OS on an actual Nspire until further testing is done.  As far as is known now, this OS very well might block downgrading/Ndless/countless other things.

It is actually clearly stated at the download page that downgrading will not be possible...
very nice from TI that now they at least give this warning.

Sorry if this a stupid question. But couldn't we just reformat a section of the flash memory(or whatever the correct term is)?

Quote from: Hot_Dog on March 31, 2011, 11:59:16 pm

http://education.ti.com/educationportal/sites/US/productDetail/us_nspire_cx.html?bid=5

"Features a dedicated programming environment as well as programming libraries for global access to user-defined functions & programs"

Is it possible that the Nspire CX will have a much better programming environment than before?  I'm sorry if this question had been asked, but I don't know

And by user defined, they probably mean teacher defined... for which you have to get a license and wear one of those little GPS ankle bracelets...

Or they mean the libraries as they are defined at page 403 of the Nspire user manual ...

confirmed. Works excellent now.

the limit seems to correspond to the point where the OS would actually start to display a mouse and not in any way, if "pressed" or not.
If it is good or not, depends directly from where you using it, for "porting" clickpad games it is probably low enough but I can easily think of scenarios where in may need more sensitivity.

But I think I have to take back

the "touch" is registered separate on the surface of this key, but only if the "key" is not pressed.

this misinterpretation origins from my habit to press the touchpad on its borders, where the proximity is much inferior to what it is half a mm more to the middle  (what probably also is the cause why isKeyPressed(***) sometimes didn't seem to work for me )

yes and no if you mean "machine code"(hex) with assembly then 2*yes
but if you mean with assembly something like
...
add r1, r2
mov r3, #4
ldr r0, [r1]
...
then no

What you describe is a long know error, basically everything works fine but this message.
And I think if ExtendeD knew what the cause is, he would upload a fixed version very quickly
What model of nspire have you between as this error seems to appear never to some people but always to others, so knowing on which hardware the error appears may help to find it (that's what I think at least).




@ExtendeD

Touchpad works fine so far, exept two things.

1) RIGHTDOWN is mapped to LEFTUP
here is the corrected line:
case TPAD_ARROW_RIGHTDOWN:
return report.y <= touchpad_info.height/TPAD_RATIO && report.x >= (touchpad_info.width * (TPAD_RATIO - 1))/TPAD_RATIO;
2) I suppose that since you haven't a Touchpad, you aren't aware of the fact that the touchpad does not only "react" on "touch" but also to "press" on the nine areas.
Actually that's how it is most used in normal OS function, and I think it would be very tiresome to "touch" it when you only want to navigate through a menu etc.
Now the touch will be sure useful in future games but the press is what, as far as I can say, corresponds to the up,down,left etc. keys on the clickpad.
I barely got that line above done so I fear that I can't help there but it would be nice if you add a test for "touchpad pressed".
My proposal is that isKeyPressed() tests for press and a other separate function tests for touch and returns the cords. ( I think that's what touchpad_scan() does but I'm not yet so far in the code)