Problems burning Kickstart

[3VILC]

I thought you mightve been onto something for a minute there, as I had been wondering along similar lines. But alas pin 2 (pin1 on the 40pin socket) is connected to where it's supposed to be on the CPU. The A2000 does have a 2.04 mask rom in it so not likely a problem there. I guess I should retrieve that chip and sanity check it in the A500 as well.
Have been using the A500 for Rom testing since is much easier to get at the chip.

:Edit: With a bizarre twist, the 2.04 mask ROM works fine in the A500, I figured I'd test a 3.2 in the A2000 again while the drive tray was out.. and it kindof works?! but is unstable as heck, like most of the time Guru's within a few seconds on the kickstart screen. Same chip that only gives a red or yellow screen on the A500. No I'm just even more confused than I was before ?? do I just have 2 machines that are rock stable on older but not on 3.2

[Elmo Putney]

hmmm, I'm out of ideas then. I would be cleaing socket and pins, they are not getting any younger! I dont have a functioning A500, but I guess I could try your bin file in my A600 if you want to send it to me.

[3VILC]

I guess it couldn't hurt to verify my file/programmer isn't the issue, if you have some 27c800 kicking around.
I tried DiagROM in the A2000 again and learned that ram on the A2091 that I had to disable because it random started making the machine not boot, is actually because it generates a "bus error" when its enabled, so wonder if theres some dying bus logic also playing a role in later kickstarts not working properly as well. Might start up a new thread on that