|
Post by JMan on Jul 2, 2002 9:30:49 GMT -5
I'm using a TI-83+, am I'm starting to work with ASM. I'm just curious, is it possible to permanently ruin a calculator (totally prevent it from working) through ASM? And, what compiler do you use? Do we still use TASM?
|
|
|
Post by mog42 on Jul 2, 2002 15:01:00 GMT -5
I've never heard of a calculator being rendered totally inoperable by an assembly program, but I don't know enough about assembly to give a definitive answer. Usually, the worst thing you can do to a calculator is reset the memory.
I use TASM. I've tried other compilers like ZDS, but I still like TASM the most.
|
|
|
Post by feamsr00 on Jul 3, 2002 12:41:38 GMT -5
Actually there are ways, but you can almost never do it on purpose. Usally it happens when bad writes are sent to flash. Somtimes it seems that the boot codes sees this, and freaks!
|
|
|
Post by Jbirk on Jul 5, 2002 13:38:38 GMT -5
Just overwrite the boot code! All you have to do is LDIR the bytes.
|
|
|
Post by Jbirk on Jul 5, 2002 13:39:18 GMT -5
Even then all you would have to do is install the os again though.
|
|
|
Post by JMan on Jul 7, 2002 11:19:50 GMT -5
Basically, unless you try, you can't screw up your calc massively?
|
|
|
Post by Jbirk on Jul 17, 2002 2:04:32 GMT -5
try my application for screwing up the calc if you dare. calcbasic.netfirms.com/evil.zipBefore you open the .zip, set your zip program to not automatically display comments, because the answer to easy recovery is in the comments. Go ahead, it will screw up your calc bad enough that you will have to pull the backup batteries; unless, you read the comments which explain a certain key combination that I put in there if you choose to surrender instead of pull out the screwdriver. This program won't actually harm your calculator, it is sort of like a controlled, artificially created crash, that actually exits so that the application isn't even running. Well, it is kind of running, and kind of not...it's complicated.
|
|
|
Post by Chris on Aug 19, 2002 12:21:02 GMT -5
Basically, unless you try, you can't screw up your calc massively? you can screw it up massively...but unless you're trying i doubt you want the calc to be screwed up....tho there is a way that i accidently screwed my old one up...took me like...6 months to figure out how to fix it *is still thankful for justin helping him on that* (for some reason i think you're trying to screw it up and then say it was an accident) if you wanna screw it up and act like you didn't mean to...then send the startup app to your calc, and then install it...and set it to run anything....then archive the appvar for it...soon as you turn off your calc...you won't be able to turn it back on...btw as far as pranking goes, justin's app is probably the best you'll get also...to undo the damage that this causes, take out all the batteries (you don't have to worry bout the backup battery tho), and re-insert them with teh polarities reversed, then press ON, then take them out an put all but one in the right way, then hold down the DEL key while you insert the last battery, now it should ask you to re-install the os...now just press ON to cancel re-installing the OS, and after a quick RAM clear...your calc is workign fine again
|
|
|
Post by feamsr00 on Aug 23, 2002 15:40:40 GMT -5
These are all very nice ideas but it woult not be right if I did not include the "Evil Buffer Prog". You see, the "Evil Buffer Prog" is not all that distructive, some might even say benign, but it is VERY annoying and almost imposible to remove (without a reset of course). You know those 2 things (these are programs belive it or not, # and !) you take for granted, the entry buffer and the last entry buffer. Well what this does it switch them around(the address) so that the current entry points to the last entry and the last entry point to the current entry. The result is anything you type results in "DONE" ;D. This may seem harmless but run it during a test and see how "harmless" it realy is! However there currently no known way to remove it unless you have calcsys or a reset, so be warned. (Normaly I could post a link to it (it was posted here before) but the H&G forum is locked so......).
|
|
|
Post by JMan on Aug 28, 2002 21:23:52 GMT -5
People are still responding to this???!! Wow.
Thanks for all the "nice" responses, its good to know people are being so constructve.... ;D
Actually, if you want do some really fun stuff, don't just switch the addresses, but corrupt an entry (Isn't calcysys fun?) change the first byte of the #'s entry, (it's at FD01 on a new calc) to something different, I chose $00. Then, get out of calcsys, do a problem, and then do 2nd+Entry twice, and watch the ? marks fly by...
Or try corrupting Ans altogther...
|
|
|
Post by Chris on Aug 29, 2002 8:42:52 GMT -5
if you already knew how to do that, then why did you bother asking us for methods?
|
|
|
Post by JMan on Aug 30, 2002 18:21:32 GMT -5
Let's try this again...
That first post was about two months ago. I wanted to make sure that it wasn't possible to complety destroy a calc by fooling around with it. Now, two months later (and assembly litterate), I like hex editing the RAM.
|
|
|
Post by Chris on Aug 31, 2002 19:14:24 GMT -5
lemme get this straight, you learned asm in 2 months?
|
|
|
Post by JMan on Sept 1, 2002 16:51:38 GMT -5
Well...I had looked into ASM alittle earlier before I actually started coding, so I was familiar with it when I "started" two months ago. Anyways, I'm also a windows devloper, so it wasn't complety new to me. So I guess it's about 3-4 months. And It's not like I'm another Patrick Davidson or something.
|
|