Lol, there is an actual bcall?
I must have accidentally done that one time.

That is too bad that they just made them "ret". 

They also added pointless loops to the display command, and now it's slower than a snail.  (and I thought that MP was slow)

Quote from: DJ_O on April 01, 2011, 05:33:06 pm

Wait? Hooks got removed too?

Well, the bcalls to set up the hooks were removed, so any program/app that uses hooks needs to be modified a little.

Ah weird. X.x

I wonder if they removed anything else...

The last day of work thing could be possible, although I think if it's something like that it would probably instead be a teacher who hates calc games who visits calc forums or Google groups and in revenge to the rants about TI lately he could have made some sort of prank or something and upload that modified OS.

This is  the  funniest  April  Fool's  Day  joke I've seen  in  a  while!

I can't believe you  all  are  believing  this.

But the thing is, it was posted, and it was real, at least for a few minutes. What we are unsure of is if they are actually going to release this OS, since TI killing ASM support is not out of the question.

Here, Goplat found this in the new text routine:

ld b,$1E
ei
halt
djnz $-1

Brilliant, just brilliant.  Better than the sliced bread routine. [/sarcasm]

EDIT: Actually, I have to give TI props from optimizing the routine from
dec b
jr nz, $-1

This whole story about  System  2.71MP has  many  red flags.  First off,  TI is  releasing  2.56MP  with  System  3.0 for the  TI-Nspire. Why would they  just come  up with  this version  out  of the blue?

Second, it's on  April 1st.

Third,  this  OS came  from  only two  people  on  this forum.

Fourth, I found this interesting.

Nice try!


But...
DJ, it seems you have been tricked, or that you're trying to trick us.

868 138 bytes is the size of the original 2.55MP OS
You told me the 2.71MP OS was 868 115 bytes.


The size is just wrong, 23 bytes too small.
It's the exact size you get by resigning the 2.55MP OS with RabbitSign.

Official OSes end with ":00000001FF   -- CONVERT 2.6 -- \n0x1A".
RabbitSigned OSes just end with ":00000001FF", which is exactly 23 bytes smaller.


There is no way TI would have started to use RabbitSign with the 0x0A key we've hacked.

That OS is probably just a 2.55MP OS with its version & welcome strings modified, and then resigned with RabbitSign.

Strangely, nobody has sent it me up to now, although I'm usually sent important things.


I can release the 3.00MP OS for the TI-84+ immediatly if you want

Fifth,  the  stories  in the  news and  the  original  thread don't add up.

Quote from  News  Article

Earlier this evening, ThePenguin77 went on TI Education website to download a copy of TI-84 Plus OS 2.55MP to test his video player, but he was instead greeted with OS 2.71MP:

Original  Post about  2.71

Have you guys heard the news? TI just released OS 2.71. Here's the link. Go get it.

I'm pretty busy so I don't have much time to test it out tonight, but if I find anything cool, I'll definitely tell you guys.

The  post says absolutely nothing about  downloading it to  test a video  player.

Sixth, why would TI release an  OS that  is ten  times slower  and  full  of  bugs  on  top of  all this?

I know, I was just playin' Anywho, I am kind of liking this new OS... I like trying to figure out how to get around certain barriers

I've been working on this all day and I think I've cleaned up the mess. This patch should fix 2.71MP.

I took care of:
-Parser Hook
-USB hook
-Asm(, AsmComp(, and AsmPrgm tokens, all reinstated and all working
-The random crashing
-ClrHome, Output(, Disp, and ClrDraw being slow
-Apps over 2 pages not running
-Output( not displaying in row 8
-Asm(, AsmComp(, and AsmPrgm no appearing in the catalog
-The weird advertisement

Hopefully the OS is now in a more recognizable state.

Edit:
    You might want to press F8 in wabbitEmu because this is going to take a while.