Sorry if this has been asked and answered. I tried searching for "cfg" but it's not 4 characters long and the search feature of this forum doesn't allow < 4 char. long searches.. But this is what I get when I try zoneing into my server.
World Server Error Log
2263260 New client from ip: 127.0.0.1 port: 2821
Logged in: Local: eqemu
Guild Send Request...
Sending character information.
Unknown opcode: 0x3541 size:2056
Unknown opcode: 0x3941 size:2056
Maxclients: 4
Attempting autobootup of 'akanon' for -CharacterName-
Error: No zoneserver to bootup 'akanon' for -CharacterName-
Zone Server Error Log
Using default zone header data...
Petition 0 pettime = 0
-----------
Zone server '7' listening on port:7995
-----------
Automatic shutdown
Message:----SERVER SHUTDOWN----
Zone shutdown: going to sleep
Zone bootup by *eqemu
Map: Maps\7.map not found.
ZoneID = 0
Couldn't find/read ./cfg/7.cfg. (returning -1)
Couldn't find/read ./cfg/.cfg. (returning -1)
Corrupt (or nonexistant) zhdr file ./cfg/.cfg -- fread count = -1 (should be 170
)
Using default zone header data...
Petition 0 pettime = 0
-----------
Zone server '7' listening on port:7995
-----------
Automatic shutdown
Message:----SERVER SHUTDOWN----
Zone shutdown: going to sleep
Now granted it scrolled off screen from many attemps, so I can't figure out where it acctually started.. Now I acctually unpacked the zip using folder names so all the files should be in their proper places..
Lemme rewind and backup a lil and start off by saying prior to this incident I was unable to create new characters (it would boot me back to char. sel. screen and never auth my name and create my char.). So I patched to eqlive. Patching to eqlive yields this result.. So after some digging I found I did have some cfg files in the (I'll just use the pathname to make it easier) f:\Program Files\Sony\Everquest Trilogy\ directory as well as in f:\Program Files\Sony\Everquest Trilogy\cfg so what I did was I dumped the cfg files in the Tilogy directory, re-unpacked the cfg files from the zip overtop of the cfg files in the cfg directoyr just to make absolutely certain I was using correct zone config files.
Now one thing I did notice that was kinda weird was when I created the database (which I always do upon new release) for the 0311 ver. and I sourced the db.sql file I was getitng something like 0 rows affected not 1 row affected (that I usually get)... if I were sourcing the db.sql into a freshly empty created db it should have given me tons of 1 row affected instead of the 0 row affected.. Maybe I just answered my own question?
Anyhow, perservering (sp?) while inside the game I tried linking the sql db through an access table, up came the tables. I opened up 'zones' modified akanon (as I created a gnome, GNOME POWAH!

) and I tried pointing the filename to akanon.map, it wouldn't save right.. so I loaded up eqadmin this time and tried it again ok it saved.. Tried akanon.map and akanon.cfg nothing worked still same error.. Then I had a pretty good idea.. I remember a while back having to fight with zone id's ingame to bootup and shutdown zones because zoning was as 'perfected' as it is now.. so remembering that I seen a no zoneserver to bootup 'akanon'
error I decided that I'd try a backend approach and telnet to port 9000.. (at the time Iwondered why the devs were making such a feature, now I'm damn glad they did, thanks guys

). So I got into my console.. I threw out some commands such as
'zonebootup 3 akanon'
'zonebootup 2 akanon'
'zonebootup 1 akanon'
now here's the weird thing, sometimes 3 2 or 1 wouldn't even budge almost as if they didn't even received a backend command.. However when they did respond I got the same results as I did when I tried logging in with a character. I was kinda banking on maybe the zoneserver wasn't decoding which zone to bootup as it says in the error message:
Map: Maps\7.map not found.
ZoneID = 0
Couldn't find/read ./cfg/7.cfg. (returning -1)
Couldn't find/read ./cfg/.cfg. (returning -1)
so that's why I tried loading the zone manually and then attempting to enter the world, but that didn't work either.. Is this a packet decoding problem? Like did I patch one hour too late after the news post and received a patch version newer to what the 0311 was designed for? Any help would be greatly appreciate. Thanks
-- StakFallT