Re: Strange //c problems

[RKFAIRCLOTH@unca.edu (Rhonda K. Faircloth)]

In <3211C68D.73FC@esis.vsnet.ch> gilles.tschopp@esis.vsnet.ch writes:

> It is quite normal. I also make the CTROL-OA-CA-RESET on my old 
> //c and I get random low-graphics and after 1-2 minutes, it 
> becomes locked. It doesn't damage anymore your //c.
> 
> Regards,
> 
> Gilles Tschopp

Hmmmm. Low res graphics? Mine will flip around the low and high res screens
before it gets stuck in the loop. Then it's nothing but high res. Every second
or so, the pattern changes, and I hear a click. If I look very closely, I can
see the drive led flash for a split second. I believe that the loop is trudging
through the soft switches, somehow not crashing the machine alltogether. On
ApplePC 2.4, I did the PEEK and also got 0. I did the self test, and it flipped
through most (if not all) of the resolutions before giving me a "System OK"
message. Even worse, the emulatore *did* get locked in a loop the first time I
tried it! Maybe this is psuedo-normal behavior for a //c? To loop like this?
Either way, my //c doesn't go through the same graphics pages like the
emulator, I'm tempted to pull the ROM and compare it with the emulator's.