VOGONS


First post, by seanneko

User metadata
Rank Newbie
Rank
Newbie

I've got a PC Chips M321 here which I have previously tested and confirmed working. I recently got it back out, but it's no longer reading from any floppy or hard drives.

I've tried multiple different multi I/O controllers and drives, all of which are 100% working on other computers.

After configuring the drives in the BIOS and rebooting, the floppy drives will perform the seek test as per normal. But then when it goes to actually boot from the disk, it doesn't even attempt to read. It immediately gives an error saying that no bootable disk is inserted without the floppy drive making any noise at all. Same goes for the hard drive.

Has anyone seen something like this before? The motherboard isn't damaged and otherwise works fine so I'm failing to see why it doesn't work with a confirmed working I/O card.

Reply 1 of 6, by SirNickity

User metadata
Rank Oldbie
Rank
Oldbie

Are there any other cards in there? Sounds kinda like the boot interrupt is being usurped by something (maybe with its own BIOS?) and never getting to the floppy / HDD. I assume you've set the boot order to A: or C:? I know, dumb question, just checking the obvious stuff.

Reply 2 of 6, by seanneko

User metadata
Rank Newbie
Rank
Newbie

The only other card is the video card.

When it tries to boot from the floppy, the LED actually does comes on, but the drive otherwise does nothing. Exactly the sort of symptoms you'd expect from a dead drive, but the drive definitely works perfectly... Even tried it with a Gotek USB thing and got the same symptoms.

Reply 3 of 6, by dkarguth

User metadata
Rank Member
Rank
Member

What brand of IO controller is it? It doesn't happen to be a certain Kouwell KW-556N, does it? I have one of those that did the exact same thing in my 286 when I was building it a couple of weeks ago. It would say something like "Drive not ready" regardless of if there was a floppy in the driver or not. It didn't even check the drive. Rather odd.

"And remember, this fix is only temporary, unless it works." -Red Green

Reply 4 of 6, by seanneko

User metadata
Rank Newbie
Rank
Newbie

I've tried a Goldstar Prime 2C and a UMC based one.

Tried using a BIOS from another random 386 board which made no difference. It POSTed and otherwise worked, but had the same issue.

Reply 5 of 6, by dkarguth

User metadata
Rank Member
Rank
Member

hmm. If it were mine, I'd hook it up to the ol' HP 16500B logic analyzer to see what's going on with the floppy bus. I seriously doubt you have a 16500B, though. Do you have an oscilloscope, by chance?

"And remember, this fix is only temporary, unless it works." -Red Green

Reply 6 of 6, by seanneko

User metadata
Rank Newbie
Rank
Newbie

Unfortunately not, I've had an oscilloscope on my shopping list for ages now but haven't gotten around to getting one.

Just did another check of the board to look for broken traces. Looks fine. Pretty much run out of ideas. I've tested all sorts of combinations of controllers/drives/cables. It's definitely the motherboard that's at fault.