MaviGozler
12-31-2001, 12:46 PM
We are do-it-yourselfers working with Spacewalker AK31 board.
We've come to the moment of truth---with not much help from the "friendly user's guides" from boardmaker welcoming DIY types.
We worked out the "floppy disk fail" from the BIOS (we hope), and now we see the FDD motor light turn on about the time it should. A bootable disk is loaded; made from "format a:/s" from another PC running W98 (we verified it works). Now the message is "Disk I/O error...replace the disk" etc.
Potential problem: new FDD not working
Test for solution: took known working FDD from that other PC, used its own ribbon cable to connect to board, and we see same message
Potential problem: mainboard defect
Test for solution: didn't do it (yet)...we dread idea of running down to the store and get a replacement board; popping CPU, cards and connectors; then seeing how the replacement board works (at least a day). Have thought of also testing I/O to HDD with loaded O/S taken from other PC, just to see how that's working. System also has new CD/RW we installed, but attempt to boot from CD using "HP Recovery" disks did not work ("Booting from ATAPI CDROM: DISK BOOT FAILURE...")
There must be a simpler solution than believing that data transfer between board and FDD is due to damaged hardware.
------------------
Mavi Gozler
We've come to the moment of truth---with not much help from the "friendly user's guides" from boardmaker welcoming DIY types.
We worked out the "floppy disk fail" from the BIOS (we hope), and now we see the FDD motor light turn on about the time it should. A bootable disk is loaded; made from "format a:/s" from another PC running W98 (we verified it works). Now the message is "Disk I/O error...replace the disk" etc.
Potential problem: new FDD not working
Test for solution: took known working FDD from that other PC, used its own ribbon cable to connect to board, and we see same message
Potential problem: mainboard defect
Test for solution: didn't do it (yet)...we dread idea of running down to the store and get a replacement board; popping CPU, cards and connectors; then seeing how the replacement board works (at least a day). Have thought of also testing I/O to HDD with loaded O/S taken from other PC, just to see how that's working. System also has new CD/RW we installed, but attempt to boot from CD using "HP Recovery" disks did not work ("Booting from ATAPI CDROM: DISK BOOT FAILURE...")
There must be a simpler solution than believing that data transfer between board and FDD is due to damaged hardware.
------------------
Mavi Gozler