Some code errors and optimisations

[color=#0066ff][b]There are identical sub-expressions to the left and to the right of the '!=' operator: p->mod_death != p->mod_death char.c 503
The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 76, 80. raconf.c 76
There are identical sub-expressions to the left and to the right of the '&&' operator: p[1] == '-' && p[1] == '-' script.c 913
The 'masterstatus->speed' variable is assigned to itself. status.c 2074
Consider inspecting the condition. The 'FindFileData.cFileName' pointer is always not equal to NULL. utils.c 139
It is incorrect to compare the variable of BOOL type with TRUE. Correct expression is: 'TryEnterCriticalSection(& m->hMutex) != FALSE'. mutex.c 93
Use _beginthreadex/_endthreadex functions instead of CreateThread/ExitThread functions. thread.c 194
Decreased performance. It is inefficient to identify an empty string by using 'strlen(str) == 0' construct. A more efficient way is to check: str[0] == '\0'. login.c 502
Decreased performance. It is inefficient to identify an empty string by using 'strnlen(str) > 0' construct. A more efficient way is to check: str[0] != '\0'. login.c 983
Decreased performance. Calls to the 'strlen' function have being made multiple times when a condition for the loop's continuation was calculated. npc.c 2883
Decreased performance. The 'strlen' function is called twice in the specified expression to calculate length of the same string. irc-bot.c 282
Decreased performance. It is inefficient to identify an empty string by using 'strlen(str) > 0' construct. A more efficient way is to check: str[0] != '\0'. log.c 367
Decreased performance. It is inefficient to identify an empty string by using 'strlen(str) > 0' construct. A more efficient way is to check: str[0] != '\0'. map.c 3645[/b][/color]