2. Restore the 4 databases in db folder, maintaining their respective names: - rf_account - rf_world - rfweb - exgame
3. Edit the 3 ini files located under \RFServer\RF_Bin\Initialize\, change all IP's to your IP. - AccountSystem.ini - LoginSystem.ini - WorldSystem.ini
4. Run the odbc.reg file. Double Check User DSN under ODBC, it uses Windows NT Authentication, test the source. Load servers on this order, - LoginServerSR.exe - AccountServerSD.exe - ControlServerR.exe - ZoneServerD.exe
First time Zoneserver loads it gives some kind of error message, just hit OK.
How to tell if it's loaded properly? LoginServer and AccoutServer windows both have some lines where it displays false/true. LoginServer's "True" indicates zone is connected. AccountServer's "true" indicates ControlServer connected. At least that's what I think. tongue.gif
Zone loads roughly 2 to 5 mins depending on your hardware. seems light on resources.
Connecting client: rfonline_client_exe.rar contains the exe and ini files needed. Edit the IP in the ini file to your server IP. You'll actually need a specific client pack to use that RF_Debug_Dev.exe, or should I say "old style client". Anyway, the client roaming around is a lil over 200mbs. I will prolly host the client on my server for a bit, even though it's not fast download. >_>;
Some notes: This package is just about the same as how we found it. I think there are different client/server versions running around. This specific client doesn't match the server protocol 100%; hence, it has a chat bug and shops not working. There are servers out there with these already fixed, or have "better match", so it is "fixable".