0 Members and 1 Guest are viewing this topic.
biggest file I've downloaded is rl3 by Kevin Oullet, 120 kb.
...It worked after a few battery removals though (it had me pretty damn nervous).
"welcome to the world of computers, where everything seems to be based on random number generators"
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
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.
In my old RPGs, what usually happened was the game giving an error if you modified the wrong stuff or pressing ON prematurely.