Upgrading old Underfoot Server

[Uleat]

Some people put a shared_memory.exe call in their script to make sure that it's up-to-date every time.

You should at least make sure that it's run once..you may need to create the sub-folder '\..\shared\' in your server directory, if it doesn't exist.

(It does need to be run whenever there are changes to database entries or, especially, when there are changes in pertinent structure sizes in the code.)


Are you using 32-bit or 64-bit binaries?

[Warking]

I added the shared folder and the shared_memory.exe in the startup script. I should be using x64 binaries but the C++ runtime is calling for x32 so it might be x32 on a 64bit server. there a way to call up an output to show binary bit?

The one thing I noticed was there are new loginDB tables under the base PEQ DB. Do we not use a seperate DB for account logins anymore? Because last login is not populating in any login tables but the account is able to login initially... I do not see the server listed and eqlaunch.exe screen is blank.

Wassn't there some table in PEQ where I need to update the name of the server and login info? Like in rule_values or something? Since I overwrote the entire DB? Something is not calling the correct login DB and Server...

[Warking]

I just found multiple login server entries in the PEQ DB

login_server_accounts.

And

tblloginserveraccounts


It looks like when it works it is reading from the login_server_accounts and not the older peqlogindb or the PEQ DB > tblloginserveraccounts

I dont care if I have to copy the tables over for account logins. I just need to get is working for one. whereever the login tables are... then copy over the accounts....

Is this a normal occurance? I must be missing some setting somewhere

[Warking]

ok... so after I determined that the login tables were different I copied the table entries

From --- To
peqlogindb>tblloginserveraccounts --To-- PEQ>login_server_accounts

peqlogindb>tblserveradminregistration --To-- PEQ>loginserver_server_admin_registration

peqlogindb>tblserverlisttype --To-- PEQ>lloginserver_server_list_type

peqlogindb>tblworldserverregistration --To-- PEQ>loginserver_world_server_registration

Then... I noticed that world.exe would not load unless 127.0.0.1 instead of localhost was in the eqemu_conf file. So I changed that as well. Again still using the the older EQEMUloginserver.exe

Then updated the start script:

@echo off
Echo Starting EQEmuLoginServer
c:
cd C:\eqemu
echo
shared_memory.exe
echo
start eqemuloginserver.exe
echo
start world.exe
echo waiting for the world to finish before starting zone...
ping -n 10 127.0.0.1 > nul
start queryserv.exe
start ucs.exe
start eqlaunch.exe zone
exit

I was now able to see the eqlaunch.exe change to sleeping. and have the below output on the server windows. BUT When trying to login to a zone (tutorialb) the eqclient just crashes. When trying to enter crescent reach as well with a new toon EQ crashes.

Nothing notable in the log file but I see the below in world.exe when trying to zone in:

[World Server] Loading variables..
[World Server] Loading zones..
[World Server] Clearing groups..
[World Server] Clearing raids..
[World Server] Clearing inventory snapshots..
[World Server] Loading items..
[World Server] Loading skill caps..
[World Server] Loading guilds..
[World Server] Loaded default rule set 'default'
[World Server] Loading EQ time of day..
[World Server] Loading launcher list..
[World Server] Reboot zone modes OFF
[World Server] Deleted 0 stale player corpses from database
[World Server] Loading adventures...
[World Server] Purging expired instances
[World Server] Loading char create info...
[World Server] Zone (TCP) listener started.
[World Server] Client (UDP) listener started.
[World Server] New TCP connection from 127.0.0.1:52963
[World Server] New TCP connection from 127.0.0.1:52965
[World Server] New TCP connection from 127.0.0.1:52967
[World Server] New connection from 192.168.1.162:51104
[World Server] Checking inbound connection 192.168.1.162 against BannedIPs table
[World Server] Connection 192.168.1.162 PASSED banned IPs check. Processing connection.
[World Server] New TCP connection from 127.0.0.1:52969
[World Server] New TCP connection from 127.0.0.1:52971
[World Server] New TCP connection from 127.0.0.1:52973
[World Server] New connection from 192.168.1.162:51108
[World Server] Checking inbound connection 192.168.1.162 against BannedIPs table
[World Server] Connection 192.168.1.162 PASSED banned IPs check. Processing connection.
No start_zones entry in database, using defaults

but there is a start_zones table

************************************************** **

Thanks, I might try to spin up another VM to compare as well. I can get to character create now so that is a plus... can't zone in