CoinLab

Members
  • Content Count

    163
  • Joined

  • Last visited

Everything posted by CoinLab

  1. Our servers are currently down due to technical issues. We are working our hardest to get them back online. The issue started at 11PM PST last night. Our servers went down at 3:20 pm PST today and from then until they come back up you will recieve error messages on the client. Your card will not be burning electricity until they are on again. You will be credited for all work done.
  2. You're right, I was in a hurry. Thanks for catching that for me. Original post updated.
  3. 1) No, we are not sending out any work besides bitcoin mining. Due to some setbacks, we will not be able to offer any other work besides other than bitcoin mining. 2) We don't have any plans to integrate that into the client, but if you look up what GPUs you have in this table https://en.bitcoin.it/wiki/Mining_hardware_comparison, and compare the sum of their power to what you see on your stats page: http://pool.coinlab.com/partners/wurm/stats, you can get an idea of what numbers you should be seeing. Note that the numbers posted on that site can be faster than what you will see with our miner due to overclocking and/or mining kernel optimized for their card. 3) Sorry, but we don't have plans to make use of integrated GPUs in our client. You should just use cgminer. That's right. Nvidia cards aren't good at bitcoin mining due to the way they are built. Mobile cards aren't good at bitcoin mining because they are low power and not very efficient. We're sorry we can't help you. You should just buy your silver through Wurm.
  4. So, you have both tried both clients and a clean boot? If so, I don't think there is anything I can do to help you get our client working. If you want to, you can use a regular bitcoin mining client, like cgminer, and point it at our pool using the credentials: pool: http://pool.coinlab.com:8332 user: wurm_yourusernamehere password: x
  5. To everyone having issues, try using the old client: https://s3-us-west-2.../wurm-1.0.7.msi If that doesn't work, there might be some service using the same port as our client, try doing a clean boot. Sorry about the links. We signed up for ddos protection and it screwed up our download links. The links on the original post and the email are fixed.
  6. The link to the new client was never broken. Here it is: http://media.coinlab.com.s3.amazonaws.com/clients/wurm-latest.exe The old link was broken, the post has been updated and here is the link. Only use this one if the other does not work for some reason. />https://s3-us-west-2.amazonaws.com/media.coinlab.com/clients/32/wurm-1.0.7.msi
  7. Your rate may vary, but it should be somewhere around 100 iron per hour or 24 copper per day.
  8. Yes, dedicated bitcoin mining hardware will eventually push out GPU's, but we still have a good amount of time. The price has more than doubled in the past 2 months with only a very small increase in difficulty. Also, Butterfly Labs has had that page up for almost a year. They have been "One Month Away From Shipping!" for the past 5 months. You will be able to see any price fluctuations in your iron per hour counter on the miner.
  9. It is only designed to work on Windows XP and above. If it does work, great, but we didn't plan to support it.
  10. Good idea! I had forgotten about that. This one is easy to set up I believe. http://bitclockers.com/forums/index.php?topic=8.0 . I don't have any experience with it, but it seems simple enough. If you are a programmer and have some command line experience I would recommend cgminer. You will want to log in to our pool with the following credentials: pool: http://coinlab.com:5001 user: wurm_exelsiar password: x
  11. If it said lost connection, then I am sorry, but there is nothing I can do. Either some hardware or software is blocking the connection, or it is just intermittent. I don't know why your coinlabwindow.exe would have been deleted. Nothing in our code does such a thing.
  12. We have 3 services. Coinlabcompute.exe is a local server which manages everything. Coinlabwindow.exe is a dumb window which simply displays what compute is doing. Coinlabengine.exe is where the actual bitcoin mining happens. Compute gets the work from Coinlab's servers, parses it and sends it to the engine. Whenever the engine finds something it sends it to Compute to report back. The engine and compute communicate on 1338, and unfortunately changing which port that happens on would require recompiling the engine.
  13. About the port changing issue, it looks like changing the port from 9999 to something else will probably not do anything. The port conflict is between the local server and the compute engine. The only way to remedy this issue is making sure that no other local service is using port 1338. An easy way to do this is to perform a clean boot. http://support.microsoft.com/kb/929135
  14. The change I made is completely unrelated to anything that would cause that error. But, if the issue does not resolve itself within a reasonable amount of time, you can revert to an old version and disable the auto-update. If the program is running, close the window, and either wait 30 seconds, or open the task manager and kill coinlabcompute.exe and coinlabengine.exe. Install an old version of the client http://media.coinlab.com/clients/wurm-02.00.13.exe Now, change your client.conf file located at C:/Users/[yourusernamehere]/AppData/Local/Coinlab/wurm-compute/client.conf. Note that AppData is a hidden folder. Add a line at the end of that file like this: update_check_interval = 9999999999
  15. New version released! Your client should auto-update within the hour, or if you're getting antsy, you can download it here. Minor engine tweak, some of you may see higher speeds. Exelsiar and Davatar: Whenever a new version comes out, the client.conf file is cleared in the installation, so you will have to add the host_port = 9998 line after the update.
  16. From you stats page it looks like you've earned 80 iron. What kind of graphics card do you have? You log file shows that you have an intermittent connection, but if you've earned shares then you are eventually getting through. How is the quality of your internet connection? Do you get dropped from online games sometimes? Do you connect to the internet through a medium, eg firewall (hardware or software), proxy, vpn? Do you have any other software services running on port 9999? You should try the steps below to run it on a different port, like 9998. That's a good point. These steps might actually be useful to you exelsiar and anyone else who is still having issues connecting to the pool. There is a way to get it on a different port, but it isn't all that pretty. Open your client.conf file in notepad, found at C:/Users/[yourusernamehere]/AppData/Local/Coinlab/wurm-compute/client.conf. Note that AppData is a hidden folder. Add an extra line to the end of the file like so: host_port = 9998 Replace 9998 with whatever you want. Unfortunately the window is hardcoded for 9999, so you will have to navigate to localhost:9998 using Chrome, Firefox, or IE.
  17. Interesting. I did see that graph, but I assumed it wasn't running on turbo. We have a 7970 which runs our client at around 520 MH/s and cgminer at 550 MH/s, so although there may be a slight difference in kernel efficiency from one card to another it will not be a factor of two. It looks like it's only one card even though our client can utilize an arbitrary number of cards granted they are all talking to the OS. Are you running GUI Client on Windows as well? Are your cards crossfired? Those drops to zero in the graph are caused by your machine not finding a share in a generation. It happens when you get a combination of a really fast generation and bad luck.
  18. Our mining engine was developed by Con Colivas developer of cgminer. The reason you may be seeing a speed difference is due to our engine being a bit nicer to the user. A standard bitcoin client is very aggressive, sucking up all available power, which greatly reduces your computer's performance while you are using it. Ours tries to only use spare computing power, so it backs off when the user wants to use the GPU for something else. I can understand a few percent, but I'd be very surprised if your speed doubled. When you were running our client, did you set the speed setting to turbo and leave it idle? A good way to do a side by side comparison would be to run start our client, leave the computer idle for an hour. Then turn off ours, and run your other mining client for an hour. Then check out the graph on your stats page at http://pool.coinlab....s/wurm/stats. Also, where were your getting your MH/s number from? The big number at the top of your stats page is calculated through a 30 minute exponential decay algorithm, so if you haven't run the client in a while, it will take 30 minutes before it is accurate. Also, it is calculated through your share rate because the client does not send speed data to the server. As a result, there is a fair amount of variance depending on your hash rate.
  19. You will see similar returns with our pool. We adjust the share price based on the last Mt Gox 24 hr weighted average price.
  20. Nvidia GPUs run much slower than ATIs. More info here: https://en.bitcoin.it/wiki/Why_a_GPU_mines_faster_than_a_CPU#Why_are_AMD_GPUs_faster_than_Nvidia_GPUs.3F
  21. Update your Internet Explorer. We use a headless IE window to render the graphics so having an outdated version will cause some visual problems. So, when you start the client you get no errors? When running the client, open up the task manager. Do you see coinlabwindow.exe, coinlabcompute.exe, coinlabengine.exe processes? Or do you only see the window and compute?
  22. Also, did you create an account through the sign up page at http://pool.coinlab.com/partners/wurm ? If so, what username did you use?
  23. What graphics card do you have? When you start the program, do you get any errors, such as cannot find OpenCL.dll? After starting the program, open the task manager. Do you see coinlabwindow.exe, coinlabcompute.exe, coinlabengine.exe processes? Or do you only see the window and compute?
  24. I'm sorry, but I do not think you will be able to mine with that card. The issue is that Nvidia never built OpenCL drivers for your card due to its age. If Nvidia doesn't give you OpenCL drivers, then there is nothing I can do. Sorry I didn't figure this out sooner.
  25. Which client are you using? Does it look like the screenshot on this page: http://pool.coinlab.com/partners/wurm When you start the client do you get any errors? Example: "Cannot find OpenCL.dll" What kind of graphics card do you have? Have you updated your graphics card drivers?