I was running two tasks on my GTX750 Ti and that was fine. I installed the Quad install and ran the update quad ini file bat job. I thought that it would run two tasks as it had done on the GPU and run two on the CPU.

However what it did was try and run all four on the GPU and none on the CPU.

How do I configure the ini file to run CPU and GPU ?

This is the only server uncommented server=GFN262144:100:6:prpnet.primegrid.com:11002

// This is the name of LLR executable. On Windows, this needs to be
// the LLR console application, not the GUI application. The GUI
// application does not terminate when the PRP test is done.
// On some systems you will need to put a "./" in front of the executable
// name so that it looks in the current directory for it rather than
// in the system path.
// LLR can be downloaded from http://jpenne.free.fr/index2.html
// If running a 64-bit system, comment out the llr.exe and uncomment llr64.exe
// To use a CC 1.3+ CUDA GPU, comment out llr.exe and uncomment llrCUDA.exe
//llrexe=llr.exe
llrexe=llr64.exe
//llrexe=llrCUDA.exe

// This is the name of the PFGW executable. On Windows, this needs to
// be the PFGW console application, not the GUI application.
// PFGW can be downloaded from http://tech.groups.yahoo.com/group/openpfgw/
// If you are running a 64 bit OS, comment out the pfgw32 line
// and uncomment the pfgw64 line.
//pfgwexe=pfgw32.exe
pfgwexe=pfgw64.exe

// This is the name of the genefer executables used for GFN searches. Up
// to four different Genefer programs can be specified. The client will
// attempt a test in the following order if applications are available:
// genefercuda/geneferocl, genefer, and pfgw. If a round off error
// occurs, the test will restart with the next available application in the
// same order. The order they are specified below is not important.
// If you are running on a 64 bit OS, uncomment the genefer64 line.
// If you have an Nvidia Compute Capability 1.3 or greater GPU, you may uncomment the genefercuda line.
// If you have an OpenCL-capable GPU with double precision support, you may uncomment the geneferocl line.
// GeneferOCL may be faster than GeneferCUDA for some Nvidia GPUs - we recommend you test both and choose the fastest.
geneferexe=geneferocl.exe
//geneferexe=genefercuda.exe
//geneferexe=genefer32.exe
geneferexe=genefer64.exe

// This is the name of the executable used for Wieferich and Wall-Sun-Sun searches.
// Available ONLY to 64bit OS. Uncomment if you have 64bit OS.
// If you have an OpenCL-capable GPU, uncomment 'wwwwcl'
//wwwwexe=wwww.exe
//wwwwexe=wwwwcl.exe
//wwwwexe=wwwwcl64.exe

// This sets the CPU affinity for LLR on multi-CPU machines. It defaults to
// -1, which means that LLR can run on an CPU.
cpuaffinity=

// This sets the GPU affinity for CUDA apps on multi-GPU machines. It defaults to
// -1, which means that the CUDA app can run on an GPU.
gpuaffinity=

// Set to 1 to tell PFGW to run in NORMAL priority. It defaults to 0, which means
// that PFGW will run in IDLE priority, the same priority used by LLR, phrot,
// and genefer.
normalpriority=0

// This option is used to default the startup option if the PREVIOUS
// SHUTDOWN LEFT UNCOMPLETED WORKUNITS. If no previous work was left
// this will act like option 9.
// 0 - prompt
// 1 - Return completed work units, abandon the rest, then get more work
// 2 - Return completed work units, abandon the rest, then shut down
// 3 - Return completed, then continue
// 4 - Complete in-progress work units, abandon the rest, then get more work
// 5 - Complete in-progress work units, abandon the rest, then shut down
// 6 - Complete all work units, report them, then shut down
// 7 - Complete all work units then shut down (do not report completed work)
// 9 - Continue from where client left off when it was shut down
startoption=9

// stopoption= tells the client what to do when it is stopped with CTRL-C and there is
// work that has not been completed and returned to the server. Options 2, 5, and 6 will
// return all workunits. This will override stopasapoption. The accepted values are:
// 0 - prompt
// 2 - Return completed work units, abandon the rest, then shut down
// 3 - Return completed work units (keep the rest), then shut down
// 5 - Complete in-progress work units, abandon the rest, report them, then shut down
// 6 - Complete all work units, report them, then shut down
// 7 - Complete all work units then shut down (do not report completed work)
// 9 - Do nothing and shut down (presumes you will restart with startoption=9)
stopoption=9

// stopasapoption= tells the client that it needs to be shutdown automatically, i.e. without
// a CTRL-C. It is evaluated after each test is completed. It should be 0 upon startup.
// The accepted values are:
// 0 - Continue processing work units
// 2 - Return completed work units and abandon the rest
// 3 - Return completed work units (keep the rest)
// 6 - Complete all work units and return them
// 7 - Complete all work units then shut down (do not report completed work)
stopasapoption=0

// Timeout on communications errors
// (default is 60 minutes, minimum is 1 minute if not specified here...)
// Note that the actual used in the client is anywhere from 90% to 110% of this value
errortimeout=1

// Size limit in megabytes for the prpclient.log file...
// 0 means no limit.
// -1 means no log.
loglimit=1

// Set the debug level for the client
// 0 - no debug messages
// 1 - all debug messages
// 2 - output debug messages from socket communication
debuglevel=0

// Whether or not to echo "INFO" messages from server to console for accepted tests
// 0 - no echo
// 1 - echo (default)
echotest=1

____________

Proud Founder of
Have a look at my WebCam

What project do you want to run? I think genefer. You must exclude every CPU and GPU in an extra folder and setup the file.

Not sure what the means. Create another folder and just run CPU in that one and run GPU only in the original ?

Yes genefer
____________

Proud Founder of
Have a look at my WebCam

OK thanks I will try that. I guess I will have to manually modify every time instead of running the ini update bat ?

____________

Proud Founder of
Have a look at my WebCam

OK thanks I will try that. I guess I will have to manually modify every time instead of running the ini update bat ?

Last night I created two folders one for CPU and one for GPU and run them as required. As I only have one GPU running in the this PC I have the GPU running one instance and the CPU running four instances. That way I can change the master ini file in each folder and not have to remember to change all the Instances ini.

Thanks to John for the PM today, great minds think alike.
____________

Proud Founder of
Have a look at my WebCam