Show Posts
|
Pages: [1] 2 3 4 »
|
As anecdotal evidence goes...
Just couple months ago I found myself experimenting with old floppies from 20 to 30 years ago. A bunch of 880KB Amiga single density ones, and both 1.44MB PC high density and 720KB turned 1.44MB via hole punching. Some of well known brands, some with no branding at all. I had no problems reading a complete image out of each floppy I tried, with an Hitachi USB floppy drive from 10 years ago. I was kinda suprised.
Again, I don't recommend actually using floppy nowadays to store things (it's also most impractical), but they worked far better than I expected.
Old, cheap burned CD-Rs, on the other hands... a real bloodbath!
|
|
|
Had the time to play with the new version with HD wallets just now. I have to say that, as usual, the backup part is very well made and thought out: clear and simple. Congratulations!
|
|
|
A minor suggestion: when entering the PIN number, it would be nice if the virtual keys were randomly scrambled (and maybe that could be a configurable setting). Thx.
|
|
|
How about adding a bit of space for a photo on the rig page, with an external link to a bigger one?
Could be a way to give an idea about the equipment used, make an impression, etc.
|
|
|
how is that possible, lower power consumption? I am assuming you are running your cards at full speed.
Yes, speed of the card is the same: moderate overclock, and undervolted. X11 is a different algorithm, so a different workload that's less stressful for the card.
|
|
|
I built the rig at the end of January, mining Scrypt on multipools autocoverting to bitcoins, mostly for experimenting. Then changed to X11 in the last period, as profits for Scrypt were going lower and lower. Checking for example Wafflepool, the BTC/MHs/day of X11 are now about 1/3 of Scrypt, but in X11 I get 4x the hash rate and halve the power consumption, so it's definitely more convenient now, at least for me.
|
|
|
Nothing fancy: 2x 7950 mining X11. Fans at about 50%/2000rpm, cool running around 50c.
|
|
|
Usually things goes pretty smooth for me, but this just happened. Someone rent for 3 hours. Renting start, but the miner don't switch on Betarigs, meaning that the pool chosen by the renter isn't working. Live stats by CGMinerMonitor show all is good on my part. I send a message after 5 minutes, explaining, recommending checking config and trying another pool, and offering assistance. Then again after 20 minutes, and after 1 hour. No answer. Now I just imagine what will happens when the renter will be back / notice / see the messages...
Added: All good; renter later replied and paid regularly.
|
|
|
I read a: Looks like guerillacoin forked, working on it now. on the website.
|
|
|
Same here, although I have only mined X11 for brief periods of time (12h at most). Wasn't very much convinced of the results, and your posts seems to confirm my impressions...
|
|
|
Anyone has detected new issues?.
My X13 rig, actually not rented but mining fine at my backup pool, seems to be offline in "my own rigs page" (Getting "Your rig is right now not connected" message) when it is not. Of course it is not also listed in rental page.
Nope. No issues for me.
|
|
|
Cool! Thanks!
|
|
|
For the rigs owners:
Uhm... I may be wrong but, wasn't the server URL, userid & password to be used shown in the rig page? It's not showing now! Am I looking in the wrong place?
Oh! Now the config data reappeared, and the miner is finally free! The website seems also much faster.
|
|
|
For the rigs owners:
Uhm... I may be wrong but, wasn't the server URL, userid & password to be used shown in the rig page? It's not showing now! Am I looking in the wrong place? Or could this be linked to the issues (like a db not responding)?
|
|
|
Since it's a generalized problem, we can hope they are working at full steam on it: no rents = no fees.
|
|
|
It's OK again! Ahem... Not really. Now the 3 hours passed, by about half an hour; miner turned to my backup pool as usual, but the graph keep going, and the status is still "Rented - Ends in a few moments"... I'm sure it's just a display/temporary issue. But I'm curious: it's happening just on my rig?
|
|
|
|