AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool

[lvlrdka22]

For those people that 1.4 refuses to work, try this: http://www.mediafire.com/?qgz988s9ojx7j4n
I copy-pasted the entire phoenix-launching function from 1.4 over. See if this works.

This works for me as 1.4 wouldn't actually run phoenix.exe

Yay! Now try this (pasted the kill function into the wrong window on the last link , updated now): http://www.mediafire.com/?c2jfam1cubkg1b3
I replaced the kill function with 1.4's.
Let me know if hitting stop successfully kills phoenix.exe or not (or if it blue screens).

[FRanz33]

used 1.32 version overnight and all day. no hang issues..will try 1.4 when the dust settles a lil

[lvlrdka22]

used 1.32 version overnight and all day. no hang issues..will try 1.4 when the dust settles a lil

Glad to hear it ... finally!

[lvlrdka22]

Well, fixed a stupid issue in 1.41. Phoenix should launch correctly now.

[FRanz33]

will try soon..I think for the next version osd control should be a concern. Having a set place that they go each time so they dont pile up in the corner and an option to hide them. what do u think?

[dishwara]

PR 1.41 from this link http://www.mediafire.com/?5h3y5b6jq1azp13

I have in this order
cl1 device 0, gpu 0 in afterburner gpu2
cl2 device 1, gpu 3 in afterburner gpu3
cl3 device 2, gpu 6 in afterburner gpu1

The temp function works correctly, pausing & restarting.

But all the thing happened only after i removed "READ ONLY".
So, its better to avoid read only now.

[Peao]

Strange ... Has anyone noticed a drop of approximately 10% in hashrate these latest versions?
Tested 1.41 in two rigs and got the same problem...
When I use the 1.3, the hashrate is normal.

[lvlrdka22]

PR 1.41 from this link http://www.mediafire.com/?5h3y5b6jq1azp13

I have in this order
cl1 device 0, gpu 0 in afterburner gpu2
cl2 device 1, gpu 3 in afterburner gpu3
cl3 device 2, gpu 6 in afterburner gpu1

The temp function works correctly, pausing & restarting.

But all the thing happened only after i removed "READ ONLY".
So, its better to avoid read only now.

Hacky temperature monitoring works for someone other than myself , amazing!

Strange ... Has anyone noticed a drop of approximately 10% in hashrate these latest versions?
Tested 1.41 in two rigs and got the same problem...
When I use the 1.3, the hashrate is normal.

Yeah, did you add VECTORS to Extra Flags yet? It was already added in 1.3 when launching phoenix, but I removed it in later versions so people can have control over VECTORS or not.

[dishwara]

I am now running 1.41 & let it run until i woke up. Time here is 2:40 am & i may sleep at 3 or 4 or 5 or....don't ask.
For the past 20-30 minutes running with out a single crash.
I am not using temp function right now, cause i run fan at 75% & my temp stays below 74C even in daytime with 36C-40C, my city temperature.

Again, i repeat one thing, all working ONLY after i disabled Read only.


You can buy some of my shares to help me rise.

[Peao]

Yeah, did you add VECTORS to Extra Flags yet? It was already added in 1.3 when launching phoenix, but I removed it in later versions so people can have control over VECTORS or not.

Ooops! 

[dishwara]

I am getting same speed 430+ Mhash/s for each 5870 card. No speed change.

Running 1.41 for past 4-5 hours. 3 clients running. & 2 shows 1700+ shares accepted.
When i woke up, i saw a Windows white error window saying, phoenix.exe gave problem something & asked to close it.
I clicked close then OSD showed up with 2 clients 1700+ accepted & another one 800+ accepted.
Seems one client crashed, but it restarted itself in background & was running. But in front widows showing crash error.
Once i closed the crash error window, it showed OSD.
So, seems working good.

[kwaaak]

Good stuff, thank you.

[mosimo]

Nice program, the only gripe I have atm is the OSD overlapping. I know I can click the "click through" button to make them movable, but when I do this the OSD goes to a solid colour, lets me move it and no matter how many times I press the click through button again it never actually gets any text or transparency back.

I've not looked into that at all, I'm at work and a bit busy atm. But I did edit the client so it offsets the clients down the side of the screen and adds a 5px gap between them.

Changed line 715 from:

Code:

$osd[$i]=guicreate("OSD #" & $i+1,200,64,0,0,-1,bitor($ws_ex_topmost,$ws_ex_layered,$ws_ex_toolwindow),$hidden)

To:

Code:

$osd[$i]=guicreate("OSD #" & $i+1,200,64,0, + $i * 90,-1,bitor($ws_ex_topmost,$ws_ex_layered,$ws_ex_toolwindow),$hidden)

Source + binary here:
http://www.megaupload.com/?d=AXN0MYRP
http://www.mediafire.com/?qfau02x6fc8qa2c

[Internet151]

Moving the GUI box seems to be unusually difficult if using the Windows 7 Basic Theme. There's only a tiny point on the box that actually allows you to drag it and the rest clicks through.

[mosimo]

Connecting over logmein to a slow connection it's difficult at times to click and drag. With that changed I don't need to do anything, turn the pc on, PR launches and puts the OSD in the correct places.

[Kluge]

Moving the GUI box seems to be unusually difficult if using the Windows 7 Basic Theme. There's only a tiny point on the box that actually allows you to drag it and the rest clicks through.

Yeah - that's a bit of a pain in the ass. My W7 boxes change to basic when the VNC server receives a connection. OSD can be dragged if you take the time to make sure the pointer is exactly on text of the OSD.

Unrelated -- Switched to BTCGuild today

[Peao]

Someone is also seeing a decline in some of hashrate GPUs in the new versions?
In my rig 2x5970, for example, the hashrate of two GPUs are constant at 388. But the other two are ranging between 340 and 370.
Do not understand why this is happening...
If I run the phoenix from the command line, all four GPUs running steady at 388.
Any ideas? 

UPDATE:
This problem happens only in cards with two GPUs (5970 and 6990).
In version 1.3 this did not happen.
If I start mining in only one of GPUs, the hashrate is normal. When I start the second GPU, the problem starts.

[rowbot]

This is great. But without fail it crashes my entire desktop after about 10-15 minutes.

I have a 5830 running 2.4 SDK @ around 85C. I've tried both the phatk and poclbm kernels, and they both crash.

Independently running phoenix with the same args I have no problems, so I'm not sure what the issue is.

I'm running the GUI on 3 machines crossfired and am having no issues. Maybe you can update your flags?

Flags? I'm using the same settings as I was using with phoenix command-line: namely, in Rising I have 5xxx checked (which turns on BFI_INT), AGGRESSION set to 7, and I have VECTORS in the Extras.

[Internet151]

Another issue I found is the latest version (1.41) for some reason dropped the ability to set the color of the GUI text to none. Please add this back in.

[lvlrdka22]

Moving the GUI box seems to be unusually difficult if using the Windows 7 Basic Theme. There's only a tiny point on the box that actually allows you to drag it and the rest clicks through.

Yeah - that's a bit of a pain in the ass. My W7 boxes change to basic when the VNC server receives a connection. OSD can be dragged if you take the time to make sure the pointer is exactly on text of the OSD.

Unrelated -- Switched to BTCGuild today

It's one of the "features" of the Basic theme, don't think I can fix that .
What I can do is set an option to be able to save the places of the OSDs.

Another issue I found is the latest version (1.41) for some reason dropped the ability to set the color of the GUI text to none. Please add this back in.

It wasn't intended to allow anything other than those colors listed.