v22.9 service problem

PageFault · 2002-09-13, 23:53

I got permission to put the client on some new boxen at work. OS is w2k pro sp2. Setup is one group use account, no others except administrator.

I tried v22.9 in order to avoid the old firedaemon routine. After logging in as the group user I checked and prime had not started. So, I changed the priviledges to administrator for that account, started the client and toggled the run at startup a few times. That seemed to (hopefully) have done the trick - I will see next time some idiot reboots it simply because the button is there.

This afternoon I set up on the other machine. Same problem, it would not run under the group account. I didn't have time to fiddle so it most likely won't be crunching for long.

Anyone else have this happen?

smoffat · 2002-09-25, 01:06

See the "Couldn't open service control manager" thread just up one in the list. This is the same problem and George promises it will be fixed in next beta. Either put it in the Startup folder or add a new Item to the Start key in the registry as a workaround.

PageFault · 2002-09-26, 01:35

The machines operated correctly after a full shutdown. It seems that logging on to the other account was not enough to force a re-read of the registry. All is well with the production increase.

2002-09-13, 23:53	#1
PageFault Aug 2002 Dawn of the Dead 5×47 Posts	v22.9 service problem I got permission to put the client on some new boxen at work. OS is w2k pro sp2. Setup is one group use account, no others except administrator. I tried v22.9 in order to avoid the old firedaemon routine. After logging in as the group user I checked and prime had not started. So, I changed the priviledges to administrator for that account, started the client and toggled the run at startup a few times. That seemed to (hopefully) have done the trick - I will see next time some idiot reboots it simply because the button is there. This afternoon I set up on the other machine. Same problem, it would not run under the group account. I didn't have time to fiddle so it most likely won't be crunching for long. Anyone else have this happen?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Factoring as a service	Nick	Factoring	8	2016-03-18 03:37
NT service version 25	Prime95	PrimeNet	28	2008-12-08 08:32
LLRNet as a NT service	rover	Sierpinski/Riesel Base 5	6	2006-10-02 13:43
How to fix the Prime95 Service	E_tron	Software	1	2003-10-05 03:55
FireDaemon (or P95 service) question.	Deamiter	Software	9	2002-11-12 19:32

2002-09-25, 01:06	#2
smoffat Sep 2002 10₁₆ Posts	See the "Couldn't open service control manager" thread just up one in the list. This is the same problem and George promises it will be fixed in next beta. Either put it in the Startup folder or add a new Item to the Start key in the registry as a workaround.

2002-09-26, 01:35	#3
PageFault Aug 2002 Dawn of the Dead 353₈ Posts	The machines operated correctly after a full shutdown. It seems that logging on to the other account was not enough to force a re-read of the registry. All is well with the production increase.