Dean-Ryan Stone
Kazakhstan
4.2.5 (Nov 3, 2009)
In addition to my note below, this version also takes an unnecessarily long time to analyze the drive. There's still opportunity for some major procedural optimization in this area. Every other defrag program generates a drive analysis about five times faster. Perfectdisk screams by comparison. I'm definitely hanging around to see what develops with MyDefrag but there's still plenty of sawdust on the ground with this program right now.
4.2.4 (Oct 27, 2009)
Update: v4.2.5 is out. STILL not usable. Ran for about 8 hours on my C: last night and never got past 13% of completing zone 1 of 15. I recommend people continue to avoid this until the major bugs (such as running for over 8 hours without getting more than 13% of the first zone completed) are ironed out.
Changelog for v4.2.5:
* Added the !InstallDirectory! macro.
* Added the !ScriptDirectory! macro.
* Added the !ExecutableDirectory! macro.
* It is now possible to use macros inside included files.
* Added the * ProcessPriority setting.
* The MakeGap() and AddGap() functions before v4.2.4 would automatically scale down a gap if it would not leave enough room for the remaining data to be processed. This limiting is now removed.
* Added an extra test to make sure the script chooser will only list "*.MyD" files, and not for example "*.MyD~".
* Fixed an infinite loop for unmovable NTFS compressed files.
* Fixed a bug that prevented the PreventScreenSaving() and PreventPowerSaving() settings from working if they were placed in the Settings.MyD file.
* Fixed an infinite loop problem for extremely rare cases where the Microsoft defragmentation api returns an empty list of extends.
* Change the tree locking timeout from 15 minutes to 2 minutes.
----------
v4.2.4 is probably worth trying again for those people who thought it was slow. The slowness was usually due to the presence of compressed files on your HD which the program always had a problem with - note that when I say "compressed" I'm talking about NTFS compression, not things like zip. This version has a bugfix for that.. giving a tentative four stars until I test it tonight. In the meantime, here's the changelog for this release:
* Fixed a bug in the Title() setting that caused it not to replace macros.
* Fixed a bug where a change in the size of the windows would not be remembered if the windows were not moved away from the top-left of the screen.
* Added a parameter to * PlaceNtfsSystemFiles to set the size of the NTFS reserved area.
* Added the !ProgressPercentage! macro.
* The script chooser will no longer display volumes that are excluded with ExcludeVolumes() in the Settings.MyD file.
* Changed the syntax of the * MakeGap and * AddGap actions. It is now possible to place zones anywhere, they do not have to be placed one-after-another from the beginning of the disk.
* Changed the default scripts so that the MFT, some other NTFS system files, and the directories, are now placed 30% into the data on the disk.
* Fixed a bug in the screensaver that would not display the progress percentage.
* Fixed a bug in the graphics code that will properly show StatusBar(path) if StatusBar(Status) is not specified.
* Changed the vacate function so that when there are no gaps above the end of the zone, it will use the highest gap available. Before it would use the first gap available.
* Changed the default script for the screensaver into Optimize Daily. Before it was Optimize Weekly.
* Changed the default setting for the status bar of the screensaver into Full Status Bar. Before it was No Status Bar.
* The positions of the windows are now also saved when the windows are moved and not only when they are resized.
* If the Windows defragmentation API has not succesfully moved an NTFS compressed file then MyDefrag will no longer try to move the file with the alternative method, but leave the file where it is and mark it as unmovable. The alternative method is extremely slow for compressed files.
* Made a change that should increase the chance of succesfully moving files on Windows 2000 machines. Sometimes files could not be succesfully moved and they would be marked as unmovable.
* Fixed a bug that caused unnecessary work and unfilled gaps at the end of a zone for the SortBy fileactions.
* The script chooser window will now list scripts that contain a syntax error. The description of the script shows the error.
* Fixed a bug where the subroutine that determines if a file is fragmented (see the IgnoreWrapAroundFragmentation setting) would treat gaps as unmovable.
* Fixed a bug that caused the program to skip very big FAT volumes.
* If the Sortby fileactions find two files to be equal (for example SortBySize and files with equal size) then the program will now also compare the Inodes. This reduces the number of filemovements.
* The !Include PATH! macro is now evaluated before any other macros, so that macros inside the included file will be processed.
1.8.8 (Oct 26, 2009)
Lockhunter is rubbish. For example, I just started the installation of Unlocker 1.8.8 (I have 1.8.7) installed. Like Aegis69, the installation was telling me that c:\program files\unlocker\unlockerhook.dll was locked. I rightclicked on it in Explorer and asked LockHunter to tell me what's locking the file. Answer? No processes found. Rightclicked and had Unlocker tell me the same thing - about seven or eight processes listed. Click on "unlock all", try again, and the file gets updated fine. Now, maybe Unlocker itself is retarded for not being able to unlock one of it's own files during it's own update procedure, but I've been using it in a practical sense for years and it's worked great every time. If you have 32bit, this is the one to get. Hopefully Cedric Collomb, oh, I'm sorry, "Keyser Soze" can update it for 64bit sometime soon.
6.3 (Oct 22, 2009)
"Evil Maid" attack. Cracked me up *8-)
"Housekeeping!" (looks left) (looks right) (tiptoes into room with feather duster in one hand and USB thumbdrive in the other)