I uploaded a new dbg release
May be a conflict between winsock.h and winsock2.h
Topic: Pollard's kangaroo ECDLP solver - page 128. (Read 59389 times)
Exactly. And as I mentioned - on Linux I have four clients on the test and for several hours without problems.
So this is not a crash but an unexpected exit ?!?
I'm investigating....
Exactly. And as I mentioned - on Linux I have four clients on the test and for several hours without problems.
So this is not a crash but an unexpected exit ?!?
I'm investigating....
Someone to add opencl support ?
So same behavior with the dbg exe and exit without a popup ?
Exactly. And as I mentioned - on Linux I have four clients on the test and for several hours without problems.
So same behavior with the dbg exe and exit without a popup ?
I did a test on linux and the problem doesn't occur there.
The effect of working on Windows with the new dbg from a moment ago:
The effect of working on Windows with the new dbg from a moment ago:
I uploaded a new dbg exe
OKAY... I kill only one to test
Do not kill clients
Ok thanks
no it is not compiled for more than 50 clients
i redo it
no it is not compiled for more than 50 clients
i redo it
OKAY. I have something...
I have disabled the client from this previous IP ... it's the same message about another machine
Second try:
I have disabled the client from this previous IP ... it's the same message about another machine
Second try:
Do you have it compiled for over 50 clients? After running for 5 minutes, nothing happens, then flies for 10 seconds and ends on the command line to close "Press any key to continue ...."
OK ... however it works ... End .bat "pause" caused what I described above: - / IP of one of the machines appeared earlier with information that it sends incorrect data.
OK ... however it works ... End .bat "pause" caused what I described above: - / IP of one of the machines appeared earlier with information that it sends incorrect data.
Yes, I have it installed.
I solved the problem by installing Windows Debug Tools with SDK from this page: https://developer.microsoft.com/pl-pl/windows/downloads/windows-10-sdk/
I will add effects in a moment...
I solved the problem by installing Windows Debug Tools with SDK from this page: https://developer.microsoft.com/pl-pl/windows/downloads/windows-10-sdk/
I will add effects in a moment...
did you get the file from here ?
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
vc_redist.x64.exe
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
vc_redist.x64.exe
I added a debug release, hope it can bring some infos:
https://github.com/JeanLucPons/Kangaroo/releases/tag/1.5
Thanks to try as server...
https://github.com/JeanLucPons/Kangaroo/releases/tag/1.5
Thanks to try as server...
Did not work.
At startup, errors appear missing files
ucrtbased.dll
msvcp140d.dll
vcruntime140_1.dll
VCRUNTIME140D.dll
I downloaded these files and an error pops up
Code:
Procedure entry point _realloc_dbg not found in library MSVCP140D.dll
Code:
Procedure entry point _callog1_dbg not found in library server.exe
I added a debug release, hope it can bring some infos:
https://github.com/JeanLucPons/Kangaroo/releases/tag/1.5
Thanks to try as server...
https://github.com/JeanLucPons/Kangaroo/releases/tag/1.5
Thanks to try as server...
-snip-
You're right ... Many thanks for a great job! I will definitely start your version by # 115 ... if I finish # 110 :-)
I saw in the code that it supports your info server on Telegram ... Where exactly do I set the channel parameters?
to get telegramm notification you need have your telegramm bot.You're right ... Many thanks for a great job! I will definitely start your version by # 115 ... if I finish # 110 :-)
I saw in the code that it supports your info server on Telegram ... Where exactly do I set the channel parameters?
if you have telegramm bot you can set params -tgbotid YOURTELEGRAMMBOTID and -tgmyid YOURTELEGRAMMID
in that case if server will see this 2 params, he will launch telegramm hook thread. and send you hello message like "Key server started at port:...."
to your telegramm account. When the key will solve server send via your telegramm bot message "Key found!!!"
The telegram will not send the key itself, for security reasons, but only a message that it is found.
-snip-
Thank you very much! I appreciate the help!
Should I understand that this requires new clients to be started?
At this time, it probably won't be the best idea to start a new customer run from the beginning :-)
In your case maybe it is not good idea to use this server because you almost done this job.Thank you very much! I appreciate the help!
Should I understand that this requires new clients to be started?
At this time, it probably won't be the best idea to start a new customer run from the beginning :-)
But if you want, all what you need it is copy your masterfile to serverapp folder, setup in server bat file SET workfile=....
And run clientapp on rig. All new client files will be merged to your masterfile.
But I repeat that in your case, perhaps the best solution would be to stay on the built version.
You're right ... Many thanks for a great job! I will definitely start your version by # 115 ... if I finish # 110 :-)
I saw in the code that it supports your info server on Telegram ... Where exactly do I set the channel parameters?
-snip-
Thank you very much! I appreciate the help!
Should I understand that this requires new clients to be started?
At this time, it probably won't be the best idea to start a new customer run from the beginning :-)
In your case maybe it is not good idea to use this server because you almost done this job.Thank you very much! I appreciate the help!
Should I understand that this requires new clients to be started?
At this time, it probably won't be the best idea to start a new customer run from the beginning :-)
But if you want, all what you need it is copy your masterfile to serverapp folder, setup in server bat file SET workfile=....
And run clientapp on rig. All new client files will be merged to your masterfile.
But I repeat that in your case, perhaps the best solution would be to stay on the built version.
Jump to: