DeadMeat
8th August, 2004, 07:44 PM
Sorry if this is a duplicate... had problems first time....
Since I run Linux based servers, I was jumping with joy when I saw 111 supported them... YeaHaw!! Thx Prof!
Then I started testing and haven't been able to get it to work on a bunch of server combinations. The common problem is that the clients get a report of a hacked QValidate111. The log reports:
QValidate: QValidate Client-side error!!!
QValidate: Hacked package detected!
QValidate: Player Name : JustTestn
QValidate: Player IP : 192.168.100.104:1747
QValidate: Package Name: QValidate111
QValidate: Local Hash : 73A88265B019540E6DC3621DA9C5542F
QValidate: Remote Hash : C1856A1E8BC3F13ED8451A2BC08EDD85
QValidate: ########################################
The QValidate* files have been verified as being identical using fc /b on the clients.
The server install process was to get linux server version and follow the readme instructions. Download url was set to a web server I have. Left everything in the ini as is (but since have tried turning off logging to separate file which doesn't work). The log shows:
': +------------------------------------+
': | QValidate Loader V111 initialized! |
': +------------------------------------+
': Checked packages:
':
': 0: QValidate111
': 1: QValidateLoader111
': +------------------------------------+
Client installs were done initially with the autoinstaller. Then using manual install (clearing cache too).
I have tested this on the following server combinations (common gametype of TDM):
A RH8.0 (2.4.18-14) server with the UT server version 436
A RH7.3 (2.4.18-24.7.x) server with the UT server version 436
A RH7.3 (2.4.18-24.7.x) server with the UT server version 451
I have trimmed back all mutators on the 451 server to only include QValidate without effect.
The clients I have used to test with are:
Win2000 box with UT 436
XP box with UT 436
So far, no joy... Any ideas or should I just wait for 112.
GL HF
|LCN|DeadMeat
--
Software is evolutionary not revolutionary.
It takes lots bug and enhancements before it fills a niche for a long time.
Since I run Linux based servers, I was jumping with joy when I saw 111 supported them... YeaHaw!! Thx Prof!
Then I started testing and haven't been able to get it to work on a bunch of server combinations. The common problem is that the clients get a report of a hacked QValidate111. The log reports:
QValidate: QValidate Client-side error!!!
QValidate: Hacked package detected!
QValidate: Player Name : JustTestn
QValidate: Player IP : 192.168.100.104:1747
QValidate: Package Name: QValidate111
QValidate: Local Hash : 73A88265B019540E6DC3621DA9C5542F
QValidate: Remote Hash : C1856A1E8BC3F13ED8451A2BC08EDD85
QValidate: ########################################
The QValidate* files have been verified as being identical using fc /b on the clients.
The server install process was to get linux server version and follow the readme instructions. Download url was set to a web server I have. Left everything in the ini as is (but since have tried turning off logging to separate file which doesn't work). The log shows:
': +------------------------------------+
': | QValidate Loader V111 initialized! |
': +------------------------------------+
': Checked packages:
':
': 0: QValidate111
': 1: QValidateLoader111
': +------------------------------------+
Client installs were done initially with the autoinstaller. Then using manual install (clearing cache too).
I have tested this on the following server combinations (common gametype of TDM):
A RH8.0 (2.4.18-14) server with the UT server version 436
A RH7.3 (2.4.18-24.7.x) server with the UT server version 436
A RH7.3 (2.4.18-24.7.x) server with the UT server version 451
I have trimmed back all mutators on the 451 server to only include QValidate without effect.
The clients I have used to test with are:
Win2000 box with UT 436
XP box with UT 436
So far, no joy... Any ideas or should I just wait for 112.
GL HF
|LCN|DeadMeat
--
Software is evolutionary not revolutionary.
It takes lots bug and enhancements before it fills a niche for a long time.