• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

D2OL New Client Issues

Slatzman

Golden Member
We seem to have problems being reported in a few different threads, so here is a central thread to keep track of issues right now with the new client.

I too have had problems the last few days with the client locking up on a zero rotational bond candidate.

Here are the directions to killing your queue. This is a cut and paste from someone elses post

Please try following these steps to completely clear out the cache of your client.

1. Close out and exit your agent.
2. Navigate into the directory where your client is located.
3. Go into the ?res? directory and delete your tasks.dat file.
4. Inside the ?res? directory, navigate into the ?data? directory and then into ?taskdata?.
5. Open up the ?structs? directory and delete all directories and files inside there.
6. You can now restart your client which will then download a new cache of candidates to process.
This should correct the problem your client is having by removing any corrupted candidates it might have downloaded.
If your client continues to experience these problems after going through these steps please let us know about it so that we may continue to troubleshoot this for you.

Please post any other problems and fixes and we will link this thread to the sengent folks if necesary.

Slatz
 
I concure with Geoffs.

Also would the memory hog be a problem? (As stated in the other topics the Mac OS 10 new client only uses 50MB...)

 
Originally posted by: RemyCanad
I concure with Geoffs.

Also would the memory hog be a problem? (As stated in the other topics the Mac OS 10 new client only uses 50MB...)

Yep its a problem but we cant do a lot about it 🙁.

 
What is a "a zero rotational bond candidate" and how do you detect it?

I've tried installing D2OL on machines where it did not work, in the process I've created two nodes that I can't use! Is there a way to salvage a file from a non-working machine that will allow me to salvage the node number? The particular system only has a floppy drive and 56k dial-up, so I'm not going to take the whole SengentD2OL directory.
 
Originally posted by: JWMiddleton
What is a "a zero rotational bond candidate" and how do you detect it?

I've tried installing D2OL on machines where it did not work, in the process I've created two nodes that I can't use! Is there a way to salvage a file from a non-working machine that will allow me to salvage the node number? The particular system only has a floppy drive and 56k dial-up, so I'm not going to take the whole SengentD2OL directory.

I know it might sound like I`m on a recruiting drive for malör, but the easiest way to see this is with DSpy
Also look for node.prp for node and stats.prp for stats (obviously 😉) in SengentD2OL\D2OL\Res
 
Originally posted by: tbates757
darnit! another Conformer #1 freeze, there goes another 5 hours of crunching... :disgust:

If you open the task manager, what is using all your cpu time when the conformer freezes ?
 
Andy, good question about what was using the CPU. For me, I wondered why Dockwin was still using it all the last time mine locked up...which I would like to say was 27 hours ago..woohoo...my first whole day without a lockup since the upgrade...could things be getting better?!?!
rolleye.gif


Slatz
 
I haven't had either of my machines lock with a candidate having zero rotational bonds. But I did watch my second machine burn through one @ 10-12secs per conformer. If I was here to baby sit the machine, I'd like to have a hundred of those in my queue. 😀
 
Originally posted by: JWMiddleton
What is a "a zero rotational bond candidate" and how do you detect it?

I've tried installing D2OL on machines where it did not work, in the process I've created two nodes that I can't use! Is there a way to salvage a file from a non-working machine that will allow me to salvage the node number? The particular system only has a floppy drive and 56k dial-up, so I'm not going to take the whole SengentD2OL directory.

Actually you dont have to add the node to the TeAm, it can run fine without adding it. If you find you have to delete it just ignore it. When you get a good one running then add it.

There is a way to save the node number, its posted in one or two threads here and over at the Sengent Forums. Something like install and shut down at the registration screen, then replace a file with one you save from the original folder.

 
I started getting Invalid Page Faults in DockWin.exe errors. I posted in the D2OL support forum.

I had another node with a different issue that I fixed by deleting the files that Statsman and GeoffS stated above. 🙂

I just started D2OL a week ago. Was there this much trouble prior to the client 'upgrade' a few days ago?

viz
 
It seems my client freezes at Initializing Engine... on both my Linux AND Windows machine! I have tried restarting both but to no avail, I think there is clearly something wrong on their side of the coin.
 
tbates, is it because your que is empty?

Viztech, I hope you can get an answer soon. I havent experienced this on any of my nodes.

We now have an email addy which slatzman has posted and Badsac is now aware of the server probs.
 
Back
Top