Extending the actual arguments in commandline

[MichelRx]

It could be very functional replacing dir/filesnames by files containing this off the dir/filesnames concerned.



jkdefrag -a 3    -e c:\dir1\dir2\dir3\bigfile_1.ext     -e c:\dir4\dir5\dir6\bigfile_2.ext    -e c:\BigDirectory\*   -e ...  -e ... c:

could be changed with :

jkdefrag -a 3 -E c:\example\ExcludeList.job  c:

                     ExcludeList.job being an ascii file, containing :

                                                             c:\dir1\dir2\dir3\bigfile_1.ext
                                                             c:\dir4\dir5\dir6\bigfile_2.ext
                                                             c:\BigDirectory\*   
                                                             -e ... 
                                                             -e ...
                                                           
In the first case, the exclude file can be very long : number of files AND number of characters used, not supported.
And the secund situation make easy to create complexe defragmention, especialy via BATCH files...

--- choosing files that have to be "classicaly) defragmented (-a 3) 
--- moving at the end of the disk (-a 6), like big and old archive files,
--- moving at the first beginning of the disk with size sorting (-a 8) for continuously used but never changer files...

REM
REM        Example of very little and silly batch file, with three passes
REM
REM        (1) Moving lot of big and old files at the end of the disk
REM
defrag -a 6 -E c:\ToTheEndFiles.ext
REM
REM        (2) Moving and sorting continuously used and rarely changer files
REM
defrag -A 8 c:\UltraUsedFiles.ext
REM
REM        (3) Defragment and fast optimize of the rest of the disk
REM        with exclusion of the previous -A 6 et -A 8 files
REM
defrag -a 3 -E c:\TotalOfFilesToExclude
REM
END

[jeroen]

Thanks for sharing your idea, I appreciate it! You are right, the commandline is overloaded, it's too limited for long lists of excludes. A possible way to overcome the limitation is creating include files such as you describe. But then there would also have to be an exclude file for defining spacehogs. And there are a lot of other things I would like to implement, but the commandline.... Thinking along these lines I decided some time ago to make a small scripting language. Everything in a single file. I am working on that right now, it will be v4 of JkDefrag. Progress is slow, I am very busy with other things that are demanding my time. But it will come, some time in the future....

[MichelRx]

I undertand very well ! It's easy to have an idea, without having to accomplish it ! And it's easy to imagine that jpdefrag is not the only occupation in your life ! That my little idea is the thousandth ! I only sent you that because i notice the "Requests for new features "!

IMHO, jkdefrag could be an inescapable and unique way to solve the worse part of our computers: HARD DISK. Having a few HD for various functions: not a so good solution. I made tests, in the past, with loony methods: it's really possible to double and more the speed of the operations of our computers.

And "graphic", easy-to-use softwares... are very limited. some "sysinternals" (for example) are inescapable to.

(An other solution: using RAM disks... Other problem).

BON COURAGE !
and MERCI !

[MichelRx]

Bonjour, Jeroen !

About my suggestion : it can be very sophisticated.

But i think that the basic function has priority and is enough for the moment : making possible to have more treated files.

It's not a revolution but it's greatly improve the reasons to user jkdefrag.

Amicalement!
Michel

[poutnik]

You are right, the commandline is overloaded, it's too limited for long lists of excludes.

Well, not so much limited.
W2k is said to allow about 2k command line length and XP even 8k.
And if one uses editor with wrapping long lines.......