### Micro.Blog (Patrick H. Mullins)
[Back] - Date: 2019-07-13 @ 03:34 AM EDT by PHM / Amiga 500 Project: Trouble in Paradise

I hate to say it but I really screwed up my Amiga 500. The good news is that I managed to get the GoTek drive working. This is great because it allows me to access a ton of Amiga software that i'd normally not be able to use. The bad news is that I installed the drivers for the Wicher 500i accelerator card and used the resulting configuration utility to overclock the CPU from 25 MHz to 33 MHz. That was an extremely bad idea. The entire system immediately stopped working as soon as I enabled the change. I tried rebooting several times, pulled the power, did a hard reset, and even tried booting from a floppy disk. All I got in return for my efforts was a solid black screen. I tried every trick that I could possibly think of. Unfortunately, nothing worked.

It later occurred to me that perhaps I simply needed to let the A500 rest for a few hours before plugging it back in. This little hack often works because it gives the system time to reset itself. I waited a few hours before plugging in the power supply and turning the system back on. This time I got a little bit further than before, but still not far enough to help. Instead of displaying a black screen it now boots to a super minimal AmigaDOS prompt. How minimal? I messed with it for a while and I have yet to find a single command that actually works. I'm starting to think that something is terribly wrong here. Inserting the v3.1.4 Workbench floppy disk results in the same useless AmigaDOS prompt.

Let's back up a bit and consider what we already know. I'm pretty sure (95% positive) that a solid black screen is actually a CPU post error code. This makes perfect sense considering that the last thing I did before the system crashed was overclock the processor on the Wicher card from 25 MHz to 33 MHz. So, how do I fix this? Well, there are a few pins and jumpers on the card that I can mess around with that will change certain CPU settings. I'm going to start there. My plan is to first disable the turbo option which will cause the board to default to a blistering 10 MHz. My hope is that by running the CPU at such a ridiculously slow speed that it will give the system a chance to boot to a usable desktop.