If the stack operator runs out of memory because registers are constantly pushed onto it and not popped off what happens to the calculator? When I emulate it the emulator tells me it fails and the calculator turns off and clears the RAM, but are their actual detrimental effects to the calculator's RAM or Archive memory?

Code:

I know its an infinite loop, but its the goal to scare people, I always back up the RAM in a group before using it.[/code]

The stack grows from high memory to low memory; you will be able to push until the stack overwrites the area in RAM where you are running the program, at which point random code will execute, and your calculator will almost definitely crash. Since you're executing completely random code, there is a nonzero possibility you could accidentally write things to ROM, but you won't permanently damage your RAM.

Ok thanks

Explain please? Do you mean to make a routine to purposely crash a calculator?

Unfortunately yes, but it was more of just a mistake that it came about. I was working on learning assembly and I accidentally made that, and it happened to spread a bit, i wanted to make sure it was harmless to the calculator's ROM before it got onto some school owned calculator

I hope not; we generally frown on that sort of thing. On a happier note, would you care to introduce yourself in the Introduce Yourself topic?

will do

Ohh, I was under the impression that you were trying to make a sort of "malicious" program so-to-speak. Also I don't know Assembly, so I can't help, I was just trying to decide what the intentions of that bit of code was.

That's fair; thanks for asking, Sonlen. Etag, I wouldn't call it harmless, but it's unlikely to cause permanent damage.