No, I believe your answer is here:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q314463

How did you partition and format the drive? Were you trying to install XP?

Thanks for your reply. I looked at the link which talks about FAT32 has a limit of 64GB size.

I am not quite sure how that applies to an brand new unformatted hard drive ?

One thing I didn't mention in my previous posting was, when I first installed the new hard

drive, I accidently connect it to IDE(1) connect(primary) and the existing hard drive to IDE(2) connecter.

When I restarted the computer it could find XP boot file and asked me about loading XP or not?

Then I realized that I had it wrong so I quit and power of and switch the connecter.

Now the existing hard drive is on IDE(1) - primary and the new empty hard drive is on IDE(2) and

XP is booting find. When I trie to format it

it only shows the capacity of  32GB from XP diskmgmnt on the new drive so I stopped.

do you think the first sequence that messed up the capacity and make it "FAT32" ?

 

Check this link, it will tell you how to get the atapi 1135 that you need for larger HDDs. Doogie

http://support.microsoft.com/default.aspx?scid=kb;en-us;303013

Still no luck with the 2nd wd120-JB hard drive after I tried these
steps,

1. In Bios setup menu, I turn off my primary hard drive and
boot off WD CD that came with the HD. Without XP, it seems to
configure to 120GB - at least based on the message on screen.
2. then I turned back on my primary HD and boot XP w/ SP1. It
still reads 2nd HD as 33MB!
3. I manully regedit EnableBigLba =1 in registry and restart,
still reads 2nd HD as 33MB!
4. I tried to follow instruction from MSN support page to get
Atapi.sys 5.1.2600.1135. I can't quite follow the steps because
I can't find sysprep/i386 directory on my machine. So I put
the 48bitlba.inf and cmdlines.txt in c:\i386\$OEM$\ and merged
rundll commands in a file called cmdlines.bak. Not sure if this
is correct. Not it didn't make any difference, still 33MB!

I checked driver details from admin tools menu,
driver verision is 5.1.2535.0 from Microsoft 7/1/2001 release.
drive detail button says c:windows\system32\drivers\disk.sys
5.1.2600.1106(xpsp1.020828-1920) which mean atapi.sys 1135 is not
taking effect.

Not sure where to go from here. Any suggestions to fix this
Bios problem?

Dell has tested and shipped 120gb drives on the 8200 without BIOS problems or the need to upgrade the BIOS.  I would double check your jumper settings and make sure they are correctly set and to use the "cable select" setting.  If the BIOS is correctly identifying the drive then the problem is in the way you have set it up with the operating system.

 

Message Edited by Majestic on 04-14-2004 10:32 AM

The 4300 model was tested and shipped by Dell with a 100 gig drive as you already know.  Since the machine can use a 100 gig drive then a 120 gig should be no problem.  It is after a 137gigs that you might encounter problems, but you are well under that.  Make sure of the following:

• The BIOS recognizes the drive.
• It is jumper and cabled correctly.
• The drive is correctly FDisk and formatted for NTFS.

Here is a link to a Microsoft article on using XP's disk management software for setting up a new drive.  I'm not a Windows XP user so I can't help you out in that respect.