Survey posted 2004-10-12 07:16 by Morgan.

Contribute ideas to surveys by sending a mail to survey@ticalc.org.

Your TI-83+ (se) doesn't crash enough? Try to run this:

:AsmPrgm
:EFCG53
:C9

Use at your own risk.

Allow me to be the first to ask: what the heck? Last I checked, G was not a hexadecimal digit, and I believe TIOS agrees with me there. But in any case, there are so many better ways to crash than simply calling some random bit of code...

G *isn't* a hex digit!!! Maybe some bug in the OS causes it to crash or incorrectly assemble if it hits a "G" in an "uncompiled" assembly prog...

yeah--that's it, I think.

Or perhaps it interprets "EFCG53" as an ASCII string. I really don't know, but the effect is cool.

Hmm, what does it do? I'd try it but I don't have one to try it with. Would this work on a TI-84+? If so, I know a kid who has one, and I'd really like to try it on his calculator... ;-) (He's probably reading this right now, 120d)

If I were him, I wouldn't let you within a mile of it.

Well, I bet I live pretty far away from you, so you're safe :P

How to crash your 83/84 calc:

NO, this code dosn't do anything but produce an error

IF you change the 'G' to 'F' it runs and says "Done"

IF you change the 'G' to 'F' it turns off the calc and clears the ram

YES, #3 does work on the 84+SE, I have one and it just crashed.

1. Create new program and name it 'A'
2. Enter the code below
:AsmPrgm
:EFCF53
3. Go to the home screen and type
Asm(prgmA
4. turn on the calc

<pauses and looks at calc>
WHAT?!? MY TIC TAC TOE PROGRAM THAT I JUST GOT WORKING IS GONE?!?
<realizes he also owns a 83+SE>
</pauses and looks at calc>
Oh, wait, I have the other copy still from when I was testing it

MOST EFFICIENT CRASH:

HEY, I found the most efficient command to crash the calc!

1. Put the following (single line) in Program 'A'
:AsmPrgm

2. run the following prompt at the home screen
Asm(prgmA

3. turn on the calc and look at the "cleared ram" message

u know we don't need to know how to crash peoples calcs, what if sum1 used that to make a virus

How the hell would it spread?

wow...I tries it in VTI, and it worked the first time, but on the second try the screen turned black with random bars of white. Is that just VTI?

I can't get that to compile...I know there's probably something idiotic I forgot...I created a new program (B) and entered the code, then tried "Asm(prgmB", but it gave me a syntax error.

Same here... I tried to run it, and it gave me an ERR:SYNTAX. Then I changed the G to an F, and it worked fine. I even tried running it as a BASIC program, and that didn't work. I tried compiling it with another program and then running it like that, but it STILL gave me an error! This is truly not possible... though it may have been possible in former versions of the TI-OS. I have v1.18. What version did you have, JcN, when you ran it?

Frankly, I'm not even sure I typed in the hex command correctly. I think the OS was 1.12, but the effect was really weird. The calculator (normal 83+) turned off and locked down. Whenever my friend and I (he did this to his calc to show me) tried to turn it back on, the screen flickered up this garbled image of the memroy (a chaotic mess of pixels) and turned off. We removed all the batteries, and tried again. Same effect. We removed the back-up battery. It turned on, and all of the programs were hidden (they turned up a week later or so), and all of the RAM had been cleared.

Have any of you guys messed up your calculator soo bad it turned all blue? No, not using that program bt RCT, but just general with ASM programs?

I've had that happen a couple of times and it scared the shiznits out of me, especially becasue my warranty had expired.

Yes, I've had the "Blue screen of death" playing a regualar ASM game. (I don't remember which one). This was back when I had just gotten my 83+ (Okay, okay, it was only a year and a half ago) and I sat there and watched it, thinking "cool, I didn't know my calculator could do this!" I thought this until I couldn't get it to stop, and had to pull out the batteries.

On my TI-82, I did once. I was trying to make this stupid little game in ASM and all of the sudden, the screen turned blueish (even though it's already blue :P) and it started flashing all sorts of weird stuff all over the screen. It did this for a while and eventually reset. I couldn't get it to happen a second time, so I have NO idea what happened. Unfortunately, I don't have the source anymore. But then again, it doesn't really matter since it only worked once.

No, but I had "nice" colors on my V200. I was playing around with Command Post Plus's cool.txt (Extremely Interesting Ideas). I was messing around with the logical screen height. It said that a value from 256-0 through 256-256 is valid, but I was bored of that and I tried putting 256-257. This made my screen turn weird colors, and it scared the "shiznits" out of me. I quickly took out my batteries, and deleter Command Post Plus. Actually, when I come to think of it, those colors were pretty cool.

(cough) Deleted!!! (Not deleter)

Bahleeted!

Was it as colorful as the V400? ;-)

What colors did you get? Remember any specifically, or was it just a whole bunch of colors? Hehe, I'd really like to see that. :-D

If you want to take a risk, try to follow my instructions exactly. I think that this overloads the lcd or something.

My screen has turned blue plenty of times due to some bad code in my program. For you ASM programmers, _FillRect's lower-right coordinate must be 'more lower-right' than the other corner, or it will give you a blue screen :)

o0o... *Looks at the pretty blue lines*