Now I'm REALLY ticked off!!

TheyCallMeSAK

Senior member
Jun 21, 2000
690
0
0
It was bad enough to not have a warning about the switch to OGR. After fixing all of my clients with the

[misc]
project-priority=RC5,DES=0,CSC=0,OGR=0

OGR came back!! I had to restart the system I'm on for something. Just now I noticed its back cracking OGR packets! Sure enough, I checked the dnetc.ini file and wouldn't ya know it:

[misc]
project-priority=RC5,DES=0,CSC=0,OGR=

That is what it said. Does this thing have a mind of its own. It changed the config file on you without your permission!
 

dvch

Senior member
Jun 28, 2000
752
0
0
Mine were all done from the configure command and have remained active after reboots.
 

dawks

Diamond Member
Oct 9, 1999
5,071
2
81
Perhaps you didnt save the file??
Thats the only explination I can think of.. Mine works fine now..
 

MWalkden

Golden Member
Dec 7, 1999
1,082
0
0
I'm not aware of this being a problem either. I would have to say something else caused the issue although I wouldn't have a clue what. Maybe a bad cut and paste? Try switching it back and see if it happens again. If it does, then I would say this thing really is a trojan!
 

Hossenfeffer

Diamond Member
Jul 16, 2000
7,462
1
0
Another alternative would be to set the priority to RC5,OGR=0 and forget the other two. I mean, really, what have they ever done for you? Besides the occasional load of laundry, that is.

Sleepless night + bad sense of humor = amazing forum posts
 

Drakkhen

Senior member
Nov 9, 1999
824
0
71
Are all of your clients sharing the same .ini file?

I would make changes to the .ini file, and if any of the other clients were active, the .ini file wouldn't update.

Just a thought.