[QUOTE=Dubslow;284721]Whatever I was doing then, it wasn't right. I just tried this again, with opposite results: ^C is passed to mfaktc. Unfortunately, the options aren't recognized and the affinity isn't set properly (not set at all).

So that still leaves me clueless.[/QUOTE]

Well, if you want to reconsider, this will do affinity and priority. You can add switches at the end of the last line, if you want them.

[CODE][your drive letter]:
cd \[your directory]\[your subdirectory if needed]
start /low /affinity 0x20 mfaktc-win-64[/CODE]

Edit: Ctl-C will go to mfaktc.

Hehe, thanks. (Though I did have to use affinity 0x80 :rolleyes:)

[QUOTE=Dubslow;284945]Hehe, thanks. (Though I did have to use affinity 0x80 :rolleyes:)[/QUOTE]

Yeah. I didn't put in [your hex value] in line 3.

[QUOTE=kladner;284936]That would be KB, right?:rolleyes:[/QUOTE]

Of course. The fingers need to pay more attention to what the brain is thinking.

[QUOTE=bcp19;284976]Of course. The fingers need to pay more attention to what the brain is thinking.[/QUOTE]

It's been so long since such numbers were pertinent. The first computer in this household had 8MB of RAM (I insisted on upping it from the 4MB on offer), and a 120MB HDD. The second machine had 256MB of RAM, or double what the first had in the HDD. The first was a 486DX 33MHz with DOS 5 and Windows 3.1. The second was a Pentium Pro, which had a few OS upgrades in its life span.

He, found another problem. It works great when I double click the file -- but if I pin the resulting icon to the taskbar and just click on that icon, it doesn't work. Pain the butt.
Edit: Making a shortcut and pinning that doesn't work either.
Double clicking the shortcut on the desktop works though.

[QUOTE=Dubslow;285018]He, found another problem. It works great when I double click the file -- but if I pin the resulting icon to the taskbar and just click on that icon, it doesn't work. Pain the butt.
Edit: Making a shortcut and pinning that doesn't work either.
Double clicking the shortcut on the desktop works though.[/QUOTE]

Hmm. Haven't tried that. I have icons on the desktop.

EDIT: But I've been lazy about consolidating the start up of the two instances I run.

I am completely new to GPU TFing and have some stats to share with you guys.

System
2600K/GTX460 stock

During TFing on the GPU it seems like the CPU is rather busy as well, which in turns use a fair bit of power, 26.8 watt in this case. Is this normal? Is there anyway to run this more effectively? The same CPU idling uses about 5-7w of power.

The GTX seems to churn out a 70-71 bit TF in about 1 hour and a 71-72 in about 2 hours which is fairly fast (i think) compared to pure CPU TFing.

[QUOTE=xtreme2k;285078]seems like the CPU is rather busy as well, which in turns use a fair bit of power, 26.8 watt in this case. Is this normal?[/QUOTE]Perfectly normal. You're using one core's worth of CPU power to keep the GPU pretty well fed. Looks good.

[QUOTE=xtreme2k;285078]I am completely new to GPU TFing and have some stats to share with you guys.

System
2600K/GTX460 stock

During TFing on the GPU it seems like the CPU is rather busy as well, which in turns use a fair bit of power, 26.8 watt in this case. Is this normal? Is there anyway to run this more effectively? The same CPU idling uses about 5-7w of power.

The GTX seems to churn out a 70-71 bit TF in about 1 hour and a 71-72 in about 2 hours which is fairly fast (i think) compared to pure CPU TFing.[/QUOTE]

Your CPU does some sieving, so that's normal. Everything from you're picture seems good. You could try running two instances to see if you get more throughput.

Thanks guys.

Great info, I will try to run 2 instances, would that be by running 2 separate ones from 2 folders?

Would you also run prime95 on 3 CPU cores (TF or other units) at the same time?