World.exe problem after updating
 

I had an old version of EQemu, and thought I would try to make a server. Followed instructions to the 't', and world.exe worked, except it was an out-of-date. Easy, I thought, just download the new version.

However, I updated the EQemu, reread instructions and did this 3 times over, and still cannot figure out. When I fire up, world.exe, I get

Using database 'EQ' at localhost
Error in GetVariable query 'SELECT value FROM variables WHERE varname like 'hold
zones'' #1146: Table 'EQ.variables' doesn't exist
Loading zone names & items...Error in LoadZoneNames query 'SELECT MAX(zoneidnumb
er) FROM zone' #1146: Table 'EQ.zone' doesn't exist
done.
Loading guild ranks...done.
World server listening on: port 9000
Connected to LoginServer: eqlogin1.eqemu.org:5999

Subsequently, my server comes up as "LOCKED" as I have errors in my world and boot files.

Perhaps I missed something from repeatedly doing the instructions over again, but I am new to this and cannot figure out what.

boot5zones.win9x.bat
REM: ****Read this first!!!****

REM: This file requires your real IP in the place of "YourIP" when you are connecting
REM: To the EQEmu Loginserver.

REM: When you are using minilogin, Replace all IP Addresses to say 127.0.0.1

REM: If you still get errors try using localhost instead of 127.0.0.1

REM: zone9x.exe is for use with Windows 98 and ME only.
REM: If you are running Windows NT/2000 or XP use ZoneNT.exe

REM:--------------Start-----------------------


@echo off
start zone9x . 65.186.10.101 7995 65.186.10.101
start zone9x . 65.186.10.101 7996 65.186.10.101
start zone9x . 65.186.10.101 7997 65.186.10.101
start zone9x . 65.186.10.101 7998 65.186.10.101
start zone9x . 65.186.10.101 7999 65.186.10.101
exit
cls


REM:---------------END------------------------

db.ini
# READ README.TXT!

[Database]
host=localhost
user=Ooogachaaka
password=cubby
database=EQ


### --- This file tells world.exe what computer mySQL is on. Host should
### --- be left as localhost unless mysql is
### --- on a differant computer than world.exe.

loginserver.ini
### --- This file tells world.exe what loginserver to connect to.
### --- do not add an account and password unless a EQEmu Dev member has created an account for you.
### --- adding an account and password only grants the server a green name and is not needed.

### --- Public Login is un-supported as is LAN playing. We reccomend using the EQEmu.org Loginserver ALWAYS.


### --- NOTE: Starting 6-1-2002, you can no longer use the word "Server" in worldname.
### --- NOTE2: the word "Server" is added to each server automaticly

# READ README.TXT

[LoginServer]
loginserver=eqlogin1.eqemu.org
loginserver2=eqlogin2.eqemu.org
loginport=5999
loginport2=5999
worldname=Brisk
locked=false
account=
password=
worldaddress=65.186.10.101

[LoginConfig]
ServerMode=Standalone
ServerPort=5999
UplinkAddress=
UplinkPort=
UplinkAccount=
UplinkPassword=

Anything else you guys need?

That error is coming from the database lookup. Did you load the
db.sql file into mysql?

Yeah, perhaps the file is corrupt?

By loading I assume you mean the "source db.sql" at the MySQL dos prompt. Then yes, I did.

Just on a lark, try to reload it..

if you put db.sql in the mysql/bin directory, do this..

command prompt
cd c:/mysql/bin
mysql
> drop database eq;
> create database eq;
> source db.sql
> exit

Then , try to restart your world server and see if it makes a difference. Also, make sure you are using the db.sql version that came with the new emu version you downloaded.

Just a suggestion.

Think I figured it out.

I waited like 15 minutes for all that Query stuff to finish, and it worked.

I thought maybe the mass Query spam was a glitch or something so I had always cancelled it before it was done.

The latest release does not include a new version of zone9x, because the devs do not have a 9x system to test on. Not to mention them taking a break. Out of luck.

It will complain alot if you have a current database in there, you need to drop the existing one before putting the new one in...

Yea, cancelling out was your problem...