hmmm... could this just be OS 1.18 wit the left+right+on key combo in it? I thought it was funny when 2.40 came out for the 84 and how the 83+'s that almost everyone has would be immune to it, but I guess we now have a new OS. Or something. Can anyone say what advantages this has over previous versions? (I thought they were done making 83+ OS's which is why I think that this is a left+right+on key combo patch thing.)

left+right+ON has no effect.. does absolutely nothing except turn the calc on..

excellent. i'd rather have a cleared calculator than a locked up one.

especially since there are no teachers at my school who know how to clear the archive. they still use 83's.

No offense, but I can't see why you'd rather have all your programs deleted, as long as your calc was unlocked at the end of the test/quiz/whatever.

yeah that's ok i can't really see why either XD

it must be one of those pride things

no asymptote lines on OS 1.19 :D

Hmm? I get an asymptote line graphing y=1/(x-1) and tan(x).

Same here..

I think he means breaks. Ie, it doesn't have the handling 2.30 has.

When XRes=1, or slowest graphing, it doesnt show a line when I draw an asymptote for the area that doesnt have a value, I noticed it had this in OS 1.18.

Isn't xres=1 default?

Also, it could be a fluke. If you set the window right, you can avoid it. It all depends on the function and the window settings.

xres is 2 by default

No it's not.

1) See link above.
2) There is nothing that anyone can tell that has changed. No left+right+on, no asmyptote checking, nothing. I ran diff(1) on 1.18 and 1.19 and was presented with an 878KB output file, however. I don't really care enough to try to dissassemble it. :)

Is there any particular areas where much code has changed or is it small bits and pieces all over the place?
Also, you said the diff was 878 KB, but I don't know enough about the format used by diff to calculate from that how many bytes actually changed. Then again, that figure wouldn't actually mean too much anyway; optimizing a routine at the beginning of a ROM page by just one byte will show the entire page as different. (Or is diff smart enough to detect that? I know fc (a Windows command line utility) isn't that smart when running is binary mode.)

There were several differences of a couple lines. There were a few of several pages changed (which would probably be a couple bytes of optimization).

There's nothing with binary in the files after the headers. The .8xu files are hex.

Has anybody thought to email TI-cares and ask them? They might even tell you.

(Imagine that! Asking for support from the people who are paid to give it. Naah. Why should we do that? It's more fun to speculate anyway.)

That would be a question about technical details. If I learned anything from previous emails to ti-cares, it's that they aren't too good at answering those. (Besides, I totally agree with that last sentence. Too bad I don't have the time for it myself. :S )

Yes. I once emailed them about a problem with my TI-85 and they asked me if I still had the warranty. This was last year. The TI-85 was discontinued long ago.

what the garbage? lolz0rs

This is sort of off topic, but was there any differences in v1.18 from v1.17?

probably some stability and/or compatibility issues fixed, like from 1.18 to 1.19