Nope, they also removed the i/o port from all of their new calcs so I'm wondering if we'll get some cool USB stuff.

Actually, it's not so bad as I/O port is not really that needed with the amount of usb cable we have...

There is probably a TI-Planet article that explains the new features in OS 5.0. I'll try to find it later when I am home.

Quote from: Duke "Tape" Eiyeron on April 08, 2015, 03:54:29 PM
Actually, it's not so bad as I/O port is not really that needed with the amount of usb cable we have...

Too bad the usb is very weird to use in ASM (or maybe im not skilled enough). Anyway at least i can understand
the raw I/O port (and its easier to use with hardware connection )

It sucks that the I/O jack is gone from all new calcs including this one, though, because this renders the transfer of data between those models and the 83+/83+SE impossible...

Indeed. But getting users to buy new calculators is precisely the goal

Yes. But in USA the TI-83+ is still in production and being sold. In classrooms where all Z80 models are accepted, 83+ users will be even more cut off from the rest of the class now and not necessarily able to afford a more expensive calc (although there are fewer and fewer 83+ users now)

TI should just get rid of the 83+ and replace it with the 84+

It's ZShell all over again!

Seriously, if they're that worried about ASM, why don't they just rerelease the TI-81 and have students buy that... Oops, my bad.

It would actually be funny if the old TI-82 way of hacking this calc would work. By the way I wonder if the screen is still the same or if it's memory-mapped, now that the CE uses one?

Is "memory mapped" like in the TI-84+ where the screen is just on a few bytes in the ram?

Memory Map means you have direct access to the screen's pixels as it were a memory location. Like a address range in your memory.

Ooh okay, thanks. Sooo... like the TI-84+ CSE?

Yep, what Eiyeron said. And nah more like the TI-85, 86 and early 68K hardwares.  What I wonder about memory-mapping is if we can point to whatever memory location we want for screen display?

Usually that's the system which decide of this. Most of the time, the address is hard linked to the CPU but with a MMU system, you could have arbitrary memory mapping in your program. FiXos isplanned to support such mappings to allow future versions of MonochromeLib to be supported in a POSIX-line environment (the MMU breaks the direct memory access and thus we have to wrap the adress call to acces the right place).

So it's like a specific memory region especially appointed to be the display's ram, right?