PDA

View Full Version : ht now only running one instance?!?! HELP


faruquehabib
02-28-2005, 08:38 AM
ok, so my p4 520 w/ ht was running 2 instances of d2ol like it should, 100% cpu usage and all. then this morning, all of a sudden i notice cpu usage at only 60% and its only been 60% for the last hour and a half. so i check my processes and sure thing, only one instance of d2ol is running. wtf happened? how do i fix this?? i want both of my instances runnin. i rebooted thinking that would fix it, but still, only one is running.

edit - and when i check my nodes on the d2ol website, it says my second node on the ht rig has been working for 3 hours less than the 1st node. that must be due to my above-mentioned problem. hmmm...

lv_dicedealer
02-28-2005, 09:10 AM
I had this happen too. I saved my node.prp files from each d2ol folder, then uninstalled and reinstalled d2ol using rodzilla's installer, then replaced the new node.prp files with the old ones. I know it is over-kill, but I rebooted between uninstalling and reinstalling. Now all is good again with d2ol, windows still sucks.

faruquehabib
02-28-2005, 09:26 AM
I had this happen too. I saved my node.prp files from each d2ol folder, then uninstalled and reinstalled d2ol using rodzilla's installer, then replaced the new node.prp files with the old ones. I know it is over-kill, but I rebooted between uninstalling and reinstalling. Now all is good again with d2ol, windows still sucks.


that seemed to work. running both instances now. thanks :D

lv_dicedealer
02-28-2005, 09:49 AM
np ;)

Mr_Slinky
02-28-2005, 10:36 AM
i had the same problem and just restarted my computer and worked fine since

Disposibleteen
03-01-2005, 06:35 AM
this seems to happen when D2OL s running as a service, it shuts itself down every now and then, that is why i took it off as a service so i can know for sure when it is running just by looking at the taskbar, and it never shuts off

Rodzilla
03-01-2005, 08:00 AM
The reason your node most likely stopped was because it came across a corrupt piece of task data. 99% of the time doing a "flush all task" data will cure the problem.

What happens is D2OL will start to crunch on the corrupt candidate and it will get stuck. Dockwin.exe will be stuck open and become non-responsive to D2OL.exe commands. This throws D2OL.exe into a fit and it will start to discard candidates because it cannot dock them (Dockwin.exe is already open and locked)

So what you do is kill the dockwin process... stop the task engine... and hit "flush all task" in the status screen. Then reboot the PC and start the node. It should fire right up! :up:

faruquehabib
03-01-2005, 08:47 AM
The reason your node most likely stopped was because it came across a corrupt piece of task data. 99% of the time doing a "flush all task" data will cure the problem.

What happens is D2OL will start to crunch on the corrupt candidate and it will get stuck. Dockwin.exe will be stuck open and become non-responsive to D2OL.exe commands. This throws D2OL.exe into a fit and it will start to discard candidates because it cannot dock them (Dockwin.exe is already open and locked)

So what you do is kill the dockwin process... stop the task engine... and hit "flush all task" in the status screen. Then reboot the PC and start the node. It should fire right up! :up:

Rod -

does this work with the nodes running as a service? because that's how mine are set up. if so, then i dont understand how to 'flush all task'...where exactly is that? when you push ctrl+alt+del?

Rodzilla
03-01-2005, 09:50 AM
Rod -

does this work with the nodes running as a service? because that's how mine are set up. if so, then i dont understand how to 'flush all task'...where exactly is that? when you push ctrl+alt+del?

If you have it running as a service you will need to make it run as a normal task temporarily.

Stop the service in the service manager and kill the Dockwin process... Go to the C:\XS_D2OL\D2OL1\D2OL folder and launch D2OL with the D2OL.exe file. That will start it in the system tray... then you can get to the status screen to dump the task.

faruquehabib
03-01-2005, 09:58 AM
If you have it running as a service you will need to make it run as a normal task temporarily.

Stop the service in the service manager and kill the Dockwin process... Go to the C:\XS_D2OL\D2OL1\D2OL folder and launch D2OL with the D2OL.exe file. That will start it in the system tray... then you can get to the status screen to dump the task.


awesome, i will remember that the next time it quits on me. thanks alot bro :toast:

Rodzilla
03-01-2005, 10:00 AM
As long as you didn't end up with a dead node... the way you did it was just as good! :up: