disParity

disParity » Announcements

1. Roland
   Roland

   Version 0.15 of disParity is now available for download:

   http://www.vilett.com/disParity/disParity0.15.zip

   Changes in 0.15:

   • Added primitive anonymous usage tracking. The first time disParity is run it assigns a random ID to itself, and every time disParity is run it hits a (currently non-existent) URL on my web server with that ID, the command ("create", "update", etc.) that was invoked, and the current version number. No other data is collected or logged. This way the error log on my web server can act as a simple way for me to keep track of how many unique users are running disPartiy and which commands they are invoking. This will influence how much time I spend working on improving disParity in the future. I would also like to eventually expand this mechanism to add support for automatic notification of new versions, and also auto-upload of crash info.
   • Fixed parity corruption bug in the edit detection code. The bug would occur if the edited file's length had changed enough to change the number of 64K parity blocks required to protect the file.
   • Fixed a bug in the handling of zero-length files.

   Posted 6 years ago #

2. Phatty2x4
   Member

   Roland,

   What port are you sending out on and is the destination vilett.com?

   Reason I ask, I have to punch a hole in my firewall, which requires port and destination.

   Posted 6 years ago #

3. Roland
   Roland

   It's a standard HTTP query to vilett.com, so port 80.

   Posted 6 years ago #

4. cartman
   Member

   Nice! Btw my server is not connected to the internet for the time being, so add one offline user to your statistics :D

   Posted 6 years ago #

5. klim
   Member

   hi, i'm new here. thank you for you program. i found it by searching via google on some alternative software raid solution. i've tested it, yes, it's working, but for me it's in too early stages and in some cases a bit uncomfortable (missing some features and gui) for every day use. but you are on the best way, respect. nor whs hasn't such a nice parity calculation functionality.

   a comment to v0.15, it takes very long until the program begins to work.
   from stating, until working there are 42 seconds, i think for anonymous usage tracking. but isn't it very long?

   Posted 6 years ago #

6. Roland
   Roland

   Hi Klim,

   Yes I agree disParity is very "bare bones" and not for everyone. My hope is that enough people will find it good enough to achieve the data protection they need, with a minimum of fuss.

   About the startup delay, that's some strange behavior that I haven't heard of before. It shouldn't be caused by the usage tracking, that runs in a background thread and should not affect main thread execution.

   To be sure, can you do me a favor and try version 0.14 for comparison? You can download it from here:

   http://www.vilett.com/disParity/disParity0.14.zip

   Posted 6 years ago #

7. klim
   Member

   i'd forgot to say that i'd still compared it with 0.14.

   (0.14)
   dos promt: disParity.exe very fast
   dos promt: disParity.exe stats about 1 sec then finished

   (0.15)
   running disParity.exe very fast
   dos promt: disParity.exe stats does 29 sec nothing, then begin working

   the long delay happens with every command
   i've also tried to disable my firewall, nothing better

   Posted 6 years ago #

8. Roland
   Roland

   klim,

   OK I guess that means it must be the new usage tracking causing the startup delay. I can't reproduce the issue here, but I've made a possible fix, can you please download this test version of disParity and tell me if it fixes the problem?

   http://www.vilett.com/disParity/disParity0.15a.zip

   Thanks for your help and feedback!

   Posted 6 years ago #

9. Fernando
   Member

   Hi Roland

   Should I recreate my backup with this new version?

   Posted 6 years ago #

10. Roland
    Roland

    Hi Fernando,

    only if you have reason to suspect you might have corrupted parity due to the edit bug. You can run a "test" command on your largest drive to see if you get any errors, or run "verify", but both of those take just about as long as a "create", so it's up to you.

    Posted 6 years ago #

11. klim
    Member

    startup also with a command is working now as 0.14. thank you.
    you have moved the stats to the end of each command. now the delay is after the command, last time was 31 sec delay, i don't understand why it takes to long. i've a 8mbit internet connection.

    Posted 6 years ago #

12. Roland
    Roland

    Interesting. I didn't actually move the usage logging to a different point in the code, I just moved more of it into its own execution thread. So now it's not blocking the main thread execution anymore, but it's still running when the main thread completes, so it's sitting there blocking program termination.

    I'm curious, what happens when you access the following URL in a web browser:

    www.vilett.com/disParity/cmd=update&id=1234

    You should immediately see a generic file-not-found error page from my web hosting service (Laughing Squid). Does it come up immediately? What if you use Internet Explorer vs. some other web browser? Just trying to narrow down what might be causing this.

    Posted 6 years ago #

13. klim
    Member

    problem found:
    i use firefox for browsing the web (it is set as standard browser on my system) , but internet explorer is still installed.

    i've a german operation system, so the following menus could be a bit different in naming.
    your program takes the internet configurations from the installed internet explorer.
    if the following option is enabled:

    internet explorer-->extras-->internet options-->connections-->lan configurtions-->automatic search for configurations

    then disparity has the 30 delay.

    if not enabled ---> no delay

    so disabled and working, maybe it'll help others too

    Posted 6 years ago #

14. Roland
    Roland

    Alright, thanks, good to know. I'm not surprised that the .NET WebClient class is picking up IE's configuration by default, that's usually how Microsoft stuff works.

    I can easily make a change to terminate the thread if it's still running when the main task is done, so I'll put that in the next update.

    Posted 6 years ago #

RSS feed for this topic

Reply

You must log in to post.