I've just removed and socketed 1 of the RAM chips but its not that one (15 to go...), but does this sound like it could be a RAM problem? What I am puzzled by is that when fastram is there turrican loads, but I thought chipram and fastram were used for very different things within the system - ie. CPU has only access to fast ram, which could mean that fast ram takes priority for code over chipram, and possibly having fastram connected means I am skipping the CPU loading code into dodgy ram perhaps, is that what I am seeing here?
I thought the A500 was supposed to test RAM on boot and give a green screen if there's a problem?
It doesn't test the ram byte by byte, as that would take far too long. You'll need a memory testing program for that, and aminet would be a good place to look for obtaining one (there are many). Someone else can perhaps point you in the right direction for the best program to use.
And on the A500, any
trapdoor ram expansion isn't Fast ram at all, despite being known as Fast ram by the system. It's actually as slow as Chip ram and is known as "slow ram", as it's connected to the same bus as Chip ram. It's quite useless really, so many people do the modification on their A500's to turn that 512k slow ram into Chip ram that can used as Chip ram (more sound samples, more screens open etc etc).