Has anyone produced a GUI yet for JKD 3.15?
Has anyone produced a GUI yet for JKD 3.15?
Pay attention, have you not read the posts directly before yours
Sorry about that. For some reason, I thought this GUI was still back on 3.12 or 3.13.
Sorry about that. For some reason, I thought this GUI was still back on 3.12 or 3.13.
It'll work with whatever version of JKD you've got. Its only a front end, all it does is send the commands you select to JKD and as the last few JKD versions have only been bugfixes (ie no new features) the gui doesn't need to be updated, ie it'll work exactly the same with JKD 3.12 as it will with 3.15.
For that GUI though you will need to download JKD itself seperately from the JKD Homepage.
I've started to really like this GUI and may even stick with it even after Ewieldra releases his updated GUI, which is the one I've always used before (unlike the GUI above his needs to be updated as he hasn't yet got the new JKD features/commands built into it)
Thanks for the help. I guess I misunderstood how this GUI worked -- thought the JK app was integrated/embedded into the GUI itself. O well, live and learn.
The GUI for JkDefrag 3.15 has been released: http://www.emro.nl/freeware/
The GUI for JkDefrag 3.15 has been released: http://www.emro.nl/freeware/
Well just had a look at it, the way it handles exclusions and including spacehogs is exactly the same as the JKD Starter GUI I've been using recently. I thought he would maybe add a browsing ability so that those who didn't quite understand how to include/exclude files could just browse to them and include them. On the plus side that means I can just copy and paste my inclusions and exclusions from JKD Starter to this to try it
Its also about three times the size of JKD Starter (only 3Mb though). Plus I don't like that Ewieldra's GUI has to be kept open when defragging using about 10Mb of memory, JKD Starter can be closed once defrag starts which is important if defragging with as little running as possible (to obtain a better defrag/optimisation result).
The only advantage it has is that it keeps the disk display visible when defrag finishes, JKD Starter goes to a blank screen. I don't think that alone is enough for me to switch back to this GUI though, I'll be sticking with JKD starter.
Version 3.16 released: http://www.kessels.com/JkDefrag/index.html
JkDefrag v3.16 (June 22, 2007)
Changes:
- Changed the message in the docs about the screensaver under Vista, it works if User Account Control is turned off.
- Bugfix in "-a 3" (fast optimize). It would not use Perfect Fit for gaps that were larger than all the data already processed.
- Bugfix in "-a 6" (move to end of disk). Files in zone 1 would not be moved.
- Added some translations of "Program Files" to the build-in list of SpaceHogs:
Archivos de programa (Spanish)
Arquivos de programas (Brazilian Portuguese)
Ohjelmatiedostot (Finnish)
Program Files (All others)
Program (Swedish)
Programas (Portuguese)
ProgramFiler (Norwegian)
Programme (German)
Programmer (Danish)
Programmes (French)
Programmi (Italian)
- Fixed a typo in the "System Volume Information" string in the SpaceHogs.
- Fixed the displaying of the zone number, should have been + 1.
For programmers:
- Changed the "makefile.bat" script, "JkDefrag.exe" does not need to be linked with "JkDefragScreenSaver.res".
@JDPower
Some replies on your comments
- The reason why my GUI is much bigger than JKD is simply, you don't have to download JKDefrag because it's built in and it has more functions.. Installer / Uninstaller / Screensaver / 64 bits support / more languages all these files are added..
- There's no special reason why my GUI stays open .. it returns to JKDefrag because maybe you want to defrag another folder/file/drive .. and 10MB memory .. ???? Windows Live Messenger takes 25 Skype 25 and i can't think off any reason why 10mb more memory improves defragging.. but this option can be implemented.. no problem at all
- And JKD Starter uses the same as my GUI does, for excluding/including/Spacehogs the reason is simpel .. browsing for files and folders is possible but browsing for *.log and other wildcards is not possible.. futher the help button which is added the the inputbox explains enough i think
Emiel
@JDPower
Some replies on your comments
- The reason why my GUI is much bigger than JKD is simply, you don't have to download JKDefrag because it's built in and it has more functions.. Installer / Uninstaller / Screensaver / 64 bits support / more languages all these files are added..
- There's no special reason why my GUI stays open .. it returns to JKDefrag because maybe you want to defrag another folder/file/drive .. and 10MB memory .. ???? Windows Live Messenger takes 25 Skype 25 and i can't think off any reason why 10mb more memory improves defragging.. but this option can be implemented.. no problem at all
- And JKD Starter uses the same as my GUI does, for excluding/including/Spacehogs the reason is simpel .. browsing for files and folders is possible but browsing for *.log and other wildcards is not possible.. futher the help button which is added the the inputbox explains enough i think
Emiel
I wasn't criticising, I think you know from the JKD forum I'm a fan of your GUI, was just giving a comparison. Different GUI's work best for different people.
I take your point about the size of the GUI, a slight oversight on my part on the reason for the difference (JKDStarter is still only 820Kb including JKDefrag).
My reason for mentioning the memory the GUI uses is simply because, as I mentioned, most times I like to have as little as possible running when I run JKD (and generally have as little as possible running for general usage too). 10Mb is still 5 times more than my AV and if it doesn't actually need to be running, it would be a good feature to be able to close it.
Finally my comment about about the inclusion/exclusion method was not a criticism, as I said it was actually quite useful (and will be in future if I switch back to your GUI).
I can understand you being defensive about your GUI but I was merely offering a comparison between the two and for my usage JKDStarter is most useful for me at present.
As long Emro is contributing to these forums, would he be so kind as to inform us if the 0.8 GUI could safely be used with JKdefrag version 3.16?
I see that your upcoming version 0.9 has been upgraded to 3.16, but since it's only a front end for the exe file, would it still be safe to use 3.16 or should we continue to use 3.15?
As long Emro is contributing to these forums, would he be so kind as to inform us if the 0.8 GUI could safely be used with JKdefrag version 3.16?I see that your upcoming version 0.9 has been upgraded to 3.16, but since it's only a front end for the exe file, would it still be safe to use 3.16 or should we continue to use 3.15?
Apologies for butting in but should work absolutely fine, there were no feature additions between 3.15 and 3.16 so shouldn't have any effect on the GUI.
Here is a test I tried in a virtual machine.Slim install of XP pro with no pagefile present.
JK is only slightly faster and that's all I have to say atm.
Before any defrag.
After JK defrag.
After Perfectdisk 7 smart placement defrag.