I've tried rebooting and tried on a Win 7 64 bit and a Win 8 64 bit computer but JD just won't work for me in the v3. Any other site gives a fast reply on the login but the JD login seems to freeze for a minute and then give an error.
It will work in v2.5 but the problem in v2.5 is that it frequently hangs and the seed refresh seems like it takes a long time.
Is there any debug to run for v3 to see what it's doing when I try to login to JD?
Don't 999 and JD use similar API? The login content for the .cs files are very different between the cs files but I have no idea what to do with those files. I was able to open them in MS Visual Studio Express and that's about the extent of my programming talent.
Not sure if this helps but this is from the jdcapilog.txt file:
5/30/2015 7:41:38 AM 1::
5/30/2015 7:41:48 AM caught!The operation has timed out
5/30/2015 7:41:58 AM caught!The operation has timed out
5/30/2015 7:42:08 AM caught!The operation has timed out
5/30/2015 7:42:18 AM caught!The operation has timed out
5/30/2015 7:42:28 AM caught!The operation has timed out
5/30/2015 7:43:07 AM 1::
5/30/2015 7:43:17 AM caught!The operation has timed out
5/30/2015 7:43:27 AM caught!The operation has timed out
5/30/2015 7:43:37 AM caught!The operation has timed out
5/30/2015 7:43:47 AM caught!The operation has timed out
5/30/2015 7:43:57 AM caught!The operation has timed out
5/30/2015 7:45:36 AM 1::
5/30/2015 7:45:46 AM caught!The operation has timed out
5/30/2015 7:45:56 AM caught!The operation has timed out
5/30/2015 7:46:06 AM caught!The operation has timed out
5/30/2015 7:46:16 AM caught!The operation has timed out
5/30/2015 7:46:26 AM caught!The operation has timed out
5/30/2015 7:47:34 AM 1::
5/30/2015 7:47:44 AM caught!The operation has timed out
5/30/2015 7:47:54 AM caught!The operation has timed out
5/30/2015 7:48:04 AM caught!The operation has timed out
5/30/2015 7:48:14 AM caught!The operation has timed out
5/30/2015 7:48:24 AM caught!The operation has timed out
5/30/2015 8:28:47 AM 1::
5/30/2015 8:28:57 AM caught!The operation has timed out
5/30/2015 8:29:07 AM caught!The operation has timed out
5/30/2015 8:29:17 AM caught!The operation has timed out
5/30/2015 8:29:27 AM caught!The operation has timed out
5/30/2015 8:29:37 AM caught!The operation has timed out