This is just a text file filled with hints for people that have "dead" A1s All credit is given to original authors of said hints --- With respect to the A1 boards. The issues that I've seen have been AGP cards not seating quite right that tends to prevent the power up of the video. Also, there have been issues with cheaper higher wattage power supplies not getting enough load to regulate the voltages correctly. A right-sized power supply, rather than a 350 W or 400 W supply will do you better. The next thing I'll ask is for you to pull the video card, hook up a serial cable to another machine and see if you get anything out the serial port. This is an important test that will tell you a lot about whether the board is running. Sincerely, Adam Kowalczyk --- There are several terminal programs on Aminet that you could use. Download one and set it to 9600, 8, N, 1. I've still come across Laplink cables that have both 25 and 9 pin connectors on them. Hook the 25 Pin side to the A4000 and the 9 pin to the top most serial connector (closer to the kb and mouse port). If you can't find that style of cable, find someone with a laptop with a serial port and use one of the Windows terminal programs. Adam Kowalczyk --- Possibly a long shot, but have you physically unplugged the computer or really turned it off (not just the front power switch) at any point? A couple of months ago, my A1 stopped booting in a similar manner to yours, and after testing everything (including two other graphics cards) to no avail, I finally turned it off using the power supply switch in the back (which I should have done from the beginning, but I'm still used to my old Amiga where the front power switch really does totally cut the power). And hey presto, when I turned it on again, it worked. The Uboot settings were back to their defaults, but it was easy enough to fix that and it's been fine ever since. Not sure what caused it, but just in case, I've been using "halt" instead of "reboot" on those occasions when I need to reboot, since the "reboot" command seems a bit stuffed right now anyway. Maybe there's no connection and it was just a fluke. Eric Haines --- Sometimes a badly seated CPU module can cause this fault. Firstly earth your computer, (plug into wall socket but mains power at wall MUST be OFF). Touch metal on case to discharge any static from your body. Open case, loosen two nylon screws securing CPU module lift module off Motherboard. With it off you might want to check the heatsink and put some real paste between the heatsink and CPU. Re-seat the CPU module firmly, but don't break the Motherboard. :) Tighten nylon screws, assemble, etc.. Test run again, hope this helps. Regards, Tim --- Try another battery. Cheers Justin Veggerby Kristensen --- You'd be suprised how much trouble a bad battery can cause! Take a look in the archives and see some of my preivous messages about the troubles I had with my XE. I really thought that my XE was dead! When Justin informed me about the battery I was very suspicious about it, but after replacing it with a new one it worked perfectly. And it still does... =) Regards, Pekka Nissinen --- There might just have been enough power left in the battery for one boot. If everything seems to be working individually, but the boot sticks, suspect the battery. In any case, it's not as though it's a horrendously expensive item! Rose --- Actually what happens is that it sort of starts up - at least it sends a little output to the serial console, but then stops dead at a time where it expects some kind of sane reply from battery/date. It might help to remove the connection to all equipment including memory and start it up without anything connected wait 15 secs and then take the power - or to short out the conectors on the battery socket, but in the end it will continue to not boot whenever you have had it off for even a short while. Cheers Justin Veggerby Kristensen --- EOF