Unable to Login

dierks · #1 04-18-2006, 08:34 PM

"Logging in to the server. Please wait... "

I can't seem to get past this message when using Minilogin. I recently installed Titanium and EQEmuServerPack-3.1, ran VarCheck ( to ensure compatibility ) and it showed that the version was compliant. I can log onto public servers ( tried Paradigma ) but am still unable to log-in to my own Minilogin server.

Is there anything I could be doing wrong? I just installed the ServerPack ( set it to Minilogin Server, and Client ), but still can't get past that screen.

**cavedude** · #2 04-18-2006, 11:43 PM

Are the client and server on the same machine?

dierks · #3 04-19-2006, 02:32 AM

Yes, they are.

allpumk · #4 04-19-2006, 04:43 PM

I get the same message "Logging in to the server. Please wait... " from a fresh install of titanium and 3.1 serverpack. I am new to eqmu but I think my login error is listed below:

LoginServer.ini read.
[Status] Loading opcodes..
Server mode: MiniLogin
Login server listening on port:5999
4187 New Server connection: 127.0.0.1 port: 59913
91093 New client from ip: 127.0.0.1 port: 2545
Unknown packet: .4233692 [**.**.**.**:15->0.0.0.0:0]
[OpCode 0x0001 (OP_Unknown) Size=13]
00000: 00 02 00 00 00 00 00 00 - 00 00 00 08 00 | .............

Unknown packet: .4233692 [:**.**.**.**15->0.0.0.0:0]
[OpCode 0x0003 (OP_Unknown) Size=11]
00000: 00 03 00 00 00 00 00 00 - 00 00 00 | ...........

**cavedude** · #5 04-19-2006, 10:58 PM

Hmmm... it looks like minilogin and Titanium aren't getting along to well. That would make sense since minilogin uses opcodes.conf and now with the multi client support we have three opcode files (plus the original opcodes.conf) I am going to get my own Titanium client shortly but until then I can't do any testing.

**fathernitwit** · #6 04-20-2006, 01:09 AM

hmm... I dont remember any login server changes needed for titanium... it looks like its not mapping any opcodes.

**cavedude** · #7 04-20-2006, 02:01 AM

The login opcodes in opcodes.conf that comes with the 0.7.0 source are all 0x0000. patch_6.2.conf has the proper opcodes filled in, but I would think minilogin wouldn't know to look for that, AND if it did wouldn't it only use it for the 0.6.2 client and not titanium or live? Could this be the problem? I'm sorry, FNW I haven't had time to figure out exactly how the opcode switching between clients is handled.

Filling in the proper opcodes in opcodes.conf should fix this problem but will that in anyway affect public login? Or was the change to opcodes.conf a typo?

For the time being, download the 3.1 upgrade installer and unselect everything except for EQEmu. That *should* correct this problem.

**fathernitwit** · #8 04-20-2006, 11:37 AM

opcodes.conf is only used by minilogin now, just because we havent recompiled it. just copy the patch_6.2.conf file to opcodes.conf

**cavedude** · #9 04-20-2006, 01:40 PM

Cool already done thanks for the confirm.

allpumk · #10 04-20-2006, 03:06 PM

Quote:

Originally Posted by fathernitwit

opcodes.conf is only used by minilogin now, just because we havent recompiled it. just copy the patch_6.2.conf file to opcodes.conf

Thank you guys, I did this and now I can login now using minilogin.

DDude11 · #11 07-21-2010, 02:24 PM

where can i download patch_6.2.conf and do i just copy it into my eqemu folder? i have the same problem and it seems that will solve it but i dont know where to get it!

DDude11 · #12 07-21-2010, 02:25 PM

haha nevermind ust realized its in the folder already but how to i "copy it to opcodes.conf" like you said?