• 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 Problem...

Jagators

Senior member
I have a Drive on one of my nodes about to give up the ghost. Is there a way to keep my current node ID and stats when I replace it?? Also, I'm getting tired of baby sitting these 8 boxes because of spinning wheels. Anyone know of a fix coming out to help this problem?? I haven't been on this project that long, but the first client I downloaded didn't seem to have this problem.
 
To keep the same node ID, back up the file <D2OL home>\D2OL\res\node.prp. Then if/when you reinstall the client, exit out of the install at the point where it asks you to enter an e-mail address, and copy the file above to the proper place. You can also do the same with the stats.prp file for stats.

 
I like the speed of the new client but I'm losing about 30% of my production due to the constant lock ups. I'm to the edge of my patients right now.:|:|
 
Just made a post about this I am really getting angry about this. HOW DARE THESE IDIOTS WASTE OUR CONTRBUTION !!!!!! THEY ARE SENDING US VIRUSES INSTEAD!! GIVE THEM HECK! VIRUS = causes program to crash IS THIS THE REAL PURPOSE OF THIS PROJECT?
 
NO It was not . I am sorry. I am very frustrated with this project, it seems to waste more cycles than it uses
 
actually, I think it was a bit unfair to lock it down.

Yes, it was a rant, but it was also a call for action for TeAm D20L to let Sangent know about the frustrations of the team, and I think that that has its place. Maybe if the tone was turned a little? /shrugs.
 
I'm thinking about giving the project one more week, and if it continues to require that I still baby sit it, I will look for something else. :disgust:
 
I'm also willing to give them a little longer to fix the problem. We have to remember that the new client just came out and it will take them some time to fix. They should have a better method for pre-release testing to avoid these problems but it is too late for that now. I hope they will learn their lesson for further client releases.

I have one particular machine (my fastest) that is constantly locking up so until the problem is fixed I'm going to switch that pc to a different project.
 
Back
Top