Too many sections in worktodo.txt. Line #4

[TheOutcaste]

After upgrading from V24.14 to V25.8, I get the above error every time I reboot one system, a Pentium D 3.0 GHz running XP Media Center 2005. (only dual core I have)
This is the Communication screen:

[Main thread Jan 2 05:40] Mersenne number primality test program version 25.8
[Main thread Jan 2 05:40] Too many sections in worktodo.txt.  Line #4
[Comm thread Jan 2 05:40] Exchanging program options with server
[Comm thread Jan 2 05:40] URL: http://v5.mersenne.org/v5server/?v=0.95&px=GIMPS&t=po&g=9a5d9624314082c05f6b81dc8b38267e&nw=1&ss=28370&sh=7C10562A7991AB8258F4BB
[Main thread Jan 2 05:40] Starting worker.
[Main thread Jan 2 05:40] Too many sections in worktodo.txt.  Line #4
[Comm thread Jan 2 05:40] RESPONSE:
[Comm thread Jan 2 05:40] pnErrorResult=0
[Comm thread Jan 2 05:40] pnErrorDetail=SUCCESS
[Comm thread Jan 2 05:40] od=6
[Comm thread Jan 2 05:40] ==END==
[Comm thread Jan 2 05:40] 
[Comm thread Jan 2 05:40] Done communicating with server.

Worker #1 is set to use both cores.
Worker #2 window is blank. If I stop Prime95, Worker #2 window icon stays green.
Click Continue, Worker #1 is set to core 0, Worker #2 is set to core 1, but is immediately stopped.
If I exit Prime95, then restart, it will sometimes work.
Only consistent way to get both Worker threads running is to exit Prime95, open worktodo.txt in notepad, save it (no changes made, just File | Save), then restart Prime95.

Worktodo.txt has just 5 lines, no non-printing characters. I've copied the text out of notepad into notepad++ and saved from there, no change. Manually typed the lines into a new file, save it, no change.

Not sure if this is related, but if I log off, then log back on, Prime95 will not start.
When I manually start Prime95, I get the same results as above.

I've unchecked the Start at Bootup option, then rechecked it. It does remove the Prime 95 Service from Services, then re-creates it.
Service startup is set to Automatic, but the service never shows as started, and cannot be started. When I try to start it, I get the following error:

Event Type:    Error
Event Source:    Service Control Manager
Event Category:    None
Event ID:    7034
Date:        1/2/2009
Time:        6:28:04 AM
User:        N/A
Computer:    BAMMBAMM
Description:
The Prime95 Service service terminated unexpectedly.  It has done this 2 time(s).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Jerry

[Uncwilly]

Can you post your worktodo.txt? IIRC the problem may have to do with too many parts on the line and can be fixed by editing and a manual com.

[TheOutcaste]

Sorry, forgot to include that in the OP:

[Worker #1]
Test=D9C7074A9BD287022458EACB5496B1A3,46634339,68,1

[Worker #2]
Test=F2D7AD994EFC1F5F204CF8AC4197F4E0,48070933,69,1

After fixing my speed issue by removing the CPUSpeed= line from local.txt I thought this might be similar, as the old local.ini files have an Affinity setting.
local.ini has an Affinity=0 line and loca0001.ini has Affinity=1

So in Local.txt, I Removed Affinity=100, then rebooted. Only one worker started, and Test | Status doesn't mention Worker #X any more, just shows the work for Worker #1
Went to Test | Worker windows... and set # of Worker Windows to run from 1 to 2 and the 2nd worker started right up.

Local.txt has the following lines now:
Affinity=100
WorkerThreads=2
and these are different:
SrvrPO9=2 (Was 1)
SrvrP00=20 (Was 17)

It seems to be working just fine now, have rebooted twice and it starts correctly.

Also seems to have fixed the Service issue; Services now shows the Prime95 service as started, and I can log off and it continues running. However, after logging in, the tray icon is red, and the Tool Tip does not list each Worker, just says Prime95.

Stop/Continue fixes that. I only waited about 2 minutes, so it might have fixed itself eventually, perhaps after the next screen output. I'll have to test that later and report back.

Jerry