• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win2K Does not see new IBM 40GB HD!! PLS Help!

P

Poontos

Platinum Member
Oddly, Windows XP Pro see's the drive and I was even able make some partitions in the Disk Manager. Yet, Windows 2000 Pro, does not even see the drive.

My setup:

Epox 8KHA+
x2 IBM 60GXP 40GB HD's (Just got the second one today) Jumpers set to Master on drive one and slave on drive two. The BIOS see's the drive fine, too.
512MB Crucial
Antec SX1040


Any ideas? I am not missing one patch or service pack...

Thank you!

EDIT/Update:

Here's what I did:

1.) Physically hooked up the drive as slave.

2.) Boot up, BIOS see's it.

3.) Load Windows 2000 Pro. Does not see drive in Disk Manager, whatsoever.

4.) Reboot again. No go.

5.) Boot into WinXP for kicks, see's the drive fine. Make a couple of partitions. Reboot see's them fine.

6.) Restart into Windows 2000 Pro, no see them.

7.) Back into XP, still see's them, format them as FAT32, instead of NTFS.

8.) Back in 2K Pro, no go.


WTF!?

 
Did 2000 ever detect the drive? If not, go to the control panel and try adding new hardware and see if it's detected then
 
i might be full of it but i recall that xp has a newer and not quite backward compatible native ntfs file system. you may do better formatting it under win 2k first then xp should see it no problem.
good luck
 
Still no go... NE1 else? I re-formatted them to FAT32.

But, even more I checked it out in XP, Win2k would still not see them.
 
if you format them fat32 under dos. (w98 boot floppy) does w2k see them? in my experience, it's better to format fat32 under dos. try this and all os should be able to see it.
good luck
 
When it was fresh out of the "box" Win2K did not see it. That's what the Disk Manager is for.

Thanks though... I guess I could try that, but it doesn`t make sense to me. FAT32 is FAT32.
 
I may be wrong but doesn't IBM like to use Cable Select in jumpers often? I would check that since I was confused with how the jumpers were set on my 60GXP. Maybe XP was made to override this problem. Otherwise call IBM tech support.
 
Is your drive visible during POST? If not maybe this will help:

Few weeks ago I had friends PC for setup and found strange situation:
Drive deceted in BIOS, not visible during POST, XP setup saw it, fdisked and formated it.
File copy went ok, but at restart drive WAS NOT VISIBLE!

Drive was visible in BIOS, but not visible at POST

I found in AWARD BIOS: drive was listed there, but was not active!
I highlited drive, pressed enter and got screen where drive was disabled.
Setting it to active resolved the problem.
 
Thanks...

I tried that, although there is no option to make the drive "active" in the BIOS -- which it see's it fine, exactly the same as my first drive.

Should I set the second drive to cable select, even though XP see's it fine?
 
From my experience XP can see drive even it not connected or configured correctly.
It can see and work, but cant boot from it.

If you can see drive with correct size on POST screen (not just in BIOS), maybe BIOS is a problem.
Are your BIOS compartable with 40GB drives?

I would set drive alone as master on primary channel,
boot from W98 floppy and try to access drive first.

If no access, check connection, jumpers, BIOS (40GB limit and settings).
 
K..

I already have the exact same drive plugged in as the master, so the BIOS can see one 40GB HD, and I cannot see it having difficulty see two of the same.

Anyone else running this setup?

I am going to try and set it as cable select and see how that goes. Very odd...

Thanks for all the suggestions.
 
Was the jumper placed in an unlisted configuration originally? Once, I had a drive where the jumper was placed across the master and slave pins. I changed it to master, and it didn't work. Once it put it back to it's original position, it worked fine. Seems like some kind of PnP jumpers or something of the sort. This was on a WD 8.4GB something or other.
 
So you formatted this drive in XP right? I think XP uses a different NTFS version that 2k can't read. Try reformatting in 2k and XP should be able to read it.
 
In your Win2k device manager, under IDE ATA/ATAPI controllers, have you ever changed any of the Advanced Settings?

I always set the IDE Devices that I'm not using to the None setting for a supposedly quicker bootup, and when I mess with drives I almost always forget to switch it back to Auto the first time. Since WinXP saw your drive, I can't think of anything else that could be wrong.
 


<< In your Win2k device manager, under IDE ATA/ATAPI controllers, have you ever changed any of the Advanced Settings?

I always set the IDE Devices that I'm not using to the None setting for a supposedly quicker bootup, and when I mess with drives I almost always forget to switch it back to Auto the first time. Since WinXP saw your drive, I can't think of anything else that could be wrong. >>


That appears to be it... but as soon as I made the change back to auto detect in 2K, I get a nt kernel blue screen at boot uP!

WTF!

Thanks for the suggestion!
 


<<

<< In your Win2k device manager, under IDE ATA/ATAPI controllers, have you ever changed any of the Advanced Settings?

I always set the IDE Devices that I'm not using to the None setting for a supposedly quicker bootup, and when I mess with drives I almost always forget to switch it back to Auto the first time. Since WinXP saw your drive, I can't think of anything else that could be wrong. >>


That appears to be it... but as soon as I made the change back to auto detect in 2K, I get a nt kernel blue screen at boot uP!

WTF!

Thanks for the suggestion! >>



u should try to reinstall win2k with a format 😛
 
I agree, it seems like a pretty weird problem to me. Damned computer problems, sometimes they are so quirky and so hard to diagnose. If WinXP detects it, then there must be some setting somewhere in Win2k that is not allowing the drive to be displayed properly. All I can suggest is playing around if device manager, with the controllers and the drive. After you finally give up, try and reinstall Win2k. Good luck.
 
Hmmm... still getting a ntoskrnl.exe BSOD, which I have never got (a bsod) on this machine. And in Save mode too!

I am going to unplug the second drive and see if I can get back into Windows.

Anyone running this type of setup with success? Thanks

 
OK, it appears as though I have figured it out.

I went into the BIOS setup and enabled "Reset Configuration Data". And booted up into Win2K, saw the drives, etc.

Now, can I set this back to disabled? And what does it do exactly?

One more thing, what exactly does your BIOS say when it detects these IBM drives at post?


Thanks to all!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top