disParity » General Discussion

Not Scan Upon Opening

(10 posts)
  1. cybrsage
    Member

    Is there a way to prevent the program from scanning all my drives upon opening it? There is a button I can press to have it check the current status if that is what I want.

    If I know I changed something and therefor want to do an update, I have to wait as the program scans my locations, press the update button, and then wait as it scans them all over again.

    If all I want to do is add another location, I have to wait while it scans everything when I know nothing has changed.

    Basically, I view the initial scan as a waste of my time since everything else I do causes another scan to happen anyway. Is it possible to turn it off?

    Posted 1 year ago #
  2. Klaatou
    Member

    hello, don't you have the cancel button on the lower right ?

    Posted 1 year ago #
  3. cybrsage
    Member

    How does that prevent the scan from starting, which (as most people would have understood from the thread title) is the purpose of my post?

    Posted 1 year ago #
  4. Roland
    Roland

    There is no way to prevent the initial scan on startup. Klaatou is correct that pressing "Cancel" will halt the initial scan, but it won't prevent it from starting.

    The initial scan is meant to complete quickly. Is it taking a really long time to complete? This sounds familiar, like someone else brought this issue up a while back.

    My thinking, anyway, is that disParity is an app that is meant to be left running. That's how I use it, anyway. So, the initial scan on startup is something that you rarely have to sit through. However if you only run it when want to do an update and then close it again afterwards, the initial scan does seem redundant. On the other hand I don't like the idea of disParity coming up and just sitting there dumb with ? marks on all the drives because it hasn't done an initial scan. I'll have to think about a better way to handle this.

    Posted 1 year ago #
  5. Klaatou
    Member

    cybrsage even if I'm french I understood your question, what I didn't get was when you write about your wasting of time as I don't see why you have to wait the first scan when you can cancel it (in the state of the soft currently)... all that said very friendly as I'm sure you did :)
    As said Roland we already spoke of that and it reminds me another thing why I'm shutting down Disparity after an update and start it again next days making me have the habit to cancel the first scan to launch the update : I don't let it run because it eats a lot of memory, even "sleeping" after an update. (not far from 800MB Ram)

    Posted 1 year ago #
  6. cybrsage
    Member

    Yeah, I always close it down - I close everything I am not currently using. I even removed the "call home" to check for updates on all the things like flash and java (but not the anti-virus of course).

    It just seems a very unneeded step. If it scans when I open it, why scan again when I do anything with it half a second after the scan is done. Why bother scanning on startup at all since everything you do requires a scan before it starts?

    Yes, I can push the cancel button to make it stop doing an unneeded task - the better solution is to not require me to have to manually stop the unneeded task in the first place by not running the unneeded task. :)

    Posted 1 year ago #
  7. freehand
    Member

    I agree with cybrsage that an option to disable the scan on open would be nice. The scan for me takes a bit and I always have to wait till it finishes before I can hit update. Yes I could hit cancel but I shouldn't have to as it just seems wrong.

    Roland what about adding some command line arguments to either disable the initial scan or even trigger a specific command like an update? That way the GUI isn't showing a bunch of drives with question marks because it would still scan right away but only once for the command requested.

    Posted 1 year ago #
  8. Roland
    Roland

    The next version of disParity will have the automatic update feature, which will change a few things. One significant change is that, with the feature active, disParity watches drives for changes and won't rescan a drive that has had no changes since the last scan. This means that after the initial scan, if you do an "Update", it won't do a second scan at all (assuming there have been no further changes since you launched disParity.) It also means that when you launch disParity, it will update automatically (after a configurable amount of time has passed) if the initial scan indicates changes have occurred.

    Posted 1 year ago #
  9. BloodlustMAC
    Member

    I would not advise / advocate an automatic update feature by default (may be a user selectable option - default not active).

    This feature would be causing me issues now if I had it selected.
    I had corruption / encryption on multiple files across the drives that make up my parity set.
    At least without that feature I am able to delete/move to another drive and undelete potentially corrupted files and therefore attempt recovery.

    So as I said by all means have the feature but not as a default behaviour, it could be a disaster in the making.

    Posted 1 year ago #
  10. Roland
    Roland

    Automatic updates will not be enabled by default. The default mode will be one where it monitors the drives for changes and lets you know that an update may be needed, but it won't take any further action.

    Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.