COMPLETE PUBLIC SERVER SETUP - Jan-2011

[pepsiphreak79]

Originally Posted by lerxst2112

It sounds like you did not source your database correctly. Steps 14 and 15 in the guide.

No crap that makes no since to me i dont know how do do it and when i try the walk through it messes up

[pepsiphreak79]

Originally Posted by joligario

You're already out of date. CD uploaded a new database (2083). Get that one. Drop everything, source players and source system.

and that does no good if you dont include where to get it if you couldnt tell stuff scattered all over

And again im not a programmer or hacker i dont know what half the crap they say to do is..

The whole sorcing thing makes no sence

[pepsiphreak79]

And the things sorcing sais to do i cant do it that way im not setup like thoes people im instead using heidisql and choosing import sql


I am gonna try this uniserv with the perl 5.10 addon its a portable that way i can bag it up and move it around if needed
http://www.uniformserver.com/
i got perl from a google search on ActivePerl-5.10.1.1008-MSWin32-x86-294165.msi
and it installed into the uniserv

and i set SET PATH=C:\eqemu\UniServer\usr\local\mysql\bin;C:\eqe mu\UniServer\usr\bin;C:\eqemu\Core;%PATH%

into the cores bat file for start to find the required dll files on load right now its just re importing to the new blank database

ps ActivePerl-5.10.1.1008-MSWin32-x86-294165.msi is no longer obtainable through legal means free..... now you must be a paying cust on there site for it..

no clue why but you have to be a business or enterprise subscriber to obtain there older support for now its at 5.14 as the free release



And yes if i can get this up with SOF playable "races and zones and all possible Eq like quests" I will zip it up and put it around media sharings and torrent for all to use as an ungimped un customized Eqemu server easy to use with maps and all in it.. for non dev literate people like me..
If someone has an up to date DB and pre compiled un customized bots supported recient core that would help alot also i tried compiling and it gave me fatal errors and missing files and such and i followed the walkthroughs


Afterall isnt all this sopposed to be open sorce and a community project to keep improving it together as a group?


Plus think of all the quest writers that will come back to the project if it stays simple to use and upgrade. I do love how quests are kept to .pl and db and not hard coded like the wow ones

[lerxst2112]

All I can say is those instructions are fairly simple and easy to follow. You can use the mysql command line tool just like everyone else, you are just choosing not to, and what you're doing isn't working.

I would advise instead of just saying you can't do it, take a deep breath, and follow the simple steps in order without trying to take any shortcuts along the way. You will end up with a working server if you do that.

[pepsiphreak79]

ok again im not using a mysql installed to windows or the rest its all a portable i dont have the peqdb dir for exabmple so i dont have a clue how to do that sorce command shouldnt importing the SQL through heidi sql to the peq DB work the same way
Theres more than one way to skin a vashir

So unless you actually understand it yourself your not really able to help others.
helping others by saying stick to the tutorial really helps nobody it just aggravates them

i want this so that once its up and running i can have a complete server backup that can be just unziped and ran when im done i also run a wow server and so i want the databases ect... all seperate currently the wow server is on another pc up and running with no issues i did have a repack up for eq but again it was gimped and cudtomized and trying to upgrade it was useless so i am trying to start a fresh one
The instructions are simple to follow IF you know what all this stuff means and does and IF you want to setup a server how they have

[lerxst2112]

My server works perfectly since I followed a guide very similar to this one. I didn't know how MySQL worked or what sourcing files was when I started, but by reading and following the instructions I worked it out.

Lashing out at everyone that has tried to help you really isn't going to make them or anyone else want to try and help you. You might consider being polite and rational about it since you're the one that needs help, not me.

Yes, this guide is not the only way to setup a server, but this way has worked for many people and it could work for you too. Perhaps if you follow this guide to setup a non-portable server you will be able to take that experience and be able to figure out how to make the portable server you want.

Good luck.

[pepsiphreak79]

Again not helpfull at all

So i was able to find the peq datadir ill attempt this sorcing thing If anyone else has issues because there not setup the same your dirs for the sql may be located in \mysql\data\peq
and not in the c:\peqdb dir as some may have it no offense to the writer of the first page walkthrough its great you did that

mine happens to be
C:\eqemu\UniServer\usr\local\mysql\data\peq

Now i am starting with a naked Database
i have the standard structure of
DB information_schema - Standard mysql initial stuff unsure if anything needs altering
DB login - utf8 - bin Completly naked i assume i needed it so i created it
DB mysql - filled with the standard stuff for all my sql
DB peq - utf8 - bin format and completly empty (completly empty mind u)
DB performance_schema - again standard sql stuff
DB phpmyadmin - Standard stuff again and not relivant to eqemu

i went to the peq dir i did sorce it started importing and a bunch of errors like



Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`ground_spawns`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.ground_spawns' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

in that order and alot more than that but it wont save that far up in the cmd window

i checked back and they really were missing after the import so what thats telling me is the .SQL file is telling mysql to create if not there before its telling mysql to delete it

so this whole time its not my importing through heidisql its the SQL itsself that is not working correctly

Its creating the table thats missing then deleting it then its unable to run the insert commands because the table is missing...

i appear to have a bad SQL db as i assumed... is there a 2068 DB around anywhere that is uncustomized? since the 2027 db im using is not allowing a full source

I did not run any updates because the initial sourcing failed and alot of stuff is not included anyway

what i came out with is a peqdb that was missing some tables
and not sure how to pupulate the login db so i will just copy another one into that one

i found the 2083 i will clear and try that one instead
http://code.google.com/p/projecteqdb/downloads/list
is where the 2083 db is

[pepsiphreak79]

same thing with rev 2083 db


ERROR 1146 (42S02): Table 'peq.faction_list' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`fear_hints`' already exists
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`fishing`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.fishing' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`forage`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.forage' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.05 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 501 rows affected (0.01 sec)
Records: 501 Duplicates: 0 Warnings: 0

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`graveyard`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.graveyard' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`grid`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.grid' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`grid_entries`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist
ERROR 1146 (42S02): Table 'peq.grid_entries' doesn't exist




Query OK, 48964 rows affected (0.31 sec)
Records: 48964 Duplicates: 0 Warnings: 0

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`spawn2`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.spawn2' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawn2' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawn2' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawn2' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawn2' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawn2' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawn2' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawn2' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawn2' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawn2' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawn2' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawn2' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`spawn_conditions`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.spawn_conditions' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`spawn_condition_values`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.spawn_condition_values' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`spawn_events`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.spawn_events' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`spawnentry`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.spawnentry' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawnentry' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawnentry' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`spawngroup`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.spawngroup' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawngroup' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawngroup' doesn't exist
ERROR 1146 (42S02): Table 'peq.spawngroup' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.14 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 1599 rows affected (0.22 sec)
Records: 1599 Duplicates: 0 Warnings: 0

Query OK, 1595 rows affected (0.22 sec)
Records: 1595 Duplicates: 0 Warnings: 0

Query OK, 1604 rows affected (0.22 sec)
Records: 1604 Duplicates: 0 Warnings: 0

Query OK, 1621 rows affected (0.20 sec)
Records: 1621 Duplicates: 0 Warnings: 0

Query OK, 1605 rows affected (0.22 sec)
Records: 1605 Duplicates: 0 Warnings: 0

Query OK, 1590 rows affected (0.20 sec)
Records: 1590 Duplicates: 0 Warnings: 0

Query OK, 1536 rows affected (0.20 sec)
Records: 1536 Duplicates: 0 Warnings: 0

Query OK, 1575 rows affected (0.20 sec)
Records: 1575 Duplicates: 0 Warnings: 0

Query OK, 1610 rows affected (0.20 sec)
Records: 1610 Duplicates: 0 Warnings: 0

Query OK, 1696 rows affected (0.20 sec)
Records: 1696 Duplicates: 0 Warnings: 0

Query OK, 1576 rows affected (0.22 sec)
Records: 1576 Duplicates: 0 Warnings: 0

Query OK, 1552 rows affected (0.20 sec)
Records: 1552 Duplicates: 0 Warnings: 0

Query OK, 1598 rows affected (0.20 sec)
Records: 1598 Duplicates: 0 Warnings: 0

Query OK, 1620 rows affected (0.20 sec)
Records: 1620 Duplicates: 0 Warnings: 0

Query OK, 1574 rows affected (0.20 sec)
Records: 1574 Duplicates: 0 Warnings: 0

Query OK, 1602 rows affected (0.20 sec)
Records: 1602 Duplicates: 0 Warnings: 0

Query OK, 1529 rows affected (0.20 sec)
Records: 1529 Duplicates: 0 Warnings: 0

Query OK, 1193 rows affected (0.16 sec)
Records: 1193 Duplicates: 0 Warnings: 0

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`start_zones`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.start_zones' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`starting_items`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.starting_items' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 113 rows affected (0.00 sec)
Records: 113 Duplicates: 0 Warnings: 0

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 14 rows affected (0.00 sec)
Records: 14 Duplicates: 0 Warnings: 0

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.14 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 172 rows affected (0.00 sec)
Records: 172 Duplicates: 0 Warnings: 0

Query OK, 0 rows affected (0.02 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`tradeskill_recipe`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.tradeskill_recipe' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.19 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 38390 rows affected (0.33 sec)
Records: 38390 Duplicates: 0 Warnings: 0

Query OK, 37874 rows affected (0.55 sec)
Records: 37874 Duplicates: 0 Warnings: 0

Query OK, 27620 rows affected (0.38 sec)
Records: 27620 Duplicates: 0 Warnings: 0

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`traps`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.traps' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`tribute_levels`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.tribute_levels' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`tributes`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.tributes' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`zone`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.zone' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`zone_points`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.zone_points' doesn't exist
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`zone_server`' already exists
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`zone_state_dump`' already exists
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)

ERROR 1050 (42S01): Table '`peq`.`zoneserver_auth`' already exists
Query OK, 0 rows affected (0.00 sec)

ERROR 1146 (42S02): Table 'peq.zoneserver_auth' doesn't exist
mysql>


same kind of errors and missing tables at completion
its checking for them and creating them then deleting them then trying to populate

or is it " eq`.`fo "vs " eq.fo " i see that its having errors with ones like that

[trevius]

As has already been said, your attitude is not likely to get you much assistance with your issues. The community is often likely to help people when they can, but no one is getting paid to do so, so being rude is more likely to result in no responses. You have started off rude in this thread and every post since then has followed that same overall feeling.

Regardless of what you may think, lerxst2112 is one of the more active, more knowledgeable and more helpful people in the EQEmu community right now. You are working against yourself to be rude to him like that. I won't tolerate disrespect to top notch community members, so please stop it.

First of all, from all of your posts, it looks like you are not following the guide exactly. You are trying to take short cuts or use other tools/procedures you have used for setting up your WoW emu server. If you knew exactly what you were doing and if you were able to get your server setup by doing things differently than the guide says, then that would be good. Unfortunately, that isn't working out so well for you. My suggestion would be to follow the guide exactly. If you can get the server working by following the guide exactly, then you can start doing your other stuff.

Yes, the EQEmu guides could probably be made better. Part of the problem is that there are many different Operating Systems that can run EQEmu and setting it up on each one can be slightly different. So, it does require a bit of knowledge here and there and is not for everyone out there. Though, there have been hundreds of servers created over the years using similar guides, so it isn't as hard as you make it out to be.

If you are having this much trouble just getting the server running, you are really probably going to have a hard time getting your Login Server or MiniLogin working. Both of those can be kinda tough to get working initially without a little bit of knowledge on what you need to do. The guides help, but many people have issues with it. Getting a public server running that uses the public EQEmu Login Server is much easier and most people do it that way for that reason.

Your posts on the issue seem to be all over the place. You mentioned AX classic repack, and that isn't supported here. You might try their website to see if there is better info there for it. From what I have heard of it, that is about as easy as it gets.

Your problems could be any number of things, and you may not even have the right versions of perl or mysql installed, which is only going to add to your issues.

Good luck with getting it all running. If the negative attitude keeps up, you will be temp banned to let you hopefully cool off.

[pepsiphreak79]

im not trying to be rude just frustrating that some of the peopel really arent trying to help there just being negative saying your doing it wrong or refer to the walk through but they are not acually helping i did thank the one that acually offered some help ... and they act like we have all been here for ages ans should already know all this...
its kinda condasending and thats why i was negative

[trevius]

In a previous post in this thread, you said you were able to source all of the PEQ SQL without errors, but now you are getting errors when you try?

Are you following these 3 step exactly (accounting for the path difference where your PEQ files are located)?

13.First, go to your C-Drive and right click on the folder you made called peqdb
and choose "SVN Checkout"
In the "URL of repository" line copy and paste the following:
http://projecteqdb.googlecode.com/svn/trunk/peqdatabase (then click OK)
It will finish with "At Revision XX"

Next, go to that folder peqdb and unzip the file from peqdb_rev1751.sql.gz
to the same peqdb folder.
This file will be named peqdb_rev1751.sql (without the .gz)

***NOTE***
The "rev1751" was the most current at the time of this writing. It may change over time.

14. Ok, now open up your Navicat Lite program that you installed.
On the upper left you will see Connection. Click on that and choose MySQL
A connection window will open. The only thing you really need to do is put your mysql
password in (make sure the "Save Password" is checked) and click OK.
This will create a connection with MySQL.
In the Connections window, you should now see localhost_3306 (Double click on that)
Then right click on that same name (localhost_3306) and choose New Database...
In the next window, in the first line, type peq (then click OK)
Close Navicat Lite.

15. NOW, you need to go in to a command prompt and navigate to the peqdb folder.
Simply type cd \peqdb and you should be there. You will see: C:\peqdb>_

REMEMBER THE PASSWORD YOU GAVE when you set up MySQL ? (You need it NOW)

***WARNING*** - at this point, make sure you are in the peqdb folder.

Type mysql -uroot -p
Hit enter and enter your password. (Hit enter again)
You should now see a prompt that looks like this: (along with "Welcome" text before it)
mysql>_

Type the following (in order):

use peq (Hit enter and you will see a short note saying "Database changed")

Then type the following:

source peqdb_rev1751.sql (when this is done, you will be back at the mysql>_ prompt)

Then type in the following:

source load_player.sql (this will load fast)

***WARNING*** - When you compiled your server, if you chose "ReleaseBots", you will now
need to type the following at the mysql prompt:

source load_bots.sql

Which ever you chose, you can now close the command window and work on the sql updates.

***WARNING*** - the sql updates ARE NOT in the peqdb folder, they are in the source
folder where you compiled your server, but you can use Navicat Lite to run the updates.

If you follow those 3 steps, your DB should be all set and you can move on to troubleshooting your next issue(s). If you are unable to understand exactly what to do at any part of those 3 steps, just ask specifically about the part you are unsure about.

If you don't know how to open a command prompt, you can do all of this fairly easily through Navicat and probably HeidiSQL as well. I don't use HeidiSQL, so I can't speak for how to do it there, but Navicat is similar I am sure and very simple. You just create a new database named "peq" (without the quotes). Then you double click that database to connect to it and right click on it. In that menu, you should see an option to Source the SQL (may not be worded exactly like that, but I am not at my desktop to verify right now). You then browse to the folder where your PEQ SQL files are located and run them in the order that the guide says to.

[lerxst2112]

Looks like Trevius beat me to the punch, but maybe this will help anyway.

You can do everything you need to from the command prompt and not have to worry about using a different tool to create the database. I remember when I originally tried to use SQLyog to source load_player.sql it failed because it doesn't set the current directory to where the file you're importing is so it couldn't find the player_tables directory.

I also show deleting the existing database just to be sure you are starting from scratch. It sounds like, from the issues you posted, that you may have had something leftover there causing a conflict.

Substitute whatever directory you have the peq files in for the first command. The blue text is what I typed. I didn't include all of the spam the source commands generate because it wouldn't be helpful. If you want to save all of the output to a file you can type tee output.txt as the first command at the mysql> prompt. The file will be saved in the directory you started MySQL from.

If you are not using bots then skip the source load_bots.sql command.

C:\>cd EQEmu\Database\peqdatabase

C:\EQEmu\Database\peqdatabase>dir
 Volume in drive C has no label.
 Volume Serial Number is 4A57-06FC

 Directory of C:\EQEmu\Database\peqdatabase

12/06/2011  03:11 AM    <DIR>          .
12/06/2011  03:11 AM    <DIR>          ..
10/04/2010  10:20 PM               564 drop_bots.sql
12/05/2011  07:55 PM             2,566 drop_player.sql
12/05/2011  07:55 PM             2,752 drop_system.sql
10/04/2010  10:20 PM               276 load_bots.sql
12/05/2011  07:55 PM             2,659 load_player.sql
12/05/2011  02:02 AM       169,453,496 peqdb_rev2083.sql
12/05/2011  07:55 PM        22,451,506 peqdb_rev2083.sql.gz
12/05/2011  07:55 PM    <DIR>          player_tables
10/04/2010  10:20 PM             1,586 readme.txt
12/05/2011  07:55 PM    <DIR>          updates
               8 File(s)    191,915,405 bytes
               4 Dir(s)  495,992,610,816 bytes free

C:\EQEmu\Database\peqdatabase>mysql -uroot -p
Enter password: *****
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 9
Server version: 5.0.91-community-nt MySQL Community Edition (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> drop database peq;
Query OK, 151 rows affected (2.15 sec)

mysql> create database peq;
Query OK, 1 row affected (0.00 sec)

mysql> use peq
Database changed

mysql> source peqdb_rev2083.sql
mysql> source load_player.sql
mysql> source load_bots.sql
mysql> quit

[pepsiphreak79]

yes i was using an ax repack and its still in another dir and working if i shut mine off and turn it on but its not working how i want a server to if that explains anything...

My first attempt was so use there portable mysql ect... since it was all ready to go with eqemu but each attempt failed

I have switched to a but naked uniserv
Apache 2.2.21
MySQL 5.5.18-community
PHP 5.3.8
perl 5.10

15. NOW, you need to go in to a command prompt and navigate to the peqdb folder.
Simply type cd \peqdb and you should be there. You will see: C:\peqdb>_

I believe this part was what had me from my understanding of what was written in tutorial was that this was to be the db stored files and so to copy your newly downloaded sql to it but since my portable doesnt work like others stuff it was my issue
i was copying the sql to the peq dir from the mysql and it looks like that was what botched it.... and yes up above i said thats what i did so instead i just resourced and i stoped getting the frustrating errors i still have no clue why it errord with the sql file in the db dir but oh well thats beyond my understanding. i got past it. just now

so im going to try the rest off the installs

is it ok to populate my naked login database using the login DB from a repack??

[pepsiphreak79]

and i just saw your posts lol thank you

[pepsiphreak79]

This is unclear especially since the rev is now 2027 on the db does this mean i need to install update from the 1667 till 2068 line still or is the 2068 db updated? i am afraid to screw it up again so im just going to ask for clarification first.

The reason your doing this, is because, even after a new database revision is out, all
the updates developed after that, need to be sourced in. In this case, when the rev1751
was sent out, (after the 1667), not all updates were applied to the release.
I know it leaves more work for us "end users", but what the heck, it's free