Windows 7 pro 64bit slooow boot with new MOB and CPU.. slower than old ones

[djgriff]

Re: Windows 7 pro 64bit slooow boot with new MOB and CPU.. slower than old ones

Western Digital has free software that you can download.
The safest way is to boot with the WD software on a bootable usb or optical drive and disconnect all all drives from your system except for the 500GB WD drive.
You can use their diagnostic software to write zeros to the beginning and end of the drive.
WD also has disk partitioning software that will let you format, create, or delete partitions.

The WD options will be simpler and easier than run win7's repair option from the installation DVD, where you would need to run Diskpart and manually enter the correct command sequence.

If you have other drives installed when using any of these options, you run the risk of accidentally deleting the wrong partition.

Hi Thanks for the reminder to the software,, completely forgot about it..

one thing i am finding puzzling is that i can only get 465Gb out of the 500gb disk..

Is this normal?

cheers

Daniel

[profJim]

Re: Windows 7 pro 64bit slooow boot with new MOB and CPU.. slower than old ones

Perfectly normal!
1 gigabyte for drive manufacturers is 1000 x 1000 x1000 bytes.
1 gigabyte in the operating system is 1024 x 1024 x 1024 = 1,073,741,824 bytes.

This means that the operating system reports about 7.37% smaller disk capacity.
500 GB divided by 1.073 = 465 GB, or 500 x 0.9263 = 465

To further confuse things, 1 megabyte = 1024x1024 bytes in the operating system which equals 1,048,576 bytes.
A 500 MB rated drive would be reported as having 477 MB of space which is 4.86% smaller disk capacity.

Confused??

To prevent brain overload (aka brain fart) I'm not including the math for terabyte drives, except to say that 1 trillion = 1000 x 1 billion ;)

[Acebmxer]

Re: Windows 7 pro 64bit slooow boot with new MOB and CPU.. slower than old ones

Perfectly normal!
1 gigabyte for drive manufacturers is 1000 x 1000 x1000 bytes.
1 gigabyte in the operating system is 1024 x 1024 x 1024 = 1,073,741,824 bytes.

This means that the operating system reports about 7.37% smaller disk capacity.
500 GB divided by 1.073 = 465 GB, or 500 x 0.9263 = 465

To further confuse things, 1 megabyte = 1024x1024 bytes in the operating system which equals 1,048,576 bytes.
A 500 MB rated drive would be reported as having 477 MB of space which is 4.86% smaller disk capacity.

Confused??

To prevent brain overload (aka brain fart) I'm not including the math for terabyte drives, except to say that 1 trillion = 1000 x 1 billion ;)

I do the simple math, 4x 2tb drives in raid10 = 4tb data usable space in windows is 3.63tb So lose 370GB of space. So as ProfJim stated this is normal and should have been correct over the years by now. Either MFR of hdds need to change to state what the size of the is going to be in windows or make the drives larger so after conversion you get what is stated on the drive; or Windows should change its calculation.

[djgriff]

Re: Windows 7 pro 64bit slooow boot with new MOB and CPU.. slower than old ones

Lol.. Weill i have learnt somthing new today.. If some what confusing, thanks though clears up the confusion..cheers peeps

[djgriff]

Re: Windows 7 pro 64bit slooow boot with new MOB and CPU.. slower than old ones

AAh i found another issue with the USB 3 , if you have any device attached to this port when booting up it will also cause Windows to hang for a good 30-40 seconds before the desktop appears. otherwise it boots in about 15-20 secs.

just thought i would mention if anyone else has this issue.

cheers

Daniel

[profJim]

Re: Windows 7 pro 64bit slooow boot with new MOB and CPU.. slower than old ones

Microsoft has nothing to gain by using the technically correct format of the computer industry.
The confusion comes from the common use of the metric system which uses the traditional decimal base system where prefixes are based on a power of 10. Much as I hate to side with M/S on anything, I blame the drive manufacturers for the misleading drive size descriptions.

For any of you with strong masochistic tendencies, check out the File Storage Capacity by Bits and Bytes table in Conversion Calculator Bit Byte Kilobyte Megabyte Gigabyte Terabyte Petabyte Exabyte to see how the size discrepancy grows as disk capacity grows to the next level.

For those who don't want a headache understanding the article, here's a brief summary:

• Kilobyte loses ~2.4% (1.024¹)
• Megabyte loses ~4.9% (1.024²)
• Gigabyte loses ~ 7.4% (1.024³)
• Terabyte loses ~ 10.0% (1.024⁴)
• Petabyte loses ~ 12.6% (1.024⁵)
• Exabytes loses ~ 15.3% (1.024⁶)
• Zettabyte loses ~ 18.1% (1.024⁷)

For those who are mathematically advanced, you can compute how much disk space will be "missing" when a drive manufacturer makes the first one Googolplex hard drive which has 10¹⁰¹⁰⁰ bytes. Googolplex - Wikipedia, the free encyclopedia
Gotta go get an aspirin, I've got a headache.