Is anyone running MySQL Server version 4.0.18?

[mikenune]

The past couple of days I've been trying to get my own copy of 0.5.7-DR2 running with no success (http://www.eqemulator.net/forums/viewtopic.php?t=14552). Well last night I finally decided to give up and go back to 0.5.6 which I know works. And, because I had done so many different things to my DB and INI files trying to get 0.5.7-DR2 working, I decided to just wipe everything and start from scratch.

So, first things I did were drop my eq DB and delete the user I had created with access to it (my 'equser' user).

Then I deleted everything in my \EQEMu folder.

Then I stopped and restarted my MySQL service (I'm running mysqld-max-nt version 4.0.18) just to be sure.

Then I downloaded a fresh copy of the 0.5.6 Binaries and Configurations from SourceFORGE and set them up, downloaded MiniLogin.exe and created a MiniLoginAccounts.ini with my 'eqemu' and 'mikenune' users in it, and downloaded and sourced my DB (eqemu056.zip).

Then I added back my 'equser' DB user and granted him all rights + grant to the eq DB and created my two MiniLogin accounts ('eqemu', and 'mikenune') in the account table.

Finally, I changed my eqhost.txt file and started up EQ.

Everything was working wonderfully! I was able to connect to my MiniLogin server and see my World Server in the list! I was able to connect to my World Server and get to my character creation screen! But then tragedy struck!

I had created my character, assigned attribute points, and selected starting city and deity when it happened.

What happened you ask?

IT happened!

World.exe crashed! Completely! The window closed by itself and the little Microsoft popup asking me if I wanted to send the details of the crash to Bill Gates appeared!

Frustrated (and a little miffed I might add), I started the Debugger instead. Lo and behold, the World Server had crashed at EXACTLY the same point as 0.5.7-DR2 had always crashed!

So, I started thinking to myself "What else on my computer has changed?"

The answer? MySQL.

The same day that I had started working with EQEMu 0.5.7-DR2, I had been forced to "upgrade" my MySQL server from 4.0.16 to 4.0.18 so I could get the files needed by Visual Studio to properly compile the new version of EQEMu!

So, today I am asking if anybody else here has MySQL version 4.0.18 installed on their system. And, if you do, do you also have a working copy (any version) of EQEMu running?

It is my sneaky suspicion that somewhere along the line from .16 to .18, MySQL changed how their function works or how it returns data back to the calling program! :(

[Derision]

Yes, I am using version 4.0.18, albeit it under Linux.

[Jezebell]

I have always been running 4.0.18, running it in Win2003 Server right now.

[gthang187]

i too am running it on windows 2000. i got it to work just fine atleast as far as i can see this stupid no character createing wont let me test it completely.

so i haveta wait till the devs fix it or someone can send me a sql file that has a character already created on it :( im still trying to figure out how to make a char useing mysql but i have had no luck as of yet :(

[masteryoda]

I am also running mysql 4.0.18 under WinXP. No problems so far.

[mikenune]

masteryoda, you're on Windows XP and have MySQL version 4.0.18 right? Do you have an EQEMu server up and running? Can you create characters on it and log in???

[masteryoda]

Correct, it is up right now and yes I can create and log in. Sending ya a PM

[NarutoLegacy]

Originally Posted by masteryoda

I am also running mysql 4.0.18 under WinXP. No problems so far.

Same, try downgrading if you think there is something bugged.

[Richardo]

I think downgrading would fix you up

[mikenune]

Dangit! That means I have to go all the way down to 3.2.23!!! :evil:

Oh, well. I'll give it a try.

[bUsh]

Do this:

drop table start_zones;

CREATE TABLE start_zones (
  x float NOT NULL default '0',
  y float NOT NULL default '0',
  z float NOT NULL default '0',
  zone_id int(4) NOT NULL default '0',
  bind_id int(4) NOT NULL default '0',
  player_choice int(2) NOT NULL default '0',
  player_class int(2) NOT NULL default '0',
  player_deity int(4) NOT NULL default '0',
  player_race int(4) NOT NULL default '0',
  start_zone int(4) NOT NULL default '0',
  bind_x float NOT NULL default '0',
  bind_y float NOT NULL default '0',
  bind_z float NOT NULL default '0',
  select_rank tinyint(3) unsigned NOT NULL default '50'
) TYPE=MyISAM;

No more crashes.

[mikenune]

Originally Posted by bUsh

Do this:

drop table start_zones;

CREATE TABLE start_zones (
  x float NOT NULL default '0',
  y float NOT NULL default '0',
  z float NOT NULL default '0',
  zone_id int(4) NOT NULL default '0',
  bind_id int(4) NOT NULL default '0',
  player_choice int(2) NOT NULL default '0',
  player_class int(2) NOT NULL default '0',
  player_deity int(4) NOT NULL default '0',
  player_race int(4) NOT NULL default '0',
  start_zone int(4) NOT NULL default '0',
  bind_x float NOT NULL default '0',
  bind_y float NOT NULL default '0',
  bind_z float NOT NULL default '0',
  select_rank tinyint(3) unsigned NOT NULL default '50'
) TYPE=MyISAM;

No more crashes.

Just for the record. . .






















I F***ING HATE YOU!!!!!!






















Oh, that worked BTW. Thanks.