/hydrus/ - Hydrus Network

I'm sorry you are having a problem. Thank you for reporting it.

You are running my compiled exe, right? Not from source? Did you move your hydrus installation folder from the old windows to 8.1, or did you start a fresh install?

Also, do you happen to have OpenCV installed separately to hydrus? By the looks of your trace, that is what is causing the problem.

If you check your installation directory, do you have a load of opencv_blah249.dll type files? If you have ***248.dll as well, that could be causing a conflict, or it could be being caused by another, subtler mismatch of dll versions. These sorts of files are sometimes left over from an old version, and your OS upgrade may have triggered the problem. My laptop is 8.1 and I obviously upgrade every week and I haven't had this problem, but every environment is slightly different.

If you have some of these legacy files hanging around, or even if you don't see anything obvious, making a fresh install may fix your problem. Backup/move your database somewhere safe, delete the existing install folder completely, make a new install, and copy/move your database back again. I can talk you through any of these steps if you like. If it doesn't work, or you are getting a problem from a fresh install already, I can make a special build for you that'll try to name the exact dll causing the problem.

Please let me know how you get on!

>>587

I installed (always use precompiled win exe) the newest version over the existing Hydrus Network directory on my second harddrive. (v. 147 -> 152)
After that didn't work, I downgraded to the last known working version which is 147 with the old installer exe and noticed that it still doesnt work. Each time overwriting the target folder files obv. No fresh install. I'll try a fresh install in a minute tho and report back in case that works.

>OpenCV

I have no idea what opencv is, therefore I don't think I have it installed separately. Unless some other tool installed it without my direct knowledge. A quick search of "opencv" didn't turn anything up so I think I'm good.

>Backup/move your database somewhere safe

Just for clarification: Is it enough if I backup the db/client.db file? (Currently 260+MB) Or do I have to back up the image directory as well? Because that thing is huge.

And how would I go migrating my existing db into a fresh install (should both have the same version or are different versions ok? like migrating 147 db into 152 fresh install?)

a thing i forgot to mention: the first crash is due to antivirus detecting some dll files as a virus. Error message says dll could not be accessed because of that. I use avast free snakeoil faggotry and I currently can't reproduce the exact error message, but even on a fresh install (152) the same crash occurs.

ok i disabled that shitty antivirus and installed and started the client successfully. Something fishy is there and unless you don't have a bitcoin troyan child raper hidden somewhere, avira cries foul. Any Idea besides uninstalling it?

>>588
>>589

Thanks for this update!

There's a guy in the v151 release thread who is also having Avast problems, so absent my dev machine being infected and actually propagating viruses, I think some incorrect virus detections got released, and something in hydrus is triggering a false positive.

Do you know what dll files are causing problems for you? I was going to suggest you email them to me, but gmail will probably bug out at dll attachments. If you can figure a way to 7zip and email them or whatever, or throw them up on mediafire or something, then I can look at exactly what is going wrong.

For backing up, copying client.db is good for a quick backup, especially if you are dealing with update testing, but the db isn't much use without the files and thumbnails, so it is nice to have those backed up if you can. If you don't have the space, the you can just backup that one file, and you'll be able to recover pretty good from most accidental problems, like hard drive sectors dying.

If you do have the space, I suggest you do a regular sync of the whole db folder to an external hard drive (I use FreeFileSync, which makes this job take about ten minutes a week), so that if you get complete hard drive failure, you don't lose everything.

Migrating a client is easy. Just move/copy the contents of the db folder to the other client. Make sure neither client is running when you do the move. The versions don't have to be the same, but don't try to go backwards (e.g. v152 db running on a v147 client).

>>592

I always figured that sends exe paths and hashes to some Microsoft/NSA server somewhere, so I have mine turned off out of paranoia. I guess the free anti-virus programs probably do the same, but I just feel queasy letting MS approve my stuff.

I also assumed the actual defence part of it was some piece of shit they threw together for insurance liability. It is actually good? I currently use Avira, which spams 24/7 and false-positives on pretty much anything not 100% legit Illuminati approved.

>>592
good point. uninstalling in 3..

>Do you know what dll files are causing problems for you? I was going to suggest you email them to me, but gmail will probably bug out at dll attachments. If you can figure a way to 7zip and email them or whatever, or throw them up on mediafire or something, then I can look at exactly what is going wrong.

I'm not good with python so I'm not sure what i need to do to dump the error string where the filename is, so far I couldn't read the suspicious dll filename from any logs or system messages.

I'll try one last time with the antivirus and see which file(s) he detects and maybe tries to delete or quarantine. I'll report back if something comes up, else i'll just go with it.

I've been having this issue as well. The file that avast is having problems with is opencv_legacy249.dll
A swift disable before installation allowed me to get it through, but I turned it on and then booted Hydrus up again and it yanked the file.

>>628
Even after I add the file to the global list of exclusions, it still grabs it and throws it in the chest. I'm updating avast right now to see if that'd patch it up.
Also, I'm on Win 7

>>629
Avast updated.
Redid installation. Didn't get a hang up.
When I opened Hydrus, it gave me the same issue as earlier in >>628 but this time I was able to add it to the exceptions in the Virus Chest and it's working fine.

Thank you for the update on the bad dll. I am upgrading to opencv 2.4.11 right now, so please let me know if the new opencv_legacy2411.dll causes similar problems in the next version.

I removed some old cv code, which the legacy dll was probably supporting, but my make-an-exe program is including it anyway. It is possible that my removing the code will stop the exe from trying to load the dll, but I'll keep looking for a way to exclude this file completely, as I don't think I really need it.