TI-83+/84+ OS glitches compilation thread (all OSes)

[qazz42]

yes, I tihnk so

[Deep Toaster]

Doesn't the first post say that it's for 1.13 and 1.14 versions of the OS only?

EDIT: Nice, ztrumpet!

[DJ Omnimaga]

I remember back then people trying to install a TI-73 OS on a 83+ or vice-versa and 84+ OS on 83+ or vice-versa. I think in most cases, it would crash often. BrandonW made a tool to turn a TI-73 into a 83+ a while ago, though, and if I remember, he managed to put a 84+OS on a 83+SE, although it apparently crashed often.

[Deep Toaster]

I remember back then people trying to install a TI-73 OS on a 83+ or vice-versa and 84+ OS on 83+ or vice-versa. I think in most cases, it would crash often. BrandonW made a tool to turn a TI-73 into a 83+ a while ago, though, and if I remember, he managed to put a 84+OS on a 83+SE, although it apparently crashed often.

I remember Chameleon, but doesn't the 73 have a lot less flash mem?

[DJ Omnimaga]

It has the same as the 83+, if I remember. On some 73 OS there are less flash pages available but on some others, there are more than on the regular 83+ (12, if I remember)

[Deep Toaster]

Oh, so the 73 OS is a different size? I see...

[thepenguin77]

The Err:Version definitely happens on an 83+. So I'll fix that today. It is a much more serious issue because it actually doesn't create the group, it just says it does. Whereas a garbage collect would fix error bad address.

Whenever I attach a fix, just look at the last 3 digits of the name. Addr119, Addr243, and Addr253 are for 1.19, 2.43, and 2.53 respectively.

[Deep Toaster]

The Err:Version definitely happens on an 83+. So I'll fix that today. It is a much more serious issue because it actually doesn't create the group, it just says it does. Whereas a garbage collect would fix error bad address.

Wait, so does this mean that if I get an ERR:VERSION, there's no way to get the files back, even through third-party stuff?

[thepenguin77]

Correct. The OS actually double increases the page when going to the next. So for instance, say while making the group header, the OS runs out of space on page 08, it increases to page 09, then increases again to page 0A. This causes two problems, 1. Your files weren't written. And 2. When eventually the OS moves on to write to page 0A, the calculator is going to freeze when it attempts to write to an area that has already been written to.

[Deep Toaster]

Correct. The OS actually double increases the page when going to the next. So for instance, say while making the group header, the OS runs out of space on page 08, it increases to page 09, then increases again to page 0A. This causes two problems, 1. Your files weren't written. And 2. When eventually the OS moves on to write to page 0A, the calculator is going to freeze when it attempts to write to an area that has already been written to.

I've never had it freeze like that yet. Probably a good thing...

[calcdude84se]

Ouch, that could be very bad...
Good luck fixing it!

[DJ Omnimaga]

Darn this sucks. When ERR:VERSION occured I always thought that the file was created, just not with the right header or something.

When I group shit, I just create two groups, in case. Sometimes 3 might be better. When an ERR:VERSION occurs when ungrouping, you lose the original file copy...

[Deep Toaster]

When I group shit, I just create two groups, in case. Sometimes 3 might be better. When an ERR:VERSION occurs when ungrouping, you lose the original file copy...

Whoa, really? Thanks for warning me. I've been making a single group, then testing to see if it works by trying to ungroup it. Didn't know it deleted the ones in RAM...

[DJ Omnimaga]

Yeah I lost a program due to that once, but thankfully I had a recent backup in an older group. Sadly, when ungrouping it wont even bother asking you to overwrite/rename, it immediately ERR VERSION on it and obliterate it. The trick, I think, is to archive everything that ungrouped successfully and then ungrouping the next group. I would backup before testing, though, in case that also deleted archived stuff. Grouping is definitively not 100% safe. Another thing that can happen is corrupted basic or ASM program. A byte gets changed somewhere in the code, causing an error or display issues while executed.

[Deep Toaster]

Hehe, I just checked out a TI-83 Plus from our school library. Great for backup

But then, I lost my cable