Omnimaga
Calculator Community => TI Calculators => General Calculator Help => Topic started by: robberguy189 on October 04, 2012, 10:07:38 pm
-
So is there a chance my calculator will die if I'm playing games. I have a ti 84+. Nothing big like final fantasy tales of magic 2 http://www.ticalc.org/archives/files/fileinfo/272/27285.html just some rpg's and mario, biggest file I've downloaded is rl3 by Kevin Oullet, 120 kb.
I don't use ti-boy either, I tried it and it lags like crazy.
I don't code on my calculator so I don't care if I lose anything, I just want to know if my calculator will break from playing games.
Is there any way to back up my calculator so it won't break, not just my files.
-
With the current games released so far, the only real way to really damage your calculator permanently is if one of the games frustrates you enough to take an hammer to smash your calc out of anger.
However, in case a game crashes, your RAM will most likely be cleared, along with some archive stuff in some cases. Always back up in case. Also some crashes can cause the screen to turn royal blue so in that case just remove a battery quickly and your screen should be safe.
-
Unless the games do stuff like boot-code modification or similar things (i didn't hear of any game doing that) most badly your ram could be cleard or you'd have to re-install the os, but that's all.
-
There's nothing that would permanently crash your calc other than utilities that alter the boot code or certificates, but you'll never see those things in games ever. So you should be safe if you don't mind occasional RAM clears.
-
Agreed. Nothing out there can mess up your calculator.
Here are ways to fix any problems that occur (the numbers assume you've done each previous step):
1. Press ON [Fixes 75% of crashes]
2. Remove battery and then reinsert it [Fixes 98% of crashes]
3. Remove battery and then hold DEL while inserting it [Fixes 99% of crashes]
4. Remove battery and reinsert it. Hold CLEAR while pressing ON and then clear all mem. [Fixes 99.9% of crashes]
5. Remove battery and then hold DEL while inserting it, at this point, attach it to your computer and send a new OS over [Fixes 100% of crashes]
Though, to be fair, if you get to step 4, you should talk to us.
-
That's awesome, my ram clears all the time, I don't mind. I eat that stuff up.
But something weird happened today where my screen turned black (not because of brightness) and battery removal didn't work, neither did del + insert battery. It worked after a few battery removals though (it had me pretty damn nervous). In this case would reinstall os work since I can't see the screen (and calc won't respond)?
I think it might have had something to do with the mode (clears screen, pauses game) key on mario 1.2
what about this game fftom 2, will it break my calc? http://www.ticalc.org/archives/files/fileinfo/272/27285.html
-
It's BASIC. If anything happens, just press [ON].
-
I don't know. It says that if you press on damage to your calculator may occur. It also puts a lot of emphasis on how the author is not responsible to damage to your calculator. Read the readme.
Oh yeah, and what do you mean when you say my screen will go royal blue? So it will just crash, turn royal blue, and I should pop out a battery really quick? What happens if I fail to remove a battery in time?
-
Its a programming langauge implemtented by TI, nothing by TI would damage a calculator (except os 3.0.1 for nspire)
and with basic programs just press ON if anything goes haywire
-
Oh yeah, and what do you mean when you say my screen will go royal blue?
It's a pretty specific thing called the LCD test mode, and I don't know of any programs that cause it unintentionally. Usually when it happens, it's because someone tried to make it happen.So it will just crash, turn royal blue, and I should pop out a battery really quick?
It's a command sent to the display to tell it to basically go overpowered. It's used for testing the LCD quality, but after a while it can do damage to the display. Pulling a battery will stop it immediately.What happens if I fail to remove a battery in time?
If you let it run for a few minutes, it can leave lasting damage to your screen.
Again, I don't think it really happens unintentionally.
-
On top of that, it's possible to cause a RAM clear or a calc freeze without even running one program. All you need is store a 2-bytes token in Ans or a string variable, then use Rcl on that string with only 1 byte left to recall the actual character.
-
Oh yeah, and what do you mean when you say my screen will go royal blue?
It's a pretty specific thing called the LCD test mode, and I don't know of any programs that cause it unintentionally. Usually when it happens, it's because someone tried to make it happen.So it will just crash, turn royal blue, and I should pop out a battery really quick?
It's a command sent to the display to tell it to basically go overpowered. It's used for testing the LCD quality, but after a while it can do damage to the display. Pulling a battery will stop it immediately.What happens if I fail to remove a battery in time?
If you let it run for a few minutes, it can leave lasting damage to your screen.
Again, I don't think it really happens unintentionally.
mario 1.2 is, coincidentally, the only thing i've ever seen to cause it unintentionally, so that must have been what happened./me wonders how coding that accidentally worked.
-
Actually the BSOD, if ran for about 30 seconds a few times, seems to eventually affect the screen contrast uniformity. At one point you will have parts with lower contrast and parts with higher contrast. You should be fine if BSOD runs for a few seconds, but don't do like some people who let it run for a long while several times just because they find it cool.
-
mario 1.2 is, coincidentally, the only thing i've ever seen to cause it unintentionally, so that must have been what happened./me wonders how coding that accidentally worked.
Mario 1.2 is, coincidentally, the only thing i've seen to need ALCDFIX recently.
Here's what happens, Mario uses the old naive fastcopy, this means that on calcs with bad screens, it's going to be garbled unless you use ALCDFIX. Now, what usually happens when you send commands too fast is that the LCD driver just can't keep up and doesn't perform all of them which is what causes the garbling.
That's what usually happens. But on rare occasion, the LCD driver will instead perform the wrong command. This is rare since 31/32 writes to the screen simply data rather than commands, but it happens. So what can happen is that the LCD driver executes the wrong command, and that command happens to be test mode.
-
I use alcdfix from tiwizard. I know the glitch in mario only happens sometimes when I start the game again just after it exited because I ran out of lives. From now on I will probably exit crunchy os and turn off the calc every time I die and the game exits. And then I will run the game again. Just to be safe.
The screen also turned pitch black, not royal blue.
Also, will removing batteries while the calculator is running (to fix a crash) damage my calculator?
-
No removing the batteries is perfectly fine and the reason it said royal blue is because on the ti-82 the original super mario 1.2 (it was 1.0 then) the screen was blue
biggest file I've downloaded is rl3 by Kevin Oullet, 120 kb.
O.O that happens the be the owner of this site's project DJ_O
-
...
It worked after a few battery removals though (it had me pretty damn nervous).
LOL, I guess something happens like that to all of us. I got that feeling when this (http://ourl.ca/16162) happened. Only difference between you and me is mine was actually broken. There should be a thread for posting your terrifying calc experiences.
-
Actually I think there might be one, but maybe it was just about data loss.
-
Well I might try fftom2 on a calc emulator just to be sure. It says that my calc will be damaged if I press the on key.
Thank you all for your help.
-
XD dont listen to that junk, since it is a basic.program he just doesny want people to press on and go through its source code and cheat and say they beat the game
-
XD dont listen to that junk, since it is a basic.program he just doesny want people to press on and go through its source code and cheat and say they beat the game
It's also a precaution in case for some strange and pretty much impossible reason something happens to your calculator while his stuff is running that you can't blame him and try to sue him or get him to pay for repairs/replacement.
-
The author tries to scare you so that you don't attempt at cheating at the game (which is possible by exiting the program where not supposed to and editing stuff before running it again). FFTOM is at huge risk of hacking even without code modifying/running different programs, but it's so complex that it's almost impossible.
In the worst case scenario, you'll have to restart your game from scratch or re-install it.
In my old RPGs, what usually happened was the game giving an error if you modified the wrong stuff or pressing ON prematurely.
-
Here's what happens, Mario uses the old naive fastcopy, this means that on calcs with bad screens, it's going to be garbled unless you use ALCDFIX. Now, what usually happens when you send commands too fast is that the LCD driver just can't keep up and doesn't perform all of them which is what causes the garbling.
That's what usually happens. But on rare occasion, the LCD driver will instead perform the wrong command. This is rare since 31/32 writes to the screen simply data rather than commands, but it happens. So what can happen is that the LCD driver executes the wrong command, and that command happens to be test mode.
I remember Mario crashing and causing a blue screen on a TI-83+SE. But your way sounds plausible, too.
-
In my old RPGs, what usually happened was the game giving an error if you modified the wrong stuff or pressing ON prematurely.
Unless you knew his encryption system completely >:D (Yeong points to ROL3)