You are not logged in.
- Topics: Active | Unanswered
Announcement
#1 2013-02-09 00:59:59
- Kansas1327
- Player
- Reputation: +2
- Registered: 2012-11-20
- Posts: 81
- Website
Making a Windows server compatible with v1.6, v1.61, v1.612
At the same time, making it no-cdkey. Is this possible?
Offline
0 
0
#2 2013-02-11 01:32:13
Re: Making a Windows server compatible with v1.6, v1.61, v1.612
BF1942 Windows server v1.612 doesn't check for CD-keys and it's now patched to accept all client versions. It has the problem, that you are certainly aware, keyhashes are not displayed.
Offline
0 0
#3 2013-02-11 10:01:28
- Kansas1327
- Player
- Reputation: +2
- Registered: 2012-11-20
- Posts: 81
- Website
Re: Making a Windows server compatible with v1.6, v1.61, v1.612
Thanks! I tried it out and I can run the server on pure with v1.61 and join fine, however when I try joining on v1.6 it tells me data differs from server, but it works if I turn off pure mode.
Offline
0 0
#4 2013-02-11 14:37:02
Re: Making a Windows server compatible with v1.6, v1.61, v1.612
I tried it out and I can run the server on pure with v1.61 and join fine, however when I try joining on v1.6 it tells me data differs from server, but it works if I turn off pure mode.
BF1942 clients v1.6 have different init.con and contentcrc32.con files from v1.61 and v1.612, that's why they fail the content check.
Offline
0 0