AN35N Ultra BIOS Problem??

ICee wrote:
 > K. W. wrote:
  >> Hi,
  >>
  >> I am having some troulbes getting the AN35N Ultra I bought to
  >> recognize my WD 160G/8M HDD.
  >>
  >> What I have done:
  >> -First, I used the WDC Data LifeGuard Tools to partition the new
  >> HDD; the tool can see the size as 160G. But when I start to install
  >> either Win2k pro or WinXP pro, it only sees it as 31.49G! No matter
  >> how I partition it, as one sector or as two or three smaller ones.
  >> -Using WinMe bootdisk fdisk doesn't help, either. It also sees it
  >> as 32254 MB.
  >> -Installing Win2K/WinXP directly without WDC DLT doesn't help
  >> either.
  >> -I also installed XP SP1a; updated the atapi.sys to 5.1.2600.1135,
  >> etc.
  >>
  >> For each installation, I write all 0s to WD HDD just to make sure
  >> I have a clean start.
  >>
  >> Symptoms:
  >> The bootup display shows:
  >> Primary Master Disk: LBA,ATA 100, 33821 MB (it should be 160G)
  >>
  >> Also I can't do ANY OC. The multiplier stays at 11.5. If I change
  >> FSB, it will fall back to safe mode (Athlon 1150MHz).
  >>
  >> The BIOS is AwardBIOS v6.00PG (AN35S00G -6/10/2003). It should be
  >> recent enough to see at least 137G, right?
  >>
  >> I did notice the BIOS ROM SIZE reported as 256K. But the manual
  >> says it should be 2M. Why such a small size? Even my very old
  >> Celeron400 reported 512K. The BIOS chip on the board reads:
  >> PhoenixBIOS
  >> D686 BIOS
  >> Phoenix 1998
  >> 115106460
  >>
  >> My system:
  >> AMD 2600+ Barton
  >> Enermax 350W PS
  >> Kingston PC2100/256 x 2
  >>
  >> Is the BIOS causing the problem, or is this a bad board? I am
  >> really frustrated. This is my first DIY PC. I need your expertise,
  >> please help.
  >>
  >> Thanks,
  >>
  >> K. W.
 >
 > You might want to read this:
 >
<a style='text-decoration: underline;' href="http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q126/8/55.ASP&NoWebContent=1" target="_blank">http://support.microsoft.com/default.aspx?scid=http://support.microsof...om:80/s</a>
 >
<font color=purple> > Short link: <a style='text-decoration: underline;' href="http://tinyurl.com/258p8</font" target="_blank">http://tinyurl.com/258p8</font</a>>
 >
 > If you have a newer CPU (>week 39), the multiplier is probably locked.

Almost forgot. On the WD drive, there is a position for the jumper for
Master, Slave and Only Drive on Cable. Be sure you are using the latter
position if that is the only drive on the IDE port.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: AN35N Ultra BIOS Problem?? 

"ICee" <icee.DeleteThis@nospam.invalid> wrote in message news:<UM4Kb.1598$yW1.1284271@news2.news.adelphia.net>...
 > ICee wrote:
  > > K. W. wrote:
   > >> Hi,
   > >>
   > >> I am having some troulbes getting the AN35N Ultra I bought to
   > >> recognize my WD 160G/8M HDD.
   > >>
   > >> What I have done:
   > >> -First, I used the WDC Data LifeGuard Tools to partition the new
   > >> HDD; the tool can see the size as 160G. But when I start to install
   > >> either Win2k pro or WinXP pro, it only sees it as 31.49G! No matter
   > >> how I partition it, as one sector or as two or three smaller ones.
   > >> -Using WinMe bootdisk fdisk doesn't help, either. It also sees it
   > >> as 32254 MB.
   > >> -Installing Win2K/WinXP directly without WDC DLT doesn't help
   > >> either.
   > >> -I also installed XP SP1a; updated the atapi.sys to 5.1.2600.1135,
   > >> etc.
   > >>
   > >> For each installation, I write all 0s to WD HDD just to make sure
   > >> I have a clean start.
   > >>
   > >> Symptoms:
   > >> The bootup display shows:
   > >> Primary Master Disk: LBA,ATA 100, 33821 MB (it should be 160G)
   > >>
   > >> Also I can't do ANY OC. The multiplier stays at 11.5. If I change
   > >> FSB, it will fall back to safe mode (Athlon 1150MHz).
   > >>
   > >> The BIOS is AwardBIOS v6.00PG (AN35S00G -6/10/2003). It should be
   > >> recent enough to see at least 137G, right?
   > >>
   > >> I did notice the BIOS ROM SIZE reported as 256K. But the manual
   > >> says it should be 2M. Why such a small size? Even my very old
   > >> Celeron400 reported 512K. The BIOS chip on the board reads:
   > >> PhoenixBIOS
   > >> D686 BIOS
   > >> Phoenix 1998
   > >> 115106460
   > >>
   > >> My system:
   > >> AMD 2600+ Barton
   > >> Enermax 350W PS
   > >> Kingston PC2100/256 x 2
   > >>
   > >> Is the BIOS causing the problem, or is this a bad board? I am
   > >> really frustrated. This is my first DIY PC. I need your expertise,
   > >> please help.
   > >>
   > >> Thanks,
   > >>
   > >> K. W.
  > >
  > > You might want to read this:
  > >
<font color=purple> > <a style='text-decoration: underline;' href="http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q126/8/55.ASP&NoWebContent=1</font" target="_blank">http://support.microsoft.com/default.aspx?scid=http://support.microsof...om:80/s</a>>
  > >
<font color=green>  > > Short link: <a style='text-decoration: underline;' href="http://tinyurl.com/258p8</font" target="_blank">http://tinyurl.com/258p8</font</a>>
  > >
  > > If you have a newer CPU (>week 39), the multiplier is probably locked.
 >
 > Almost forgot. On the WD drive, there is a position for the jumper for
 > Master, Slave and Only Drive on Cable. Be sure you are using the latter
 > position if that is the only drive on the IDE port.

Thanks for your input. I did tried two jumper configurations: A. Cable
Select, B. Single. The result is the same. The system can see the HDD,
yet confined to 32G. As Western Digital installation guide suggested,
I tried to set CHS (Access Mode) to 1023, 16 heads, and 63 sectors.
But as soon as the system bootup, it just falls back to the following:

Capacity 33821
Cylinder 65530
Head 16
Precomp 0
Landing Zone 65529
Sector 63

It doesn't matter whether I set the Access Mode to "Auto" or "CHS",
or IDE Primary Master "Auto" or "Manual". These number seems "Locked".
Again, is this the BIOS problem? I still don't understand why the BIOS
ROM size is so small. But the BIOS version seems quite recent.

I saw many positive comments on the Shuttle AN35N Ultra
motherboard. But this problem gives me headache. Also, isn't that the
motherboard is supposed to unlock the multiplier?

K.W.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: AN35N Ultra BIOS Problem?? 

On 4 Jan 2004 18:52:13 -0800, K. W. wrote:

 > Hi,
 >
 > I am having some troulbes getting the AN35N Ultra I bought to
 > recognize my WD 160G/8M HDD.
 >
 > What I have done:
 > -First, I used the WDC Data LifeGuard Tools to partition the new
 > HDD; the tool can see the size as 160G. But when I start to install
 > either Win2k pro or WinXP pro, it only sees it as 31.49G! No matter
 > how I partition it, as one sector or as two or three smaller ones.
 > -Using WinMe bootdisk fdisk doesn't help, either. It also sees it
 > as 32254 MB.
 > -Installing Win2K/WinXP directly without WDC DLT doesn't help
 > either.
 > -I also installed XP SP1a; updated the atapi.sys to 5.1.2600.1135,
 > etc.
 >
 > For each installation, I write all 0s to WD HDD just to make sure I
 > have a clean start.
 >
 > Symptoms:
 > The bootup display shows:
 > Primary Master Disk: LBA,ATA 100, 33821 MB (it should be 160G)
 >
 > Also I can't do ANY OC. The multiplier stays at 11.5. If I change
 > FSB, it will fall back to safe mode (Athlon 1150MHz).
 >
 > The BIOS is AwardBIOS v6.00PG (AN35S00G -6/10/2003). It should be
 > recent enough to see at least 137G, right?
 >
 > I did notice the BIOS ROM SIZE reported as 256K. But the manual
 > says it should be 2M. Why such a small size? Even my very old
 > Celeron400 reported 512K. The BIOS chip on the board reads:
 > PhoenixBIOS
 > D686 BIOS
 > Phoenix 1998
 > 115106460
 >
 > My system:
 > AMD 2600+ Barton
 > Enermax 350W PS
 > Kingston PC2100/256 x 2
 >
 > Is the BIOS causing the problem, or is this a bad board? I am
 > really frustrated. This is my first DIY PC. I need your expertise,
 > please help.
 >
 > Thanks,
 >
 > K. W.

32gb is max for fat32. Is that your prob?

<a style='text-decoration: underline;' href="http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/winxppro/reskit/prkc_fil_lxty.asp" target="_blank">http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/pro...chnol/w</a>

hth
Kristi<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: AN35N Ultra BIOS Problem?? 

Kristi <a.RemoveThis@b.net> wrote in message news:<brn5758lbnl8$.g0g3io2add1o$.dlg@40tude.net>...
 > On 4 Jan 2004 18:52:13 -0800, K. W. wrote:
 >
  > > Hi,
  > >
  > > I am having some troulbes getting the AN35N Ultra I bought to
  > > recognize my WD 160G/8M HDD.
  > >
  > > What I have done:
  > > -First, I used the WDC Data LifeGuard Tools to partition the new
  > > HDD; the tool can see the size as 160G. But when I start to install
  > > either Win2k pro or WinXP pro, it only sees it as 31.49G! No matter
  > > how I partition it, as one sector or as two or three smaller ones.
  > > -Using WinMe bootdisk fdisk doesn't help, either. It also sees it
  > > as 32254 MB.
  > > -Installing Win2K/WinXP directly without WDC DLT doesn't help
  > > either.
  > > -I also installed XP SP1a; updated the atapi.sys to 5.1.2600.1135,
  > > etc.
  > >
  > > For each installation, I write all 0s to WD HDD just to make sure I
  > > have a clean start.
  > >
  > > Symptoms:
  > > The bootup display shows:
  > > Primary Master Disk: LBA,ATA 100, 33821 MB (it should be 160G)
  > >
  > > Also I can't do ANY OC. The multiplier stays at 11.5. If I change
  > > FSB, it will fall back to safe mode (Athlon 1150MHz).
  > >
  > > The BIOS is AwardBIOS v6.00PG (AN35S00G -6/10/2003). It should be
  > > recent enough to see at least 137G, right?
  > >
  > > I did notice the BIOS ROM SIZE reported as 256K. But the manual
  > > says it should be 2M. Why such a small size? Even my very old
  > > Celeron400 reported 512K. The BIOS chip on the board reads:
  > > PhoenixBIOS
  > > D686 BIOS
  > > Phoenix 1998
  > > 115106460
  > >
  > > My system:
  > > AMD 2600+ Barton
  > > Enermax 350W PS
  > > Kingston PC2100/256 x 2
  > >
  > > Is the BIOS causing the problem, or is this a bad board? I am
  > > really frustrated. This is my first DIY PC. I need your expertise,
  > > please help.
  > >
  > > Thanks,
  > >
  > > K. W.
 >
 > 32gb is max for fat32. Is that your prob?
 >
<font color=purple> > <a style='text-decoration: underline;' href="http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/winxppro/reskit/prkc_fil_lxty.asp</font" target="_blank">http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/pro...chnol/w</a>>
 >
 > hth
 > Kristi

Not really. I use NTFS (I see the cluster size defaulted to 4K.) The
problem is the total size available is always 32G no matter how I
partition it. In other words, the system sees it as a 32G hard drive.
And I lost 128G!

K.W.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: AN35N Ultra BIOS Problem?? 

You could use the drive overlay util in the Data Lifeguard tools. That
should get you around this problem.

Dave


"K. W." <kuenw.DeleteThis@hotmail.com> wrote in message
news:b1edd11b.0401050946.242be617@posting.google.com...
 > Kristi <a.DeleteThis@b.net> wrote in message
news:<brn5758lbnl8$.g0g3io2add1o$.dlg@40tude.net>...
  > > On 4 Jan 2004 18:52:13 -0800, K. W. wrote:
  > >
   > > > Hi,
   > > >
   > > > I am having some troulbes getting the AN35N Ultra I bought to
   > > > recognize my WD 160G/8M HDD.
   > > >
   > > > What I have done:
   > > > -First, I used the WDC Data LifeGuard Tools to partition the new
   > > > HDD; the tool can see the size as 160G. But when I start to install
   > > > either Win2k pro or WinXP pro, it only sees it as 31.49G! No matter
   > > > how I partition it, as one sector or as two or three smaller ones.
   > > > -Using WinMe bootdisk fdisk doesn't help, either. It also sees it
   > > > as 32254 MB.
   > > > -Installing Win2K/WinXP directly without WDC DLT doesn't help
   > > > either.
   > > > -I also installed XP SP1a; updated the atapi.sys to 5.1.2600.1135,
   > > > etc.
   > > >
   > > > For each installation, I write all 0s to WD HDD just to make sure I
   > > > have a clean start.
   > > >
   > > > Symptoms:
   > > > The bootup display shows:
   > > > Primary Master Disk: LBA,ATA 100, 33821 MB (it should be 160G)
   > > >
   > > > Also I can't do ANY OC. The multiplier stays at 11.5. If I change
   > > > FSB, it will fall back to safe mode (Athlon 1150MHz).
   > > >
   > > > The BIOS is AwardBIOS v6.00PG (AN35S00G -6/10/2003). It should be
   > > > recent enough to see at least 137G, right?
   > > >
   > > > I did notice the BIOS ROM SIZE reported as 256K. But the manual
   > > > says it should be 2M. Why such a small size? Even my very old
   > > > Celeron400 reported 512K. The BIOS chip on the board reads:
   > > > PhoenixBIOS
   > > > D686 BIOS
   > > > Phoenix 1998
   > > > 115106460
   > > >
   > > > My system:
   > > > AMD 2600+ Barton
   > > > Enermax 350W PS
   > > > Kingston PC2100/256 x 2
   > > >
   > > > Is the BIOS causing the problem, or is this a bad board? I am
   > > > really frustrated. This is my first DIY PC. I need your expertise,
   > > > please help.
   > > >
   > > > Thanks,
   > > >
   > > > K. W.
  > >
  > > 32gb is max for fat32. Is that your prob?
  > >
  > >
<a style='text-decoration: underline;' href="http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/winxppro/reskit/prkc_fil_lxty.asp" target="_blank">http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/pro...chnol/w</a>
  > >
  > > hth
  > > Kristi
 >
 > Not really. I use NTFS (I see the cluster size defaulted to 4K.) The
 > problem is the total size available is always 32G no matter how I
 > partition it. In other words, the system sees it as a 32G hard drive.
 > And I lost 128G!
 >
 > K.W.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: AN35N Ultra BIOS Problem?? 

K. W. wrote:
 > Thanks for your input. I did tried two jumper configurations: A. Cable
 > Select, B. Single. The result is the same. The system can see the HDD,
 > yet confined to 32G. As Western Digital installation guide suggested,
 > I tried to set CHS (Access Mode) to 1023, 16 heads, and 63 sectors.
 > But as soon as the system bootup, it just falls back to the following:
 >
 > Capacity 33821
 > Cylinder 65530
 > Head 16
 > Precomp 0
 > Landing Zone 65529
 > Sector 63
 >
 > It doesn't matter whether I set the Access Mode to "Auto" or "CHS",
 > or IDE Primary Master "Auto" or "Manual". These number seems "Locked".
 > Again, is this the BIOS problem? I still don't understand why the BIOS
 > ROM size is so small. But the BIOS version seems quite recent.
 >
 > I saw many positive comments on the Shuttle AN35N Ultra
 > motherboard. But this problem gives me headache. Also, isn't that the
 > motherboard is supposed to unlock the multiplier?
 >
 > K.W.

Have you tried the diagnostic tools from WD, this might help in pointing out
where the problem lies.

Not familiar with WD but some manufacturers have a jumper on the drive that
will restrict access to the first 32gig for compat with older bios`s, does
the WD?

--
Mark
Twixt hill and high water.
N.Wales, UK.
Email is spam trap try baskitcaise at gmx dot co dot uk<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: AN35N Ultra BIOS Problem?? 

baskitcaise <baskitcaise.DeleteThis@hotmail.com> wrote in message news:<btbfgq$4p4dr$1@ID-143023.news.uni-berlin.de>...
 > K. W. wrote:
  > > Thanks for your input. I did tried two jumper configurations: A. Cable
  > > Select, B. Single. The result is the same. The system can see the HDD,
  > > yet confined to 32G. As Western Digital installation guide suggested,
  > > I tried to set CHS (Access Mode) to 1023, 16 heads, and 63 sectors.
  > > But as soon as the system bootup, it just falls back to the following:
  > >
  > > Capacity 33821
  > > Cylinder 65530
  > > Head 16
  > > Precomp 0
  > > Landing Zone 65529
  > > Sector 63
  > >
  > > It doesn't matter whether I set the Access Mode to "Auto" or "CHS",
  > > or IDE Primary Master "Auto" or "Manual". These number seems "Locked".
  > > Again, is this the BIOS problem? I still don't understand why the BIOS
  > > ROM size is so small. But the BIOS version seems quite recent.
  > >
  > > I saw many positive comments on the Shuttle AN35N Ultra
  > > motherboard. But this problem gives me headache. Also, isn't that the
  > > motherboard is supposed to unlock the multiplier?
  > >
  > > K.W.
 >
 > Have you tried the diagnostic tools from WD, this might help in pointing out
 > where the problem lies.
 >
 > Not familiar with WD but some manufacturers have a jumper on the drive that
 > will restrict access to the first 32gig for compat with older bios`s, does
 > the WD?

Yes, I tried diagnostic tools. All tests show the HD is ok. But the
Diagnostic tool shows it as 33G, though. But the WD Lifeguard Tool
shows it as 160G.) I've gone through the WD suggestions with no avail.

As for the BIOS, it is released 6/10/2003. And as you can see, this
system uses fairly new hardware recently purchased.

Is there any Shuttle AN35N Ultra users out there who can confirm
they are putting the right ROM chip (the info provided previously) for
my board? I want to know whether this is a WD hard disk problem or
the BIOS or a bad motherboard.

Thanks,

K.W.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: AN35N Ultra BIOS Problem?? 

"DaveL" <dave1027.RemoveThis@comcast.net> wrote in message news:<TIadnYuazp-zLWSi4p2dnA.RemoveThis@comcast.com>...
 > You could use the drive overlay util in the Data Lifeguard tools. That
 > should get you around this problem.
 >
 > Dave
 >
 >

Yes, that was my first try. I used the WD Data Lifeguard Tools CD
to boot the system. I went through the steps to the partition. I think
it does so called Dynamic Drive Overlay (DDO.) The partition went
well. It can see the 160G space. I partitioned one for 16G, the other
for the rest of 140G+. Everything seemed fine with the partition. It
told me to exit and start installating OS. I could see the Western
Digital Banner appeared at the bootup, (similar to the process of
older WD EZ-Drive I did years ago.)

But when it comes to Windows installation formatting step, 2K/XP
sees it as 32G. The rest is the stories I described previously... Why
only the WD DLG tools see the correct size during partition is beyond
my comprehension. The BIOS sees it as 32G, the windows see it as 32G,
the WD Diagnostic tool sees it as 32G, and the very same WD DLG tools
run in the window see it as 32G! How frustrating.

The system running now is 16G + 15.xG. Where did the 128G go?
Does this look more like a software installation or configuration
problem than the hardware problem?

K.W.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: AN35N Ultra BIOS Problem?? 

   > > >
   > > > Symptoms:
   > > > The bootup display shows:
   > > > Primary Master Disk: LBA,ATA 100, 33821 MB (it should be 160G)
   > > >
   > > > Also I can't do ANY OC. The multiplier stays at 11.5. If I change
   > > > FSB, it will fall back to safe mode (Athlon 1150MHz).
   > > >

  > >
  > > 32gb is max for fat32. Is that your prob?
  > >
  > >
<a style='text-decoration: underline;' href="http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/winxppro/reskit/prkc_fil_lxty.asp" target="_blank">http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/pro...chnol/w</a>
  > >
  > > hth
  > > Kristi
 >
 > Not really. I use NTFS (I see the cluster size defaulted to 4K.) The
 > problem is the total size available is always 32G no matter how I
 > partition it. In other words, the system sees it as a 32G hard drive.
 > And I lost 128G!
 >
 > K.W.

There might be a jumper on the hard drive limiting its size down to 32
GB -usuallylabeled 32GB clip=. This is to make it compatible with old
motherboards, go and check for it!<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: AN35N Ultra BIOS Problem?? 

"Tomasz Cenian" <aaa DeleteThis @bbb.ccc.dd> wrote in message news:<kVhKb.411669$dt3.71755@news.chello.at>...
   > > > >
   > > > > Symptoms:
   > > > > The bootup display shows:
   > > > > Primary Master Disk: LBA,ATA 100, 33821 MB (it should be 160G)
   > > > >
   > > > > Also I can't do ANY OC. The multiplier stays at 11.5. If I change
   > > > > FSB, it will fall back to safe mode (Athlon 1150MHz).
   > > > >
 >
   > > >
   > > > 32gb is max for fat32. Is that your prob?
   > > >
   > > >
<font color=purple> > <a style='text-decoration: underline;' href="http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/winxppro/reskit/prkc_fil_lxty.asp</font" target="_blank">http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/pro...chnol/w</a>>
   > > >
   > > > hth
   > > > Kristi
  > >
  > > Not really. I use NTFS (I see the cluster size defaulted to 4K.) The
  > > problem is the total size available is always 32G no matter how I
  > > partition it. In other words, the system sees it as a 32G hard drive.
  > > And I lost 128G!
  > >
  > > K.W.
 >
 > There might be a jumper on the hard drive limiting its size down to 32
 > GB -usuallylabeled 32GB clip=. This is to make it compatible with old
 > motherboards, go and check for it!

This is a 10 pin (jumper) hard drive. It comes with a jumper at pin
1,2 - Cable Select, which I initially installed. When I had this size
problem, I changed to Single setting, pin 4,6. The same result. I even
tried the suggested Alternate Jumper Settings, still no use.
I don't see there is a 32GB clip you referred, unless this driver
is internally shorted/faulty?

K.W.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: AN35N Ultra BIOS Problem?? 

K. W. wrote:
 > "DaveL" <dave1027.TakeThisOut@comcast.net> wrote in message
 > news:<TIadnYuazp-zLWSi4p2dnA.TakeThisOut@comcast.com>...
  >> You could use the drive overlay util in the Data Lifeguard tools.
  >> That should get you around this problem.
  >>
  >> Dave
  >>
  >>
 >
 > Yes, that was my first try. I used the WD Data Lifeguard Tools CD
 > to boot the system. I went through the steps to the partition. I think
 > it does so called Dynamic Drive Overlay (DDO.) The partition went
 > well. It can see the 160G space. I partitioned one for 16G, the other
 > for the rest of 140G+. Everything seemed fine with the partition. It
 > told me to exit and start installating OS. I could see the Western
 > Digital Banner appeared at the bootup, (similar to the process of
 > older WD EZ-Drive I did years ago.)
 >
 > But when it comes to Windows installation formatting step, 2K/XP
 > sees it as 32G. The rest is the stories I described previously... Why
 > only the WD DLG tools see the correct size during partition is beyond
 > my comprehension. The BIOS sees it as 32G, the windows see it as 32G,
 > the WD Diagnostic tool sees it as 32G, and the very same WD DLG tools
 > run in the window see it as 32G! How frustrating.
 >
 > The system running now is 16G + 15.xG. Where did the 128G go?
 > Does this look more like a software installation or configuration
 > problem than the hardware problem?
 >
 > K.W.

Truly a strange problem. Is it possible it was caused by using the WD
utility to begin with?
Maybe check on WD web site for any insight.

--
"I love deadlines. I love the whooshing noise they make as they go by."
Douglas Adams<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: AN35N Ultra BIOS Problem?? 

K. W. wrote:
 > "DaveL" <dave1027.RemoveThis@comcast.net> wrote in message
 > news:<TIadnYuazp-zLWSi4p2dnA.RemoveThis@comcast.com>...
  >> You could use the drive overlay util in the Data Lifeguard tools.
  >> That should get you around this problem.
  >>
  >> Dave
  >>
  >>
 >
 > Yes, that was my first try. I used the WD Data Lifeguard Tools CD
 > to boot the system. I went through the steps to the partition. I think
 > it does so called Dynamic Drive Overlay (DDO.) The partition went
 > well. It can see the 160G space. I partitioned one for 16G, the other
 > for the rest of 140G+. Everything seemed fine with the partition. It
 > told me to exit and start installating OS. I could see the Western
 > Digital Banner appeared at the bootup, (similar to the process of
 > older WD EZ-Drive I did years ago.)
 >
 > But when it comes to Windows installation formatting step, 2K/XP
 > sees it as 32G. The rest is the stories I described previously... Why
 > only the WD DLG tools see the correct size during partition is beyond
 > my comprehension. The BIOS sees it as 32G, the windows see it as 32G,
 > the WD Diagnostic tool sees it as 32G, and the very same WD DLG tools
 > run in the window see it as 32G! How frustrating.
 >
 > The system running now is 16G + 15.xG. Where did the 128G go?
 > Does this look more like a software installation or configuration
 > problem than the hardware problem?
 >
 > K.W.

Did you try it with all jumpers removed?? If it's a 6 or 10 pin (jumper
pins) drive, all jumpers should be removed. See this:
<a style='text-decoration: underline;' href="http://support.wdc.com/techinfo/general/jumpers.asp" target="_blank">http://support.wdc.com/techinfo/general/jumpers.asp</a>

--
"I love deadlines. I love the whooshing noise they make as they go by."
Douglas Adams<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: AN35N Ultra BIOS Problem?? 

I have the same problem with my wd800jb drive. It started after i
installed the wd data life guard software and used it to copy my
previous drive to this one. it installed dynamic disk overlay
software. Once that software was installed my bios stopped recognizing
he whole drive. Used to see 80 gig, now only see's 32.8 gig...just
wondering of you found a solution to your problem? I have tried a low
level format, tried to remove ddo, and data life guard software to no
avail.
 >> Stay informed about: AN35N Ultra BIOS Problem??