-
Notifications
You must be signed in to change notification settings - Fork 53
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
Setup Failure #695
Comments
Sorry about that, I changed the instructions to refer to python setup.py install. It sounds like setup tools hasn't been installed. Can you try reinstalling it and seeing if that fixes the problem? I'll try installing bitHopper on my end and see if that works better. |
I installed bitHopper on a clean vm and it worked for me with the updated instructions. I think you just forgot to install setuptools. |
I have tried installing all of them about 6 times each and it will still show it missing. I have also restarted multiple times and it will not register as installed. Is this an issue with the fact that i have Win 7 Ultimate x64? |
It shouldn't be. What happens when you just run python.exe and then import setuptools? |
I was able to get the file from here: http://packages.python.org/an_example_pypi_project/setuptools.html
|
Acually after i found that was of installing via IDLE i decided to open your "setup.py" file and "Run Module." I was able to get this result: Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win32
Traceback (most recent call last): error: no commands supplied |
FIXED IT! After messing around more with it i was able to get it working. This is what my CMD got me: Microsoft Windows [Version 6.1.7600] C:\Users\Journeyx>cd C:\c C:\c>C:\Python27\python.exe setup.py install creating build Adding dummy-bithopper-install 0.0.9 to easy-install.pth file Installed c:\python27\lib\site-packages\dummy_bithopper_install-0.0.9-py2.7.egg Installed c:\python27\lib\site-packages\flask-0.9-py2.7.egg Installed c:\python27\lib\site-packages\btcnet_info-0.1.2.27-py2.7.egg Installed c:\python27\lib\site-packages\mechanize-0.2.5-py2.7.egg Installed c:\python27\lib\site-packages\requests-0.14.2-py2.7.egg Installed c:\python27\lib\site-packages\jinja2-2.6-py2.7.egg Installed c:\python27\lib\site-packages\werkzeug-0.8.3-py2.7.egg Installed c:\python27\lib\site-packages\httplib2-0.7.6-py2.7.egg Using c:\python27\lib\site-packages Using c:\python27\lib\site-packages\setuptools-0.6c11-py2.7.egg Using c:\python27\lib\site-packages C:\c>C:\Python27\python.exe run.py |
Awesome. The next step is to configure some pools. Do the C:\Python27\python.exe run.py And then open up localhost:8339 in a web browser. I recomend eligius, mtred or arsbitcoin. Make sure that you have some workers on pools with fair (PPLNS, PPS) schemes since bitHopper currently won't give out work where it's not profitable to mine. |
I go that part setup and i moved on to configure my miner. I set it up to point to that url you said and BitHopper is showing me trying to connect but the miner keeps saying that it cannot connect. I am using Phoenix miner with the following config file: [general] [cl:0:0] Am i missing something?? |
What workers have you added to bitHopper? Also what version of Phoenix are you using? |
I have added coinotron, eclipsemc, slush, mtred, and deepbit. I set my miner, Pheonix 2.0.0, to login with http://user:x@localhost:8337 It logs in and works until the hopper goes to switch pools then it cannot connect. |
Hmmm. This may be a bug with stratum support dieing in a fire. |
And this will be fixed how? |
I'll download pheonix 2.0.0 and see exactly what its doing. I recomend switching to poclbm cgminer or bfgminer for the time being until I can figure out what its doing. |
I followed your setup instructions for Windows to the letter but i am unable to get it to run. I cannot find the install.py file that you refer to and when i run "python setup.py install" in CMD (with and without admin) it will always return with - No module named 'setuptools' (This has been installed correctly!)
The text was updated successfully, but these errors were encountered: