Omnimaga
General Discussion => Technology and Development => Other => Topic started by: BalancedFury on September 17, 2011, 06:08:14 pm
-
One day, I was doing something on my 84 SE+ and then, blue ink like thing covered my screen. I took out the batteries and tried again, and the calc seemed normal. And now, it just randomly does that...
How do I fix it? :o
-
Can you describe what happens a bit more? It could just be the contrast setting somehow getting turned to the max..
-
No.. the first time, it was when I spammed playing Mario all day. But, now, it just goes blue even when I'm trying to calculate something. Also, when the BSOD pops up, it resets, and when I check there is a unarchived program called ecsasme(?) and when i try to delete it, it just shuts itself down..
-
That happens sometimes when there's a crash. The LCD controller has something called "test mode" that sends an abnormal amount of energy to the LCD pixels. Sometimes a crash will send an errant command to the LCD controller, activating the test mode. The data sheet says of the test mode, "Do not use this command." It is common belief that leaving it in test mode for any length of time can damage the screen, but there's never been any reports of that happening.
Do you have 2.53 or 2.55 installed? Those OSes have serious stability issues.
-
That happens sometimes when there's a crash. The LCD controller has something called "test mode" that sends an abnormal amount of energy to the LCD pixels. Sometimes a crash will send an errant command to the LCD controller, activating the test mode. The data sheet says of the test mode, "Do not use this command." It is common belief that leaving it in test mode for any length of time can damage the screen, but there's never been any reports of that happening.
Do you have 2.53 or 2.55 installed? Those OSes have serious stability issues.
Ok... but how do you explain the ecsasme program?
And i have 2.43 OS which is known to be the most stable.. I think
-
Googling (which takes me right back to this website ^_^)tells me that ecsasme is a temporary thing made by Doors CS, and when Doors crashes, sometimes ecsasme isn't deleted properly. So, probably Doors is crashing for some random reason, and that's also what's causing the BSOD... maybe try redownloading Doors in case it somehow or other go corrupted?
-
Yes, ecsasme is a temporary program created by Doors CS. I've seen it show up a few times when a program tried to stop running in an unusual way. I don't understand what this has to do with the BLOD, though...
-
Oh okay thanks...
Imma erase DoorCS7 then....
It always crashes and never works. :P
-
I highly recommend using zStart as your shell. It's made by thepenguin, and any errors that he has are taken care of in a timely fashion. The most recent version has DCS like Homerun features, but it's much faster and more stable, unless you're running Basic programs. If that's the case, I'd wait until thepenguin fixes Basic compatibility, as it's kinda broken now. :P
Oh okay thanks...
Imma erase DoorCS7 then....
It always crashes and never works. :P
I'd leave Doors, but use it as zStart's shell. zStart requires a shell, and since Doors has the most routines, I kept it for this.
-
I highly recommend using zStart as your shell. It's made by thepenguin, and any errors that he has are taken care of in a timely fashion. The most recent version has DCS like Homerun features, but it's much faster and more stable, unless you're running Basic programs. If that's the case, I'd wait until thepenguin fixes Basic compatibility, as it's kinda broken now. :P
Oh okay thanks...
Imma erase DoorCS7 then....
It always crashes and never works. :P
I'd leave Doors, but use it as zStart's shell. zStart requires a shell, and since Doors has the most routines, I kept it for this.
Ok thanks..