PerfectDisk 8.00.50
Posted by Mihai Asmanow on 02 February 2007 - 21:52 · 3 comments & 1938 views
- Advertisement
-
-
(1 reply)
#1 Posted by Jeremy of Many on 03 Feb 2007 - 00:52
- Schedules? What schedules? Oh, that's right... I'm using Diskeeper 11 which is invisible and automatic, I forgot what a schedule is!
*Takes a look at fragmentation levels*
0% and 0% excess fragments on D:.... interesting... -
#1.1 Posted by .AlleymaN on 03 Feb 2007 - 03:32
- Quote - (Jeremy of Many said @ #1)Schedules? What schedules? Oh, that's right... I'm using Diskeeper 11 which is invisible and automatic, I forgot what a schedule is!
*Takes a look at fragmentation levels*
0% and 0% excess fragments on D:.... interesting...
Good for you!
-
#2 Posted by +hayc59 on 03 Feb 2007 - 06:49

This build is highly recommend for Vista users.
Raxco, during the Vista certification testing process, has discovered and reported to Microsoft a bug in volsnap.sys that can (if conditions are right) cause cause hard drive corruption and loss of the partition.
If you are running PerfectDisk 8 on Windows Vista, it is critical that you update to Build 50. You can do this by clicking on PerfectDisk and selecting Run as administrator and then click on Help and then select Check for Updates.
Please be sure to update immediately.
Submit to reddit
Submit to blinklist
Bookmark on del.icio.us
Add to furl
Share on Facebook
Add to Windows Live
What's new in PerfectDisk build 8.00.50
* PerfectDisk Command Center
1. Fixed a bug which caused excessive delays when changing the password of managed clients.
* PerfectDisk Client
1. PerfectDisk is now Certified for Windows Vista. Minor changes were made to meet the certification requirements.
2. We changed when the last schedule run time is updated to prevent some scheduler conflicts when two or more schedules were set to run at the same time.
3. Fixed a boot-time defrag limitation when external attributes were too large.
4. Fixed a bug in the post defrag statistics. The elpased time and CPU time did not support values greater than 24 hours. This has been fixed.