View Single Post
Old 07-03-2019, 12:00 PM   #1
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
Autoadd problems on Windows 10 1903

Since I used my Job Spy plugin's tweak to auto-add from a particular path based on a particular Library, and since that has quit working on my desktop, I have been looking at this.

I have a Windows 10 Home 8" tablet build 1809 with Calibre64 3.44, and auto-add works perfectly. Even with Job Spy's tweak. Even with the auto-add directory on my LAN.

I have been trying to get auto-add to work on my Dell AIO desktop Windows 10 Home build 1903 (a.k.a. 18362.19h1_release.190318-1202) with Calibre64 3.44 for a few days now. All of my auto-add directories are on my SSD.

Running "calibre --ignore-plugins" does not solve it, ever.

Running "calibre-debug -g" shows nothing, ever.

Grasping at straws, and although it certainly should not matter (and it did not), I added the auto-add directories I tested with to the "exclusion" list for both Malwarebytes and Defender. That would have been far too easy.

I wonder if anyone else with the identical build of Windows 10 Home that I have, 18362.19h1_release.190318-1202, has the same problems with auto-add.


To be continued...
DaltonST is offline   Reply With Quote