0 Members and 2 Guests are viewing this topic.
TI-Bank has finally newsed about the bug with OS 2.1, which permanently freezes you TI-Nspire basic ClickPad if you've got boot2 1.1.http://ti.bank.free.fr/index.php?mod=news&ac=commentaires&id=882If you've owned your calculator for a while and allready installed OS 1.4 or newer, you probably have boot2 1.4 and aren't concerned by the problem.But if you've just bought your calculator, it may come with boot2 1.1...And when you connect it to your computer, that stupid TI-Nspire Computer Link tells you to install OS 2.1...Some minutes later, your TI-Nspire is totally useless.This is a major bug, and sadly, no english calculator site has newsed about it.We were too busy in july taking care of the downgrade protection...As Omnimaga is one of the most visited english calculator site, I thought you could make a similar news, as it is important to inform current/future Nspire users.
Will Texas pay you if it crashes your calculator forever?
Let's put the blame where it belongs - this is not a bug in OS 2.1; this is a bug in the old version of BOOT2.When BOOT2 1.1 has finished loading the OS, it calls the memset function, to clear the memory that was used to hold a copy of the TI-Nspire.cer file. But they mistakenly passed to memset the size of TI-Nspire.img instead. If TI-Nspire.img is greater than approximately 5800000 bytes, then memset ends up trying to write past the end of memory, so it crashes. OS 2.1 is the first OS large enough to make this bug visible.
I think I'll move this to news section. It's a shame that TI hasn't done anything about this, considering the amount of people who most likely ran into the same problemAnd yeah I was a bit busy myself at work so I've been a bit slower on news and I tend to take a few days before noticing some posts.Has this been reported to TI-(doesn't)CARES, btw?(Btw I edited the first post a bit so it fits news better and also fixed a spelling error on "already". I hope you don't mind)
Let's put the blame where it belongs - this is not a bug in OS 2.1; this is a bug in the old version of BOOT2.
Quote from: Goplat on November 05, 2010, 05:46:38 pmLet's put the blame where it belongs - this is not a bug in OS 2.1; this is a bug in the old version of BOOT2.Interesting.This also means that the boot2 update is installed by the new OS? This is the worst order.
So that doesn't happen with the 2.1 CAS because it doesn't have the TI-84+SE ROM and is a little smaller ?