Go Back   EQEmulator Home > EQEmulator Forums > Support > Support::Windows Servers

Support::Windows Servers Support forum for Windows EQEMu users.

Reply
 
Thread Tools Display Modes
  #1  
Old 06-19-2006, 11:04 AM
mplostcause
Fire Beetle
 
Join Date: Jun 2006
Posts: 13
Default Server problems

I just recently started working with creating emulated servers. I have been trying to make a LAN based one just to play with friends and have been running into a few problems.

With a fresh installed 0.7.0 server files and having both cavedude and peq databases sourced I was able to log into the server and create a characater and join the server (I used the wiki guide to setting up a windows 0.7.0 guide). After I logged off and when I attempted to log back into the server the world.exe continually crashes right after selecting the server in the server select screen.

I decided to update the files to the newest build currently available on the downloads page I copied and pasted the files into the eqemu folder, I did not re-source the databases. I also added the following to the database because of what i had read on these forums:
ALTER TABLE spawnentry DROP spawn_limit;
ALTER TABLE spawngroup ADD spawn_limit tinyint(4) NOT NULL default '0';
ALTER TABLE altadv_vars ADD class_type int unsigned NOT NULL DEFAULT 0;
After making these changes I was able to get past the server select screen and load the character select but when trying to enter the world at the character select screen I keep getting the message that the zone is unavailable. I have read all over these forums and wiki trying to find a possible resolution and haven't been able to. I made a new character and attempted to connect to world in these logs:
Quote:
[06.19. - 18:38:13] [WORLD__LAUNCH] Launcher Identified itself as 'zones'. Loading zone list.
[06.19. - 18:38:13] [WORLD__LAUNCH] Removing pending launcher 1. Adding zones to active list.
[06.19. - 18:38:19] [WORLD__LAUNCH] zones: dynamic_01 reported state STARTED (1 starts)
[06.19. - 18:38:40] [WORLD__LAUNCH] zones: dynamic_02 reported state STARTED (1 starts)
[06.19. - 18:38:42] [WORLD__LAUNCH] zones: dynamic_03 reported state STARTED (1 starts)
[06.19. - 18:38:44] [WORLD__LAUNCH] zones: dynamic_04 reported state STARTED (1 starts)
[06.19. - 18:38:46] [WORLD__LAUNCH] zones: dynamic_05 reported state STARTED (1 starts)
[06.19. - 18:39:41] [WORLD__ZONE] New TCP connection from 127.0.0.1:1199
[06.19. - 18:39:41] [WORLD__ZONE] New TCP connection from 127.0.0.1:1200
[06.19. - 18:39:41] [WORLD__ZONE] New TCP connection from 127.0.0.1:1201
[06.19. - 18:39:41] [WORLD__ZONE] New TCP connection from 127.0.0.1:1202
[06.19. - 18:39:41] [WORLD__ZONE] New TCP connection from 127.0.0.1:1203
[06.19. - 18:39:41] [WORLD__CONSOLE] New zoneserver #1 from 127.0.0.1:1200
[06.19. - 18:39:41] [WORLD__CONSOLE] New zoneserver #2 from 127.0.0.1:1199
[06.19. - 18:39:41] [WORLD__CONSOLE] New zoneserver #3 from 127.0.0.1:1203
[06.19. - 18:39:41] [WORLD__CONSOLE] New zoneserver #4 from 127.0.0.1:1202
[06.19. - 18:39:41] [WORLD__CONSOLE] New zoneserver #5 from 127.0.0.1:1201
[06.19. - 18:39:41] [WORLD__ZONE] [5] Zone started with name dynamic_01 by launcher zones
[06.19. - 18:39:41] [WORLD__ZONE] [5] Auto zone port configuration. Telling zone to use port 7000
[06.19. - 18:39:41] [WORLD__ZONE] [4] Zone started with name dynamic_02 by launcher zones
[06.19. - 18:39:41] [WORLD__ZONE] [4] Auto zone port configuration. Telling zone to use port 7001
[06.19. - 18:39:41] [WORLD__ZONE] [3] Zone started with name dynamic_03 by launcher zones
[06.19. - 18:39:41] [WORLD__ZONE] [3] Auto zone port configuration. Telling zone to use port 7002
[06.19. - 18:39:41] [WORLD__ZONE] [2] Zone started with name dynamic_04 by launcher zones
[06.19. - 18:39:41] [WORLD__ZONE] [2] Auto zone port configuration. Telling zone to use port 7003
[06.19. - 18:39:41] [WORLD__ZONE] [1] Zone started with name dynamic_05 by launcher zones
[06.19. - 18:39:41] [WORLD__ZONE] [1] Auto zone port configuration. Telling zone to use port 7004
[06.19. - 18:40:33] [WORLD__CLIENT] New connection from 127.0.0.1:1205
[06.19. - 18:40:33] [NET__IDENT_TRACE] 127.0.0.1:1205: First opcode 0x4dd0 did not match expected 0x2792
[06.19. - 18:40:33] [NET__IDENT_TRACE] 127.0.0.1:1205: Tried patch 6.2_world, and it did not match.
[06.19. - 18:40:33] [NET__IDENT_TRACE] 127.0.0.1:1205: First opcode 0x4dd0 did not match expected 0x2ec9
[06.19. - 18:40:33] [NET__IDENT_TRACE] 127.0.0.1:1205: Tried patch 6.2_zone, and it did not match.
[06.19. - 18:40:33] [NET__IDENT_TRACE] 127.0.0.1:1205: First opcode matched 0x4dd0 and length matched 464
[06.19. - 18:40:33] [NET__IDENTIFY] Identified stream 127.0.0.1:1205 with signature Titanium_world
[06.19. - 18:40:33] [WORLD__CLIENT] New client from 127.0.0.1:1205
[06.19. - 18:40:33] [WORLD__CLIENT_TRACE] NOCLE: Recevied EQApplicationPacket
[06.19. - 18:40:33] [WORLD__CLIENT] mini: Logged in. Mode=(CharSel)
Reply With Quote
  #2  
Old 06-19-2006, 11:04 AM
mplostcause
Fire Beetle
 
Join Date: Jun 2006
Posts: 13
Default

Quote:
[06.19. - 18:47:21] [WORLD__CLIENT] mini: Current location: felwithea -301.00, 0.00, 4.00
[06.19. - 18:47:21] [WORLD__CLIENT] mini: Bind location: felwithea -301.00, 0.00, 4.00
[06.19. - 18:47:22] [WORLD__CLIENT] mini: Character creation successful: Skide
[06.19. - 18:47:22] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00ff
[06.19. - 18:47:23] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:47:23] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:47:26] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:47:26] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00fc
[06.19. - 18:47:26] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010a
[06.19. - 18:47:26] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010b
[06.19. - 18:47:26] [WORLD__CLIENT] mini: Attempting autobootup of felwithea (61)
[06.19. - 18:47:34] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00c7
[06.19. - 18:47:35] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:48:21] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:48:21] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00fc
[06.19. - 18:48:21] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010a
[06.19. - 18:48:21] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010b
[06.19. - 18:48:21] [WORLD__CLIENT] mini: Attempting autobootup of felwithea (61)
[06.19. - 18:48:21] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00c7
[06.19. - 18:48:21] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:48:26] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:48:26] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00fc
[06.19. - 18:48:26] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010a
[06.19. - 18:48:26] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010b
[06.19. - 18:48:26] [WORLD__CLIENT] mini: Attempting autobootup of felwithea (61)
[06.19. - 18:48:26] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00c7
[06.19. - 18:48:26] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:48:32] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:48:32] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00fc
[06.19. - 18:48:32] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010a
[06.19. - 18:48:32] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010b
[06.19. - 18:48:32] [WORLD__CLIENT] mini: Attempting autobootup of felwithea (61)
[06.19. - 18:48:33] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00c7
[06.19. - 18:48:33] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:48:37] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:48:37] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00fc
[06.19. - 18:48:37] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010a
[06.19. - 18:48:37] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010b
[06.19. - 18:48:37] [WORLD__CLIENT] mini: Attempting autobootup of felwithea (61)
[06.19. - 18:48:37] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00c7
[06.19. - 18:48:37] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:48:41] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:48:41] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00fc
[06.19. - 18:48:41] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010a
[06.19. - 18:48:41] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010b
[06.19. - 18:48:41] [WORLD__CLIENT] mini: Attempting autobootup of felwithea (61)
[06.19. - 18:48:42] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00c7
[06.19. - 18:48:42] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:48:45] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:48:45] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00fc
[06.19. - 18:48:45] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010a
[06.19. - 18:48:45] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010b
[06.19. - 18:48:45] [WORLD__CLIENT] mini: Attempting autobootup of felwithea (61)
[06.19. - 18:48:46] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00c7
[06.19. - 18:48:46] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:49:11] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:49:11] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00fc
[06.19. - 18:49:11] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010a
[06.19. - 18:49:11] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010b
[06.19. - 18:49:11] [WORLD__CLIENT] mini: Attempting autobootup of felwithea (61)
[06.19. - 18:49:11] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00c7
[06.19. - 18:49:12] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:49:18] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:49:18] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00fc
[06.19. - 18:49:18] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010a
[06.19. - 18:49:18] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010b
[06.19. - 18:49:18] [WORLD__CLIENT] mini: Attempting autobootup of felwithea (61)
[06.19. - 18:49:19] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00c7
[06.19. - 18:49:19] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:49:23] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:49:23] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00fc
[06.19. - 18:49:23] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010a
[06.19. - 18:49:23] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010b
[06.19. - 18:49:23] [WORLD__CLIENT] mini: Attempting autobootup of felwithea (61)
[06.19. - 18:49:24] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00c7
[06.19. - 18:49:24] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:49:29] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:49:29] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00fc
[06.19. - 18:49:29] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010a
[06.19. - 18:49:29] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010b
[06.19. - 18:49:29] [WORLD__CLIENT] mini: Attempting autobootup of felwithea (61)
[06.19. - 18:49:29] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00c7
[06.19. - 18:49:30] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:49:34] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:49:34] [WORLD__CLIENT_ERR] mini: Received unknown EQApplicationPacket
[06.19. - 18:49:34] [WORLD__CLIENT_ERR] [OpCode OP_WorldLogout (0x771 Size=0]
[06.19. - 18:49:34] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 18:49:43] [WORLD__CLIENT] mini: Client disconnected (not active in process)
Excuse me for the quoted log if its too long, I am not sure exactly what information will be useful so I just want to encompass any possiblity. Thank you for help in advance and if anyone needs any more information or other logs I'll be glad to supply them.
Reply With Quote
  #3  
Old 06-19-2006, 11:43 AM
Angelox
AX Classic Developer
 
Join Date: May 2006
Location: filler
Posts: 2,049
Default

Make sure you didn't copy over your "eqemu_config.xml"
Reply With Quote
  #4  
Old 06-19-2006, 11:47 AM
mplostcause
Fire Beetle
 
Join Date: Jun 2006
Posts: 13
Default

I am not sure if this is what you are refeering to but when I first updated to the new build I found that when I tried to run the server it wouldnt show up in minilogin window so I naturally thought there was a problem with the eqemu_config so I tried again to update with the a fresh install of 0.7.0 and made a backup of that file copied and pasted the new build and then moved back in the backup verison of the eqemu_config
Reply With Quote
  #5  
Old 06-19-2006, 12:13 PM
EliteSting
Sarnak
 
Join Date: May 2005
Posts: 58
Default

Check this out , maybe close to the same problem.

http://www.eqemulator.net/forums/showthread.php?t=20790
Reply With Quote
  #6  
Old 06-19-2006, 02:34 PM
mplostcause
Fire Beetle
 
Join Date: Jun 2006
Posts: 13
Default

i did another fresh install of the server files and resourced the databases along with updating the build to most current available. I ran the following commands on the database after installing as outlined in the 0.7.0 windows server guide:
ALTER TABLE spawnentry DROP spawn_limit;
ALTER TABLE spawngroup ADD spawn_limit tinyint(4) NOT NULL default '0';
ALTER TABLE altadv_vars ADD class_type int unsigned NOT NULL DEFAULT 0;
ALTER TABLE spawn2 CHANGE `condition` `_condition` MEDIUMINT( UNSIGNED NOT NULL DEFAULT '0';

After doing this I am still having the same problem. I can connect to the server and create a character but when I go to enter world the screen turns black for a split second and goes directly back to character select with the message zone unavailable. If anyone else has any suggestions at possible fixs or logs/settings I can check to find possible problems/solutions. I appreciate the help suggestions so far and the work people have put into this project.
Reply With Quote
  #7  
Old 06-19-2006, 02:38 PM
Angelox
AX Classic Developer
 
Join Date: May 2006
Location: filler
Posts: 2,049
Default

Quote:
Originally Posted by mplostcause
i did another fresh install of the server files and resourced the databases along with updating the build to most current available. I ran the following commands on the database after installing as outlined in the 0.7.0 windows server guide:
ALTER TABLE spawnentry DROP spawn_limit;
ALTER TABLE spawngroup ADD spawn_limit tinyint(4) NOT NULL default '0';
ALTER TABLE altadv_vars ADD class_type int unsigned NOT NULL DEFAULT 0;
ALTER TABLE spawn2 CHANGE `condition` `_condition` MEDIUMINT( UNSIGNED NOT NULL DEFAULT '0';

After doing this I am still having the same problem. I can connect to the server and create a character but when I go to enter world the screen turns black for a split second and goes directly back to character select with the message zone unavailable. If anyone else has any suggestions at possible fixs or logs/settings I can check to find possible problems/solutions. I appreciate the help suggestions so far and the work people have put into this project.
Try this out;

http://www.eqemulator.net/forums/showthread.php?t=20778

see if it helps
edit;
It won't help - this is another problem and it may be related with the source lines you are entering.
Read backwards through the changelogs, make sure you applied all the lines needed to the database. also, make sure you are on the same database you are using for the EQ emulator- "status" commad will tell you where you're at, and "use" command will change you. Example: USE peq will set you to peq database.

Last edited by Angelox; 06-19-2006 at 10:46 PM.. Reason: Wrong Answer
Reply With Quote
  #8  
Old 06-19-2006, 03:28 PM
mplostcause
Fire Beetle
 
Join Date: Jun 2006
Posts: 13
Default

I went ahead and tried it before you edited that it won't work and as you said it didn't work =). I did notice a new error in the logs though when I tried to see if your possible fix worked.
Quote:
[06.19. - 22:16:11] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00ff
[06.19. - 22:16:11] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 22:16:11] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00fc
[06.19. - 22:16:11] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010a
[06.19. - 22:16:11] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010b
[06.19. - 22:16:11] [WORLD__CLIENT] mini: Attempting autobootup of gfaydark (54)
[06.19. - 22:16:13] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 22:16:14] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 22:16:15] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 22:16:15] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 22:16:19] [WORLD__CLIENT_ERR] mini: Zone bootup timer expired, bootup failed or too slow.
[06.19. - 22:16:19] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00c7
[06.19. - 22:16:22] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 22:16:27] [WORLD__CLIENT_TRACE] mini: Recevied EQApplicationPacket
[06.19. - 22:16:27] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x00fc
[06.19. - 22:16:27] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010a
[06.19. - 22:16:27] [WORLD__CLIENT_TRACE] mini: Sending EQApplicationPacket OpCode 0x010b
I am going through the changelogs right now to make sure I didn't miss stuff, thanks a lot for your support.

Last edited by mplostcause; 06-19-2006 at 11:32 PM..
Reply With Quote
  #9  
Old 06-20-2006, 05:33 AM
mplostcause
Fire Beetle
 
Join Date: Jun 2006
Posts: 13
Default

I went back into the changelogs and after the changes I mentioned it seemed that all of them have already been done, I didn't go all the way down the changelog to check everyone after about 20 lines that had already been done. I am still having the same problem and now I just feel like I am missing something completely stupid and small =P. I am beginning to think I'll just wait until a new build is released and try to do a fresh install and resource the databases with it.
Reply With Quote
  #10  
Old 06-20-2006, 05:49 AM
Angelox
AX Classic Developer
 
Join Date: May 2006
Location: filler
Posts: 2,049
Default

Quote:
Originally Posted by mplostcause
I went back into the changelogs and after the changes I mentioned it seemed that all of them have already been done, I didn't go all the way down the changelog to check everyone after about 20 lines that had already been done. I am still having the same problem and now I just feel like I am missing something completely stupid and small =P. I am beginning to think I'll just wait until a new build is released and try to do a fresh install and resource the databases with it.
Ok, so actually none of the builds are working now? Did you try an install from here, http://www.eqemulator.net/wiki/wikka...indowsServer70 , following the step-by step directions? (just making sure)
If so, what OS do you have - WindowsXP?, and what CPU are you using - Intel P3 or higher?
Reply With Quote
  #11  
Old 06-20-2006, 10:20 AM
mplostcause
Fire Beetle
 
Join Date: Jun 2006
Posts: 13
Default

I've only tried two builds, the 0.7.0 (I used the EQEmuServerPack-3.52 thats linked on the how to create a 0.7.0 windows server guide that you linked from wiki) and the latest build on the downloads page. With the fresh install of 0.7.0 I get the world.exe crashes when you select the server in the server select screen and when I updated to the newest build I get zone is unavaliable message all the time. What I am going to do is I am going to do a completely fresh install with just the outline of how you are suppose to do it using the http://www.eqemulator.net/wiki/wikka...indowsServer70 guide. After I do a completely fresh install with no changes to the database other than what the EQEmuServerPack-3.52 has it in and will try to work from there. The server I have up now I have changed numerous times over the last few days trying to get this worked out. As far as computer it is a Windows XP computer with SP2 with a P3 processor. I really appreciate the help you are giving me and hopefully I'll end up getting this thing working correctly =)
Reply With Quote
  #12  
Old 06-20-2006, 11:15 AM
Angelox
AX Classic Developer
 
Join Date: May 2006
Location: filler
Posts: 2,049
Default

Quote:
Originally Posted by mplostcause
I've only tried two builds, the 0.7.0 (I used the EQEmuServerPack-3.52 thats linked on the how to create a 0.7.0 windows server guide that you linked from wiki) and the latest build on the downloads page. With the fresh install of 0.7.0 I get the world.exe crashes when you select the server in the server select screen and when I updated to the newest build I get zone is unavaliable message all the time. What I am going to do is I am going to do a completely fresh install with just the outline of how you are suppose to do it using the http://www.eqemulator.net/wiki/wikka...indowsServer70 guide. After I do a completely fresh install with no changes to the database other than what the EQEmuServerPack-3.52 has it in and will try to work from there. The server I have up now I have changed numerous times over the last few days trying to get this worked out. As far as computer it is a Windows XP computer with SP2 with a P3 processor. I really appreciate the help you are giving me and hopefully I'll end up getting this thing working correctly =)
Sorry to ask more questions, but i'm trying to figure out an answer for you;
What speed is you P3 CPU and how much memory do you have installed? also, I take you have installed MySQL 4x and Perl first?
Reply With Quote
  #13  
Old 06-20-2006, 11:21 AM
mplostcause
Fire Beetle
 
Join Date: Jun 2006
Posts: 13
Default

I have no problems with questions =) ask away. The ram on the computer is 256mb, the procressor is only 1ghz. I decided to use the computer in question because it isn't very useful to me gaming anymore so I just let it sit around =P. And I did install mysql and perl first just as instructed in the guide.
Reply With Quote
  #14  
Old 06-20-2006, 01:53 PM
Angelox
AX Classic Developer
 
Join Date: May 2006
Location: filler
Posts: 2,049
Default

The speed is ok, I'm running it with a P3 870 MhZ - but I think you may have too little ram. Somebody correct me if I'm wrong, but I inderstood the zones load up into memory, and need a lot of it. I have 1.25 GB of Ram in mine. Probably your 256mb is getting mostly ate up by your XP OS.
Reply With Quote
  #15  
Old 06-20-2006, 01:56 PM
Angelox
AX Classic Developer
 
Join Date: May 2006
Location: filler
Posts: 2,049
Default

Email me when you can, I have more help for you, but this freaking forum is not letting me make long post
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

   

All times are GMT -4. The time now is 09:17 AM.


 

Everquest is a registered trademark of Daybreak Game Company LLC.
EQEmulator is not associated or affiliated in any way with Daybreak Game Company LLC.
Except where otherwise noted, this site is licensed under a Creative Commons License.
       
Powered by vBulletin®, Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Template by Bluepearl Design and vBulletin Templates - Ver3.3