Re: XP does not see all of a WD 160GB drive that was added as a slave
From: Jason Tsang (jason-onlineDEL_at_ETEmvps.org)
Date: 02/04/04
- Next message: anonymous_at_discussions.microsoft.com: "nvidia driver headaches"
- Previous message: C Eichhorn: "A required section was not found in the INF"
- In reply to: John: "Re: XP does not see all of a WD 160GB drive that was added as a slave"
- Next in thread: Shenan Stanley: "Re: XP does not see all of a WD 160GB drive that was added as a slave"
- Reply: Shenan Stanley: "Re: XP does not see all of a WD 160GB drive that was added as a slave"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 3 Feb 2004 20:18:36 -0500
It's only going to get bigger unfortunately :(
-- Jason Tsang - Microsoft MVP Find out about the MS MVP Program - http://mvp.support.microsoft.com/default.aspx "John" <anonymous@discussions.microsoft.com> wrote in message news:91f001c3eab1$d14e81c0$a101280a@phx.gbl... > Thanks Carey!!!!! > > I knew that was a possibility but discounted it as such > because I never dreamed the gap would be so large!!!! > > John > > > > >-----Original Message----- > >From the Western Digital website: > > > >Determining drive capacity can be confusing at times > because of the different measurement standards that are > often used. When dealing with Windows and Mac based > systems, you will commonly see both decimal measurements > and binary measurements of a drive's capacity. In either > case, a drive's capacity is measured by using the total > number of bytes available on the drive. As long as the > drive displays the correct number of bytes (approximate), > you are getting the drive's full capacity. > > > >Decimal vs. Binary: > >For simplicity and consistency, hard drive manufacturers > define a megabyte as 1,000,000 bytes and a gigabyte as > 1,000,000,000 bytes. This is a decimal (base 10) > measurement and is the industry standard. However, > certain system BIOSs, FDISK and Windows define a megabyte > as 1,048,576 bytes and a gigabyte as 1,073,741,824 bytes. > Mac systems also use these values. These are binary (base > 2) measurements. > > > > To Determine Decimal Capacity: > > A decimal capacity is determined by dividing the total > number of bytes, by the number of bytes per gigabyte > (1,000,000,000 using base 10). > > > > To Determine Binary Capacity: > > A binary capacity is determined by dividing the total > number of bytes, by the number of bytes per gigabyte > (1,073,741,824 using base 2). > >This is why different utilities will report different > capacities for the same drive. The number of bytes is the > same, but a different number of bytes is used to make a > megabyte and a gigabyte. This is similar to the > difference between 0 degrees Celsius and 32 degrees > Fahrenheit. It is the same temperature, but will be > reported differently depending on the scale you are using. > > > > > > > >--------------------------------------------------------- > ----------------------- > > > > > > > >Various Drive Sizes and their Binary and Decimal > Capacities > > > > > > > > Drive Size in GB Approximate Total Bytes Decimal > Capacity > > (bytes/1,000,000,000) > > Approximate Binary Capacity (bytes/1,073,724,841) > > 10 GB 10,000,000,000 10 GB 9.31 GB > > 20 GB 20,000,000,000 20 GB 18.63 GB > > 30 GB 30,000,000,000 30 GB 27.94 GB > > 40 GB 40,000,000,000 40 GB 37.25 GB > > 60 GB 60,000,000,000 60 GB 55.88 GB > > 80 GB 80,000,000,000 80 GB 74.51 GB > > 100 GB 100,000,000,000 100 GB 93.13 GB > > 120 GB 120,000,000,000 120 GB 111.76 GB > > 160 GB 160,000,000,000 160 GB 149.01 GB > > 180 GB 180,000,000,000 180 GB 167.64 GB > > 200 GB 200,000,000,000 200 GB 186.26 GB > > 250 GB 250,000,000,000 250 GB 232.83 GB > > > > > >-- > >Carey Frisch > >Microsoft MVP > >Windows XP - Shell/User > > > >Be Smart! Protect your PC! > >http://www.microsoft.com/security/protect/ > > > >--------------------------------------------------------- > ---------------------------------------- > > > >"John" <anonymous@discussions.microsoft.com> wrote in > message: > > news:976a01c3eaab$04c32170$a001280a@phx.gbl... > > > >| I am having the same problem with Windows XP Home > edition > >| when I attempted to add a new WD 160GB drive. I have > read > >| many articles and have done the following: > >| > >| 1) Service Pack 1 is installed > >| 2) My Atapi.sys file is version 5.1.2600.1135 > >| > >| My Bios sees the drive as 160 GB. > >| My Device Manager/Disk Drives sees it as 152625MB. > >| Disk management sees it as 149.05GB. > >| > >| I have initialized the disk but have not yet > partitioned > >| or formatted the drive. > >| > >| Why doesn't XP see the full drive and how do you fix > this > >| problem??? > >|
- Next message: anonymous_at_discussions.microsoft.com: "nvidia driver headaches"
- Previous message: C Eichhorn: "A required section was not found in the INF"
- In reply to: John: "Re: XP does not see all of a WD 160GB drive that was added as a slave"
- Next in thread: Shenan Stanley: "Re: XP does not see all of a WD 160GB drive that was added as a slave"
- Reply: Shenan Stanley: "Re: XP does not see all of a WD 160GB drive that was added as a slave"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading