Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xmrig.win32 produces start error on various x86 Windows 7 systems #27

Closed
nightbowl opened this issue Jul 4, 2017 · 5 comments
Closed

Comments

@nightbowl
Copy link

nightbowl commented Jul 4, 2017

Hi!
I guess, it occurs while xmrig (2.0.0) parses command line switches. Some combinations of parameters produce error, some don't.

@xmrig
Copy link
Owner

xmrig commented Jul 5, 2017

Can you provide example command line that occurs error.
If you use option --backup-url it was removed in 2.0.0. Instead now accept multiple --url options.
Thank you.

@nightbowl
Copy link
Author

nightbowl commented Jul 5, 2017

It's a kind of strange error. The similar results I've got on different hardware (Core i7, Core i5, etc). Previous version of xmrig was without such a flaw. Below I put series of screenshots.

  1. Command line can be seen on image. There's a window in Russian saying that Xmrig has been terminated due to some error.
    01

  2. It's successful start just by removing --no-color option.
    02

  3. Removing --cpu-affinity causes error again
    03

  4. Changing --algo to -a returns working state
    04

  5. Replacing -p with --pass= brings error
    05

  6. The last command line iteration is to get rid of --keepalive option. Xmrig works.
    06

xmrig added a commit that referenced this issue Jul 5, 2017
@xmrig
Copy link
Owner

xmrig commented Jul 5, 2017

xmrig-2.0.1-dev-gcc-win32.zip
Please confirm if issue solved.
Thank you.

@xmrig
Copy link
Owner

xmrig commented Jul 5, 2017

Also nicehash does not support keepalive. Specifying this option cause disconnects by timeout because nicehash not answer for keepalive pings (no error/no success).

@nightbowl
Copy link
Author

The test was successful so I confirm that your fix had solved the issue.
Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants