[QUOTE=kladner;279843]
cmd.exe /k "start /b /low /affinity 0x20 mfaktc-win-64.exe"

cmd.exe /k "start /b /low /affinity 0x10 mfaktc-win-64.exe"

cmd.exe /k "start /b /low /affinity 0x08 mfaktc-win-64.exe"
[/QUOTE]
Back to Windows for the time being: While I don't run a web server and can't play Minecraft, I can play all things Steam, such as TF2. Anyways kladner, I've discovered the problem with this is that ^C's are sent to cmd.exe, not mfaktc -- so I get a new prompt, which eventually gets overridden by an mfaktc class output. Just so I could say I tried, 'mfaktc-win-64.exe /affinity 0x80' doesn't work -- no surprises there. I'm running this from a shortcut. Edit: Just tried 'start /b /low /affinity 0x08 mfaktc-win-64.exe', but it again said 'Target not found'. Unfortunate.

[QUOTE]Edit: Just tried 'start /b /low /affinity 0x08 mfaktc-win-64.exe', but it again said 'Target not found'.[/QUOTE]

Are you sure you're in the right directory? Check the Properties of the shortcut and look at the "Start in:" line. I have not tried the shortcut approach. I would have thought that the command line in the quote above might have worked.

Yes. Ctl-C does not get through to mfaktc in the batch scenario. Ctl-Break will stop it. Probably not ideal, but I don't stop mfaktc, or let it stop that often.

[QUOTE=Radikalinsky;283462]@Kladner,
I manually submitted both lines. Maybe it is because with partial tests the primenet server does some assumptions. But as I understand, the primenet server just does not yet understand all the details of the mfaktc message, both 0.17 and 0.18.

Thanks, Rad[/QUOTE]

OK. It seems to work in some situations. The lines I quoted above were from results.txt.

This is what shows in my Results Details page on the server:

[CODE]Manual testing 52279247 F 2011-12-24 05:43 0.0 1525757169405396xxxxx 6.2631

Manual testing 52279247 NF 2011-12-24 05:43 0.0 no factor for M52279247 from 2^69 to 2^70 [mfaktc 0.18 barrett79_mul32] 2.2870
[/CODE]
When I encountered the "partial credit" situation, the two lines were submitted separately, in two different uploads. The second upload didn't produce any further results.

These are only attempts at deduction on my part. But PrimeNet does not seem to balk at all Factor Found reports from mfaktc 0.18.

[QUOTE][B]From Dubslow[/B]: I'm running this from a shortcut. Edit: Just tried 'start /b /low /affinity 0x08 mfaktc-win-64.exe', but it again said 'Target not found'. Unfortunate. [/QUOTE][CODE]c:
cd "\Program Files\mfaktc\"
cmd.exe /c "start "mfaktc 1 DCTF" /low /affinity C mfaktc-win-64.exe -v 1"
cd "\Program Files\mfaktc - 2\"
cmd.exe /c "start "mfaktc 2 LLTF" /low /affinity 30 mfaktc-win-64.exe -v 1"
cd "\Program Files\mfaktc - 3\"
cmd.exe /c "start "mfaktc 3 LLTF 74" /low /affinity C0 mfaktc-win-64.exe -v 1"
[/CODE]I have the above in TF.bat. It even works from startup. No error checking and I'm using hex for the affinity.

It gives me three windows with the title of what each is for. Maybe it will give you a starting point.

My problem is I'm trying not to use a batch file, just a shortcut. kladner, it was starting in the correct directory, I checked that when I set it up.

OK, seems I misunderstood.

I made a shortcut by right clicking on mfaktc-win-64.exe and picking sendto desktop (shortcut).

Then I right clicked on the shortcut and picked properties.

Target box had: [CODE]"C:\Program Files\mfaktc\mfaktc-win-64.exe"[/CODE]The options were the added: [CODE]"/low /affinity C mfaktc-win-64.exe -v 1"[/CODE]The Target box now has: [CODE]"C:\Program Files\mfaktc\mfaktc-win-64.exe" "/low /affinity C mfaktc-win-64.exe -v 1"[/CODE]Note that quotes pairs are needed for the program .exe. Quote pairs for the program command line options seem to be optional.

Double click on the shortcut and the programs starts.

If I'm bugging you or really misunderstand, just say so, I will stop.

I run 2 instances of mfaktc, in C:\Prime95\mfaktc\1\ and C:\Prime95\mfaktc\2\
I put this simple batch file in C:\Prime95\mfaktc\mfaktc.bat[code]cd \Prime95\mfaktc\1
start "mfaktc 1" /min /low /affinity 0x01 mfaktc-win-64.exe

cd \Prime95\mfaktc\2
start "mfaktc 2" /min /low /affinity 0x04 mfaktc-win-64.exe[/code]Any shortcut I want simply points to the batch file.

[QUOTE=Dubslow;283482]My problem is I'm trying not to use a batch file, just a shortcut. kladner, it was starting in the correct directory, I checked that when I set it up.[/QUOTE]

OK. Just asking. I'll have to mess around with shortcuts. I'm only speaking in generalities.

[QUOTE=oswald;283490]OK, seems I misunderstood.

I made a shortcut by right clicking on mfaktc-win-64.exe and picking sendto desktop (shortcut).

Then I right clicked on the shortcut and picked properties.

Target box had: [CODE]"C:\Program Files\mfaktc\mfaktc-win-64.exe"[/CODE]The options were the added: [CODE]"/low /affinity C mfaktc-win-64.exe -v 1"[/CODE]The Target box now has: [CODE]"C:\Program Files\mfaktc\mfaktc-win-64.exe" "/low /affinity C mfaktc-win-64.exe -v 1"[/CODE]Note that quotes pairs are needed for the program .exe. Quote pairs for the program command line options seem to be optional.

Double click on the shortcut and the programs starts.

If I'm bugging you or really misunderstand, just say so, I will stop.[/QUOTE]
Thanks for the suggestion. I tried it though and got the same behavior as before, i.e. ^C is sent to cmd.exe, and not to mfaktc-win-64.exe .
[QUOTE=James Heinrich;283494]I run 2 instances of mfaktc, in C:\Prime95\mfaktc\1\ and C:\Prime95\mfaktc\2\
I put this simple batch file in C:\Prime95\mfaktc\mfaktc.bat[code]cd \Prime95\mfaktc\1
start "mfaktc 1" /min /low /affinity 0x01 mfaktc-win-64.exe

cd \Prime95\mfaktc\2
start "mfaktc 2" /min /low /affinity 0x04 mfaktc-win-64.exe[/code]Any shortcut I want simply points to the batch file.[/QUOTE]
Right click on the executable and click "Create shortcut". Of course, I'm only running one instance, so you'd need one for each instance if you didn't want to use the batch file.

I set up two shortcuts. On the left, it sets the directory in Start in: and runs the same command line I use in my batch files. An example is in the text above. Unfortunately, in the captured view of the properties box, the entire line is not visible. It is, however, the same as the last line in the batch file. This works exactly the same as the batch. It sets priority and affinity, but Ctl-C goes to CMD, not mfaktc.

The shortcut on the right also sets the directory, but it simply runs mfaktc. This launches mfaktc, and Ctl-C goes to the program. However, affinity and priority are not set and so default to all cores and normal priority.

I haven't yet tried the approach suggested by James Heinrich, using "Start" by itself without a "cmd.exe" preface.

EDIT: The following command line is not accepted by the shortcut Properties dialog:
[CODE]start "mfaktc_c" /b /low /affinity 0x20 mfaktc-win-64.exe[/CODE]It says "The name 'Start' specified in the target box is not valid."

However, using "Start" by itself in a batch file runs mfaktc. Affinity and Priority are set, and Ctl-C goes to mfaktc.

I am kind of confused by this. I didn't think there was much difference between a Shortcut command line, and one in a batch file.

EDIT2: I suppose that using Start in a batch file has implicitly invoked CMD to run the batch.

Something odd is happening when I run mfakct 0.18 on my GT 555M. After a short while, the GPU usage drops from 100% to +- 70-80%, and a little later, it goes back again to 100% for a short time, before it drops again, ad infinitum. Mfakct 0.17 always runs at 100% GPU usage on this card.