AllSync & AllDup

AllDup causes sleeping drives to awaken.

It might be nice if it didn't do that - when started from a command-line & passed directory names.

---

alldup 4518

if run from command line
if passed directory

START "" AllDupPortable.exe %XDIRNAME%

on program load
it attempts to enumerate all directories listed in (that may have happened to exist in) Source Folders

& if said directories are on drives that have spun down
then the program is "paused" as the drives spin up

- might be nice, if when run from command-line, along with a specific directory to search,
that it did not try to enumerate anything else


i don't necessarily mind that directories are added to the Source Folders list
- which can be avoided with the -n switch,
but i'd rather not have ones that "happen to be there" from being enumerated,
slowing down load (minimally if drives are already spun up, or a bit more,
significantly if drives have gone to sleep)


i'll note that:

if you use -n, then after doing "whatever", then exiting back to the main window,
you cannot then go & do, again, a Start Search - in order to perform the same
search over again - without first [re-adding] adding the source directory,
(as the directory list would be empty)

You only can fix this problem by removing all source folders from these "sleeping" drives from the source folder list.

Another solution could be to add a new command-line parameter to avoid loading the source folder list.
But this will lead to an empty source folder list after restarting AllDup...

You only can fix this problem by removing all source folders from these "sleeping" drives from the source folder list.

Which may then very well "awaken" them when you do .

One could "hack" config4.ini...

Another solution could be to add a new command-line parameter to avoid loading the source folder list.
But this will lead to an empty source folder list after restarting AllDup...

I switch to simply bypass reading (but leaving existing, & also adding new, command-line passed directories) would be nice.

All, in all, not a big deal.
(And not even something I've run into particularly, except on odd occasion.)

Actually, looks like I can do this with, -n.


If I create a Profile, NOEXISTINGDIR, in which I remove the [Ordnerlist] section entirely,
then I can run something like: & that looks to do what I want.

On load, no existing directories are in the NOEXISTINGDIR Profile,
so that should not cause any sleeping drives to load (I suppose,
& my passed directory (C:\TMP\DRIVERS2 or %XDIRNAME%...) loads & scans,
& when I exit back to the main screen, my (command-line) specified directory is there,
so if I need to rerun a scan, all I need to do is to hit, Start Search.

(The only thing that does not do is to save the search directory - unless I actually go to the Profiles & specifically tell it to Save.)


Hmm...

I'll have to see if ("sleeping drives") is worth the effort... ?


Hmm2...

Actually, unexpectedly, config4.ini is being hit... ?
heh, stupid mistake... let me see...
no, actually, i'm good (did not a mistake), so what's going on...?


Oh, so a Profile is only a subset of config4.ini.
And config4.ini gets updated on exit even if a Profile is used.


Easy enough to swap config4.ini's before actually starting AllDup...
If it's worth the effort .