Your system is old and need some fresh drivers. Why do you want to run 3 TF parallel on one card?

That's unusual behavior, to regularly d/l the master file table.

Is this intended?

no, is this the same host as the other?

<core_client_version>7.24.1</core_client_version>
<![CDATA[
<message>
The operating system cannot run %1.
(0xc3) - exit code 195 (0xc3)</message>
<stderr_txt>
2024-02-14 05:35:07 (288748): wrapper (7.24.26018): starting
2024-02-14 05:35:07 (288748): wrapper: running mfakto.exe (-d 0)
2024-02-14 05:35:07 (288748): wrapper: created child process 287960
2024-02-14 05:35:13 (288748): mfakto.exe exited; CPU time 0.000000
2024-02-14 05:35:13 (288748): app exit status: 0xc0000135
2024-02-14 05:35:13 (288748): called boinc_finish(195)

</stderr_txt>
]]>

New work is up, beta test is disabled, you can found it no longer in your prefs.

Hello, this is the content of a job file:
../../projects/srbase.my-firewall.org_sr5/job_TF_l64c_00020.xml

<job_desc>
<task>
<application>./mfaktc.exe</application>
<append_cmdline_args/>
</task>
<unzip_input>
<zipfilename>mfaktc-linux64-v6.zip</zipfilename>
</unzip_input>
</job_desc>

if you want a device number you have to add a -d <number> parameter (default is 0)

Usage: ./mfaktc.exe [options]
-h display this help and exit
-d <device number> specify the device number used by this program
-tf <exp> <min> <max> trial factor M<exp> from 2^<min> to 2^<max> and exit
instead of parsing the worktodo file
-st run builtin selftest and exit
-st2 same as -st but extended range for k_min/m_max
-v <number> set verbosity (min = 0, default = 1, more = 2, max/debug = 3)

Hello, this is the content of a job file:
../../projects/srbase.my-firewall.org_sr5/job_TF_l64c_00020.xml

The main question above was:
Do TF's end early when they find a factor so we will see runtimes ending as low as a few seconds to maybe half the normal run time?

I have removed my last post and checked a found factor result, you are right, the test ended earlier if a factor is found. Thats a bonus too in credits.

There is nearly no CPU time to run TF on GPU.

I can speak for all of us when I say, "we want to run the same amount of TF projects that we have of GPUs". Exp: 2 GPUs, we should run 2 TF projects, One for each GPU. Or one TF project on ANY GPU and run whatever project BOINC wants to run on the other GPU". Oh, wait BOINC does that on every project out there like, Prime Grid, GPU Grid, Amicable Numbers, Einstein, ext. Even all of SRBase. Well, for some reason NOT for TF projects.

I think if you changed the word "project" to the word "tasks", no quotes, it would be easier to get what you are trying to say.

What I think you are trying to say is that you want EVERY gpu in the pc to run at least one TF task on it here at SRBase, just like it does at every other Boinc Project ie MilkyWay, Einstein etc when you use the <use-all-gpus> line in the cc_config file.

Q Does mfaktc support multiple GPUs?
A Yes, with the exception that a single instance of mfaktc can only use one
GPU. For each GPU you want to run mfaktc on you need (at least) one
instance of mfaktc. For each instance of mfaktc you can use the
commandline option "-d <GPU number>" to specify which GPU to use for each
specific mfaktc instance.

I just thought it found factor and decided not to factor further and report at once.

2) Are the WUs TF CPU times only showing the amount of time after a BOINC Time Of Day suspension? (As in 3600sec of an actual 34 hour run)
3) Should my NVidia 1060 run only 1 WU at a time instead of 4 if the suspensions are an issue?

(snip)
2. CPU time is overall
3. yes

It's at 8 hours and still crunching on the UHD. Most will be aborted for deadline.

I have given up on the Intel ARC 770 and replaced it with a Gigabyte GTX1660 Super 6GB card.

I have changed the plan_class to not send out work for Intel HD Graphics, its too slow, BOINC doesnt have Intel ARC support.

7.16.20+, you can also update the cert file from FAQ