VOGONS


First post, by Hamby

User metadata
Rank Member
Rank
Member

I've kept my old K6-2 300mhz (socket 7) computer for a long time. I haven't used it much, but I wanted to keep a "vintage" DOS/WFW machine around.

Every once in awhile I'll fire it up, and there's a problem I deal with almost every time. When I fire it up, the system can't detect the HD, and I notice it doesn't spin up. Now, I have 2 HDs, a 4gb and a 6gb that have the same basic system set up, divided into 2gb partitions.

I would have concluded that the drive was going bad if it was only the one drive; I suspect it's the HD controller gone bad, but eventually I do manager to get it to boot one drive or the other. I suspected a faulty power supply, since the drive doesn't spin up, but sometimes it will (eventually) work with HD, CD, 5.25 & 3.5 floppy plugged in, and sometimes it will (eventually) work if I only connect the HD to power. Once it recognizes the drive, I have no problems with it until I leave it sit for a long while. But it doesn't lose the CMOS data.

Can anyone suggest things to try to diagnose what is going on?

I was wanting to "upgrade" this system to Win98, maybe re-partitioning the 6gb drive; I have a 486 motherboard I'm going to build into my DOS/WFW system, and a 286 motherboard I'm going to build into a straight DOS system. So I was hoping to use this old unit to fill in the win98 "hole" in my collection (after all, it originally did run Win98). But if something on the MB is going bad, especially if it's something my limited skills can't fix, I need to know so I can find another socket 7 MB before the price gets too unreasonable.

if it's the power supply, I can work around that. If it's the drives, I can get CF adapters and go that route. And if it's the controller going bad, I can begin shopping for a new MB. But how can I find out what really *is* wrong?

Last edited by Hamby on 2018-09-27, 13:56. Edited 1 time in total.

Reply 1 of 2, by appiah4

User metadata
Rank l33t++
Rank
l33t++

It is likely the PSU and in some cases moving the boot drive to a 12V rail that is not shared with a floppy and/or optical drive can solve the situation.

I have a similar issue with my Athlon64 PC, the X1950PRO in it is a 12V hog and occasionally I get no bood HDD found errors when booting from cold, when using just a 300W PSU.

Retronautics: A digital gallery of my retro computers, hardware and projects.

Reply 2 of 2, by SW-SSG

User metadata
Rank Oldbie
Rank
Oldbie

The largest amount of current that any HDD will pull at any point during its operation is at spin-up. And, most MBs will not "tell" IDE drives to turn on during BIOS auto-detection; rather it's the usual with IDE for the HDDs to spin-up by themselves when the PSU turns on and then wait for the BIOS to POST and send commands.

So, it probably is your PSU. Got a spare one to try?