Jump to content

I broke the 6,000 barrier on the pit test


brandon
 Share

Recommended Posts

It is clocked @ 800Mhz stock.

 

Edit: IG, while you're here, there's a problem with the pit test... It assumes Windows is installed on the C: drive, whereas in my case, it is installed on D:. Even though it is in beta status, the fact that it assumes which partitions Windows is installed on is disheartening.

Edited by brandon
Link to comment
Share on other sites

Edit: IG, while you're here, there's a problem with the pit test... It assumes Windows is installed on the C: drive, whereas in my case, it is installed on D:. Even though it is in beta status, the fact that it assumes which partitions Windows is installed on is disheartening.

 

 

Where are you seeing that? In your results when I click on Software>Processes> then any process it is showing Windows installed on D:

 

http://pcpitstop.com/betapit/tips/swdetail...report=Software

Link to comment
Share on other sites

Test result is saying that C: drive is fragmented:

 

http://pcpitstop.com/betapit/tips/DskOpt.asp?conid=21006964

 

It doesn't make a difference if the OS is installed on there or not. That result is only for fragmentation.

 

Only the C: drive is checked for fragmentation because of the time it takes to scan a drive. The goal has always been to keep the test as fast as possible. To that end, it was an arbitrary decision that only the C: drive would be tested. It would be possible to first locate a Windows install and only check that drive, but that adds time back to the length of the test. As something like 98% of the computers tested have the Windows install on C:, we felt that it was an acceptable compromise.

Link to comment
Share on other sites

Test result is saying that C: drive is fragmented:

 

http://pcpitstop.com/betapit/tips/DskOpt.asp?conid=21006964

 

It doesn't make a difference if the OS is installed on there or not. That result is only for fragmentation.

 

Only the C: drive is checked for fragmentation because of the time it takes to scan a drive. The goal has always been to keep the test as fast as possible. To that end, it was an arbitrary decision that only the C: drive would be tested. It would be possible to first locate a Windows install and only check that drive, but that adds time back to the length of the test. As something like 98% of the computers tested have the Windows install on C:, we felt that it was an acceptable compromise.

 

That clears things up for me. All I needed was an explanation as to why, and I got a good one. :tup:

Link to comment
Share on other sites

  • 2 weeks later...
  • 5 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...