Erik765
New member
Hi there,
I have an ACA500 with an ACA1232 attached and it's been working great on my A500+ (Rev 8.1).
I recently spotted a Rev. 3 keyboard (with the C= key on it) and decided to grab it. I just got it yesterday and replaced my old keyboard (which needed replacing anyway). Re-attached everything and the keyboard caps lock blinks continually and it didn't boot at all with the ACAs still attached. Well, maybe a bad chip on the keyboard. Oh well, I can worry about that later. I plugged my old keyboard back in but now I'm getting completely random results when I try and boot with my ACAs in. It boots just fine from my gotek without the ACAs in.
I'll sometimes get a blue screen. Sometimes blue will flash for a moment (like it always has), then I get a garbled screen. Sometimes it is blue then black.
It did boot successfully one time after re-seating the ACA1232, not sure why or how.
It never gets past blue any more with the ACA1232 plugged in.
I attempted to use the debrick method, but there is little to no documentation on it. I put the jumper on the debrick pins and powered it on with the menu500.aca file on a CF card in the aux slot. When powered on, it is blue, then black and the drive light flashes quickly and then it stays black. Doesn't seem to change anything afterwards.
How could just plugging in a different keyboard do this?
I pulled out my Rev. 6 motherboard and am getting the same results on that board as well
Another thought is I was using the system for a good 3 hours the night before, but everything was working perfectly the entire time. Could I have overheated something, or?
Does anyone know if the warranties are still good on these (even if I bought them both used)?
I'm so bummed right now (especially considering how much I spent on these 2 cards)
Any thoughts on anything at all I could try at this point?
Thanks in advance and let me know if you need any more details on anything.

I have an ACA500 with an ACA1232 attached and it's been working great on my A500+ (Rev 8.1).
I recently spotted a Rev. 3 keyboard (with the C= key on it) and decided to grab it. I just got it yesterday and replaced my old keyboard (which needed replacing anyway). Re-attached everything and the keyboard caps lock blinks continually and it didn't boot at all with the ACAs still attached. Well, maybe a bad chip on the keyboard. Oh well, I can worry about that later. I plugged my old keyboard back in but now I'm getting completely random results when I try and boot with my ACAs in. It boots just fine from my gotek without the ACAs in.
I'll sometimes get a blue screen. Sometimes blue will flash for a moment (like it always has), then I get a garbled screen. Sometimes it is blue then black.
It did boot successfully one time after re-seating the ACA1232, not sure why or how.
It never gets past blue any more with the ACA1232 plugged in.
I attempted to use the debrick method, but there is little to no documentation on it. I put the jumper on the debrick pins and powered it on with the menu500.aca file on a CF card in the aux slot. When powered on, it is blue, then black and the drive light flashes quickly and then it stays black. Doesn't seem to change anything afterwards.
How could just plugging in a different keyboard do this?
I pulled out my Rev. 6 motherboard and am getting the same results on that board as well
Another thought is I was using the system for a good 3 hours the night before, but everything was working perfectly the entire time. Could I have overheated something, or?
Does anyone know if the warranties are still good on these (even if I bought them both used)?
I'm so bummed right now (especially considering how much I spent on these 2 cards)
Any thoughts on anything at all I could try at this point?
Thanks in advance and let me know if you need any more details on anything.

