Hello all,
This is my first post so just wanted to say hello to everyone and say that I am really glad to see so many people still interested in Amiga world.

I have a bunch of stability issues with an A4000 i bought a while ago and finally had a chance to boot it up.
The config is as follows:
- A4000D mobo in a tower, (default 150W PSU)
- CS MK3 060/50MHz
- CVPPC
- Micronik PCI board (PCI slots unused - the old style one) daughter board
Standard A4000D daughterboard (bought a new one for testing a while ago as well).
- Multiface, Toccata, VLab, Octagon (board rev working with 060 - don't remember the exact number but definitely higher than the one that causes 060 to freeze)
Ariadne II.
Scan Doubler, some SCSI drives/streamer/CDROM
ATA boot drive (340MB from the good old days that I kept from my previous A4000D back in a day)
Stability was the issue before I have managed to:
1. remove some RAM (as 4x16MB on MK3 caused errors - in one of the mem tests I've found on aminet) - so currently I have 2MB chip on the mobo + 32MB on the CS (2x16MB)
2. remove the leaking battery - done (first thing)
3. format the system and check the SCSI drives for bad sectors - done
4. install 3.1 on the first partition and update setpatch, 68040 library and... what was the first thing I did and don't remember now?
5. Removed all the boards apart from the scan doubler (as I had to bin C= 1942!!) and use the new daughter board that is definitely good.
6. System works and is stable! - everything works as expected until....
Until I plugin the CVPPC - this causes a strange error in the Early Boot Menu - when I go to "Boards" - I can see the CS 060 identified properly and then all other entries are duplicated with the ID of the CVPPC - don't have to say that booting such system causes WB 3.1 (no CGX installed at all) to crash shortly after loading...
Strange thing is that I remember booting this machine up shortly after purchase (Feb 07) and there was nothing like this going on...
My question therefore is if someone has experienced similar issues and if possible did anyone find a fix for it?
I would greatly appreciate your help - got the beast in the server room ready for testing so I can try any bit of advice shortly after work (usually around 5pm weekdays).
Well - thanks in advance.
tinner