I recently purchased the A7M266-D and I can't seem to figure out a certain problem. First of all, my config:

AMD AthlonMP (Palomino) 1.2Ghz x2
256MB Crucial PC2100 DDR
Maxtor Diamondmax Plus 60.0GB x2
Pioneer DVD-104s
HP 9300i CDRW
64MB GeForce2 GTS
SBLive! X-Gamer
10/100 NIC
Microsoft Internet Keyboard Pro
Microsoft Intellimouse Explorer

Well, I put it all together and flipped the switch and was happy to see it POST fine, but as soon as I tried to enter the BIOS I found that the keyboard wasn't responding at all. I can't even turn Caps Lock/Num Lock on or anything, but the lights do flicker during the POST. I even tried two old keyboards to see if that was the problem, but still got no luck. I sent the mobo back to the company I purchased it from and they ran tests and sent it back claiming it works fine. So I hooked it all up again and now it does the same thing but it gives me the error: "Keyboard is locked out... Please unlock key. Press F1 to continue, Del to enter BIOS." I have lots of experience with computers and I have never run into this problem before. I'm pretty sure all the parts (ram and such) are compliant with the mobo. Please let me know if you can help.

I would check the Voltage multiplier settings on your board to be sure they are default for your setup. Also, are you running a USB KB or a PS2 one? Some motherboards by default will not recognize a USB KB on boot, and that may cause your issue there. If it's a PS2, then perhaps trying a different KB. Asus is a rock solid mb manufacturer in my experience (I have several Asus boards here in the house), and I have no doubts they are correct in that the board is working properly.

I know lately 2CPU has had a lot of threads relating to the A7M266-D in the forums, so you might wanna check them out.

don't think you can even use usb keyboards on the mpx boards due to the lack of integrated usb.

He is most certianly using a ps2

<---Uses USB KB and had the same situation on my dual 1900MP setup. This is why I brought it to the table.

Hey Hey --
Used to get this all the time -- mostly ended up being case/processor cooling, or a funky bios. Run only one chip, boot to dos, and flash to the latest stable bios.

Make sure the processor fans are making contact in the right places.