That ScanDefrag program is exactly what I've been wanting for years in WinXP to automate Check Disk, Disk Cleanup, and Defrag and it sort of reminds me of the one GUI to do it all feature that Win9x had in Maintenance Wizard. I liked it enough to keep it installed and even submit a winapp2.ini entry for it.
I've been meaning to try it out for ages myself but have never got round to it
Latest bugfix version available now and all seems to be fixed: http://www.kessels.com/JkDefrag/
Downloading now. Thanks JD.
There is a promising looking new GUI just released on the JKD forum. Looks nice and simple but functional though i've not given it a proper workout yet (this is not the Ewieldras original GUI that a few of us use but a completely new one by a different user):
Feature list:- supports all command line options of JkDefrag 3.11
- all settings are saved in a plain-text file in the same directory where the executable is
- can also copy the generated command line to the clipboard instead of running it, so you can easily create batch files
- optimizes the generated commandline: default options (like "-a 3") are left out.
- does not require that the JkDefrag.exe is in the same directory as the Starter (doesn't even require that ANY executable of JkDefrag is available on the computer Razz , but it can use any of them (also the command-line version))
- small standalone executable (136 KB uncompressed)
- written in pure C++ and WinAPI -> no additional dependencies
- currently supports two languages: English and German
For download an a screenshot use the following link (page is German):
http://web41.server2.dce4u.de/index.php?me...ragstarter.html
The archive includes the complete Visual Studio 2003 project.
Latest bugfix version available now and all seems to be fixed: http://www.kessels.com/JkDefrag/
Ha ha, spoke to soon, another bugfix version out now that fixes an X64 bug. I've never known a program have so many releases in the space of a few days
And you spoke too soon again JkDefrag v3.14 has been released.
New update again: http://www.kessels.com/JkDefrag/index.html
JkDefrag v3.15 (June 14, 2007)
Changes:
- Added extra breakpoints so the program will quit faster.
- Added special exception for Acronis OS Selector files.
- Changes to facilitate Delphi programmers. All callbacks are now CDECL.
- Added a Pascal example program.
These updates are getting ridiculous.
These updates are getting ridiculous.
Can i trust JKDefrag anymore? What if there's gonna be major bug in some release, that can mess up my files/system? Is JKDefrag reliable anymore...?
Can i trust JKDefrag anymore? What if there's gonna be major bug in some release, that can mess up my files/system? Is JKDefrag reliable anymore...?
My thinking exactly. I am using the GUI version 0.7 and it works absolutely perfect for me. None of the so called improvements in the newer versions are anything I would use so I see no reason to update. If it it ain't broke don't fix it.
My thinking exactly. I am using the GUI version 0.7 and it works absolutely perfect for me. None of the so called improvements in the newer versions are anything I would use so I see no reason to update. If it it ain't broke don't fix it.
Are you aware of the moving of 'spacehogs' to the end of the data, even in the default (fast) optimisation mode. I'm running the latest version now, after hanging onto 3.8 till bugs were sorted, and its working very well. There was alot added to the version of JKD that started the run of bugs so there were bound to be some minor issues that needed ironing out (and they were all pretty minor).
I'm also using that new JKD Starter GUI I mentioned a few posts back (as Ewieldras original gui is yet to be updated) and that also works well.
Can i trust JKDefrag anymore? What if there's gonna be major bug in some release, that can mess up my files/system? Is JKDefrag reliable anymore...?
To quite JK himself (hope he doesn't mind): Even if there was a major bug in JkDefrag then all your data is still perfectly safe. JkDefrag is built on top of the Microsoft defragmentation API and does not access the harddisk by itself. It doesn't even know what a harddisk is, that's why it works on everything that looks like a disk to Windows such as floppies and USB sticks. All JkDefrag does is send commands to the API, basically "move this file to that location".
Are you aware of the moving of 'spacehogs' to the end of the data, even in the default (fast) optimisation mode. I'm running the latest version now, after hanging onto 3.8 till bugs were sorted, and its working very well. There was alot added to the version of JKD that started the run of bugs so there were bound to be some minor issues that needed ironing out (and they were all pretty minor).I'm also using that new JKD Starter GUI I mentioned a few posts back (as Ewieldras original gui is yet to be updated) and that also works well.
No I wasn't aware of the "spacehogs". I will update when Ewieldra updates the GUI.
No I wasn't aware of the "spacehogs".
From JKD homepage
What are SpaceHogs?SpaceHogs are less important files that take up a lot of space. JkDefrag moves them to the slow end of the disk (zone 3), so that all the other files can be moved to the fast end. The internal list of SpaceHogs is (you can add more with the "-u" commandline option):
* Files bigger than 50 megabytes
* Files not accessed in the last month
* ?:\Progam Files\Installshield Installation Information\*
* ?:\RECYCLER\*
* ?:\System Volume Infomation\*
* ?:\WINDOWS\$*
* ?:\WINDOWS\I386\*
* ?:\WINDOWS\ie7updates\*
* ?:\WINDOWS\Installer\*
* ?:\WINDOWS\ServicePackFiles\*
* ?:\WINDOWS\SoftwareDistribution\*
* ?:\WINDOWS\Downloaded Installations\*
* ?:\WINNT\$*
* ?:\WINNT\I386\*
* ?:\WINNT\ie7updates\*
* ?:\WINNT\Installer\*
* ?:\WINNT\ServicePackFiles\*
* ?:\WINNT\SoftwareDistribution\*
* ?:\WINNT\Downloaded Installations\*
* .7z
* .arj
* .bz2
* .cab
* .gz
* .lzh
* .rar
* .rpm
* .tar
* .z
* .zip
* .msi
Could someone explain how Jkdefrag has gone from version 3.7 on February 24 to the recent version 3.15? It almost sounds like the versions are going backwards, unless the older versions are meant as 3.07, 3.08, etc?
Update - I checked his forums and see that the versions are numbered 3.7, 3.8, 3.9. 3.11, etc. It's the equivalent of saying the version after 3.9 is 3 point 10. I'm not sure why he did it this way but I'm not going to question genius and someone who's willing to create and update such a great program for free.
From JKD homepage
Did you notice any performance difference with your computer after using the new version of JK Defrag compared to the older version?
Did you notice any performance difference with your computer after using the new version of JK Defrag compared to the older version?
Its hard to say (as were probably talking miliseconds difference). I ran the 'Sort by last access date' optimisation last night (and added some of my own spacehogs for moving to the end) and launching my most used apps seems a little snappier and with less disk activity. But I could just be imagining it. Either way I'm happy to have those files near the start of the disk and to be able to move big rarely used files out of the way right to the end of the disk data.
So, after all of these updates, do you think it's fairly safe to conclude that 3.15 is pretty much bug free and stable? Also, when do you think we can expect to see a new GUI from Ewieldra?
So, after all of these updates, do you think it's fairly safe to conclude that 3.15 is pretty much bug free and stable? Also, when do you think we can expect to see a new GUI from Ewieldra?
Yes I think its now bug free (judging by the lack of bug reports since the latest version was released).
As for Ewieldra's new GUI version, should be soon. I know he is working on it but was also busy with something else last time I discussed it with him.
In the meantime I can highly recommend the new GUI I mentioned earlier, I like it alot:
Feature list:- supports all command line options of JkDefrag 3.11
- all settings are saved in a plain-text file in the same directory where the executable is
- can also copy the generated command line to the clipboard instead of running it, so you can easily create batch files
- optimizes the generated commandline: default options (like "-a 3") are left out.
- does not require that the JkDefrag.exe is in the same directory as the Starter (doesn't even require that ANY executable of JkDefrag is available on the computer Razz , but it can use any of them (also the command-line version))
- small standalone executable (136 KB uncompressed)
- written in pure C++ and WinAPI -> no additional dependencies
- currently supports two languages: English and German
For download an a screenshot use the following link (page is German):
http://web41.server2.dce4u.de/index.php?me...ragstarter.html
The archive includes the complete Visual Studio 2003 project.
Hmmm, the link in that quote appears to have changed (and its all in German so I can't understand what is on that page), heres a direct link to the JKD Starter GUI download page: http://web41.server2.dce4u.de/index.php?me...wnload=jkds.zip