OK User.ini problem people - I need your input

OK guys, d/l and run this.

All this program does is alternate reading your username out of User.ini, and reads the MapExt key out of ArmyOps.ini, the number of times you specify.

Make sure you've got your known working User.ini file in your AA\System folder.

I have the program defaulted to 100 iterations, but bump it up to a 1000 if you want.

This code is pulled directly out of CDC and just modified to run through a loop.

So just run it, and then take a look at your User.ini file.

And then I'd like you to come back here and tell me the results.



http://KustomAppz.fragout.com/CDSystem/DL/UserIniTest.zip

I did this on 100, 1000, and 10000.

The results were identical every time.

If you need more testing, feel free to contact me. I am available nearly 24/7.

Stupid me forgot to post results:

Each line looked as follows:
#: [AH]Dotarp
#: aao


I ran it on 100,000 also.

same as above results

What, you get [AH]Dotarp in yours too,

I ran it 100,1000,10000 results were the same
#[1-6]NoD
#aao

works...What will this be used for?

SplittinWigs is a h4x0r!!!

Hydra, has this helped at all. I'm curious

I went up to 1000 iterations and it still can't read my name from my user.ini file. I have reinstalled twice (AAO and CDC 1.4). Still can't find the problem.

Yes guys, it has helped.
It has helped me prove what I was saying that I found out earlier.

IT IS NOT CDC CORRUPTING YOUR USER.INI.

Even when I gave an explanation of what was going on, there was still people who insisted that it was CDC.
"It only happens when I run CDC" type of stuff.

If you can run this little tool in a 100,000 loop, and it doesn't mess up your User.ini or your ArmyOps.ini, I think it's safe to say that it's not CDC doing it, as the code is taken right from CDC. I just added the ArmyOps.ini to the mix and had it run through a loop the number of times you specified.

What I was really looking for is someone to come back here and say that it did, which of course they can't, because it's not.


Thanks for the help guys.

*cough* What about this one then?

I went up to 1000 iterations and it still can't read my name from my user.ini file. I have reinstalled twice (AAO and CDC 1.4).

Errare humanum est, ergo non humanus sum.

Open your User.ini file up in Notepad.
Then choose Save As from the menu and change the encoding type to ANSI.

Then try it.

This is what I've been saying. AA itself is changing your User.ini to Unicode, which CDC doesn't read yet.

But allot of people were saying that it was CDC doing it. Which it's not.

Post edited by [RIP]Hydra at 6/15/2003 6:09:10 PM

For what it's worth Hydra, myself and a few others defend CDC and you in #twl_aa

Again, let me know if you need more help.

1. How do i change the code. I can't find that (win98SE)

2. I just made an user.ini and saved it as read-only. I can't change mys settings now but AA doesn't corrupt my ini file either. So CDC works like a charm everytime. Just get a good copy off your user.ini and make a backup off it. Put it as read-only and your CDC problem is solved. If you are A UA player you change it back to archive because otherwise it wont work. I had this problem and it's resolved. Btw: sry if i couldn't discuss UA here.

I set it at 100,00 times. in 1:53 (roughly) Is that a good time? Yeah, I got the benchmark bug, new comp..:>)

100=instantly
1000= < one second
10000= 15 seconds

I gotta get out more...
Post edited by [HEL]Big Nose at 6/16/2003 6:11:58 PM

Hey Hydra. I have a question for you. I know AA is what is doing it, but does it do it on a clean install with no CDS? I'm just wondering cause this happened on CDS v1.3 and beyond. So I'm just wondering if it's just AA or if CDS causes AA to mess it up. It's not that I don't believe you, cause AA is causeing the inconsistancies, but I'm just wondering if it is only AA. If this is a stupid idea sorry lol. I just have a nack for looking for any extra problems in programs.

Originally posted by: -SOS_Brainiac-

Hey Hydra. I have a question for you. I know AA is what is doing it, but does it do it on a clean install with no CDS? I'm just wondering cause this happened on CDS v1.3 and beyond. So I'm just wondering if it's just AA or if CDS causes AA to mess it up. It's not that I don't believe you, cause AA is causeing the inconsistancies, but I'm just wondering if it is only AA. If this is a stupid idea sorry lol. I just have a nack for looking for any extra problems in programs.

No, it's not a stupid idea.

CDC has already read your User.ini file by the time that AA starts, and doesn't use it any time after.

So if CDS is not on a system, then does AA mess up with the unicode? Or is only on systems with CDS? That was my question in short lol.

Your INI file will change to Unicode regardless of whether CDC is installed or not.

But, AA can work with ANSI and/or Unicode.

When you do a fresh install of AA, your INI file is in ANSI.
The first time you log on, AA will change it to Unicode.

Providing that your INI files news section is different than the current news.