Latest posts of: heli0s

Show Posts
Pages: [1]

Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows/osx

on: July 21, 2011, 11:41:16 AM

Quote from: ckolivas on July 21, 2011, 01:45:22 AM

Quote from: error on July 21, 2011, 01:42:31 AM

The 1.3.1 release solved my issue with blank lines between the log entries. Thanks!

You're welcome! The issue was that windows opens a standard dos shell in 80 columns and the default text was slightly wider than 80 so I made it more concise.

Unfortunately it didn't fix it for me.

Code:

[2011-07-21 07:38:46] Accepted 3e2ec113 GPU 0 thread 0 pool 0

[2011-07-21 07:39:00] New block detected on network before longpoll, waiting on
fresh work
[2011-07-21 07:39:10] Accepted 70ab214e GPU 0 thread 0 pool 0

[2011-07-21 07:39:16] Accepted 3ab13683 GPU 0 thread 1 pool 0

[2011-07-21 07:39:19] Accepted 4e2712a7 GPU 0 thread 0 pool 0

[2011-07-21 07:39:20] Accepted 57e1f7b3 GPU 0 thread 0 pool 0

[2011-07-21 07:39:23] Accepted 45e05dd0 GPU 0 thread 1 pool 0

Other / Beginners & Help / Re: Newbie restrictions

on: July 21, 2011, 11:07:11 AM

Another dummy post to get me up to 5.

Other / Beginners & Help / Re: Whitelist Requests (Want out of here?)

on: June 17, 2011, 03:40:20 PM

I'd like to be whitelisted to be able to post in the miners' board. See here for the contents of what I have an immediate need to post.

Other / Beginners & Help / Re: Newbie restrictions

on: June 17, 2011, 03:32:09 PM

The one thing that I can say as a positive to the restrictions is that they're at least clearly-defined. Though I think two hours would be more reasonable as a waiting requirement. One hour would be best, though.

Other / Beginners & Help / Re: If your Mt. Gox account has been compromised, PLEASE READ.

on: June 17, 2011, 03:25:06 PM

* How much funds did you lose? Approx $2000 and 100 BTC * To what address were your stolen funds sent? Can't log in to check; email address was changed as well. * What OS are you using (Windows, Linux, Mac OSX ...)? Windows 7 x64 * How long was your old password? I never divulge specifics regarding passwords, but it was at least 8 characters long. * Was your old password random? No. It used multiple dictionary words. * Was your username the same on Mt. Gox as on the forum? No, but I've since discovered that someone on Mt. Gox has the same username as I do. * Did you use your Mt. Gox password somewhere else? No. However, I did discover a similar password on a published list (but it wasn't any of my accounts on the list), so my guess is that whoever is doing this is using the published lists and performing some additional checks on variations on them. * Did your old password contain lowercase letters, uppercase letters, special characters and numbers? Yes; it contained all of them. * Have you used any Bitcoin-related software, and if yes, what software? Think about things like miners, wallet managers, etc. Only the Bitcoin client and Phoenix mining software. Nothing used the same password as what Mt. Gox used. * Please also include a screenshot if possible so we know it's a real report. Since I can't access the account, it isn't feasible to include a screenshot. I've submitted a support ticket but I haven't had any response to it yet.

Other / Beginners & Help / Re: Newbie restrictions

on: June 17, 2011, 03:10:14 PM

The login and posting requirements are annoying for someone like me who only registered to get technical help with a mining client. So, in hopes of getting a solution faster, here's my problem: I run Phoenix v1.50. I have an AMD Radeon HD 4850 and a GeForce GT330 in my system. Yes, I know these are not powerful mining cards, but every little bit of hashing potential helps. I execute two mining scripts; one for the GT330 (OpenCL Platform #0) and one for the 4850 (OpenCL Platform #1). Both call Phoenix in the same way: Code: [do some minor setup tasks] phoenix.exe -v -u http://[login]:[password]@[poolHostname]:[poolPort] -k poclbm PLATFORM=0 DEVICE=0 FASTLOOP BFI_INT WORKSIZE=64 AGGRESSION=1 (on the 4850 script, it uses PLATFORM=1 but everything else is the same) My GT330 will happily start up, connect to the pool, and chug away at it's speedy 19MH/s. The 4850, however, returns the following content: Code: C:\phoenix-1.50>phoenix.exe -v -u http://[login]:[password]@[poolHostname]:[poolPort] -k poclbm PLATFORM=1 DEVICE=0 FASTLOOP BFI_INT WORKSIZE=64 AGGRESSION=1 [17/06/2011 10:57:38] Phoenix 1.50 starting... [17/06/2011 10:57:39] Connected to server [17/06/2011 10:57:39] Server gave new work; passing to WorkQueue [17/06/2011 10:57:39] New block (WorkQueue) [0 Khash/sec] [0 Accepted] [0 Rejected] [RPC] This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. I look at the application event log and see the following: Code: Faulting application name: phoenix.exe, version: 0.0.0.0, time stamp: 0x4918019b Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9 Exception code: 0x40000015 Fault offset: 0x0005beae Faulting process id: 0xe14 Faulting application start time: 0x01cc2cfee63374a8 Faulting application path: C:\phoenix-1.50\phoenix.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll Report Id: 24e65b98-98f2-11e0-91f4-782bcb9a70f2 I know that the 4850 is a working card; before I recently replaced it in another machine with a 6950, it was chugging along at about 66MH/s using the same script. I've verified that OpenCL is working with GPU Caps Viewer 1.12.0 - it sees 2 platforms, with CL devices, and successfully runs OpenCL demos on both platforms. Just for kicks, I've already tried reinstalling the OpenCL drivers from AMD. I'm not sure where to go from here. Could anyone point me in the right direction for allowing me to use both cards as mining clients? Oh, and before anyone pipes up with the brilliant suggestion of simply removing the lower-performing card, I have to have it to be able to drive the 4 monitors on my desktop. Thanks!

Pages: [1]