30.10.2010, 00:37
Its fixed!
The way to see the config.ini in action -so to speak- is logging it. The site that I was directed to had a response that instructed how to do this, so I did it. I didn't see EXACTLY what the deal was, but there was no mention of the MOD that allegedly cause the problem. So before re-installing I tried a system restore point. Because there was a lot of stuff in that log that pointed to video resolution errors and a java error then all stopped. I did this two or three times to be sure. The system restore point worked.
Thank you all who responded. I learned a good lesson... no more auto install stuff.
Thanx
The way to see the config.ini in action -so to speak- is logging it. The site that I was directed to had a response that instructed how to do this, so I did it. I didn't see EXACTLY what the deal was, but there was no mention of the MOD that allegedly cause the problem. So before re-installing I tried a system restore point. Because there was a lot of stuff in that log that pointed to video resolution errors and a java error then all stopped. I did this two or three times to be sure. The system restore point worked.
Thank you all who responded. I learned a good lesson... no more auto install stuff.
Thanx