PDA

View Full Version : Question about 1017 Error w/ XP


ajjjax
12-16-2003, 03:51 PM
I know there have been many discussions for the 1017 error and I have read the stickies and other articles regarding some possible solutions but I was wondering if someone may be able to offer some different insight regarding my 1017 error.

First off, I'm running XP Professional, Eqemu 5.2, and minilogin and have both the client/server on the same machine. My computer is slow, so after I connect to my server I can see my desktop momentarily before eq begins to load and I've noticed that when everything is fine I see what appears to be my eqemu account being submitted in the world.exe screen. Now when I get the 1017 error, I do not see the eqemu account being submitted and was wondering what could be the problem there?

What is really strange to me is that if I patch to eqlive I see it replace my eqgame.exe, lpatch.exe, and eqhost.txt only and then I'm able to play again until the problem resurfaces, after I replace the eqhost.txt file of course. I've tried replacing only the eqgame.exe and lpatch.exe from a backup but that doesn't work.
Is the patcher replacing or doing something else in the background, cleaning/deleting tmp files that I'm not aware of? Like I said, patching to eqlive has always fixed my 1017 error, but since we've been warned not to patch to eqlive after the 16th, I'm stuck.

Conan
12-16-2003, 03:57 PM
Make sure that you have the in account

username=eqemu
password=eqemu

ajjjax
12-16-2003, 05:09 PM
I have that account and pass in the db

Vaelene
12-17-2003, 04:40 AM
The EQEMU 5.2 builds do not work with minilogin. Some of the code was removed from them to prevent them from working with minilogin. If you have a compiler you can follow this link to a solution. http://www.everquestserver.com/forums/viewtopic.php?t=11705

ajjjax
12-18-2003, 03:06 PM
I have already entered the extra code into 5.2 and compiled it, like I said earlier the emulator works fine for the first couple of times I play it then for some reason it stops submitting the eqemu account to world.exe. I could fix this though with a repatch to eqlive but I notice that it only replaces those files that I listed in the original post and was wondering if anybody knew what else the eqlive patcher fixes???

ajjjax
12-30-2003, 10:25 AM
Well nobody seems to know the answer to this question but I was wondering if a dev has some idea or is anybody else experiencing this problem as well.

I have since upgraded to 5.3dr2 and am running windows XP pro on an AMD chipped machine. Like I said in previous posts, if I patch to eqlive it replaces only eqgame.exe, eqhost.txt, and lpatch.exe files. I can then login and play fine for hours, but it seems that after I restart my machine and then try to launch eqgame.exe (with patchme) it gives me some windows error that there is an access violation somewhere in the code and it is unable to continue. If I restore the whole everquest directory and then try launching eqgame.exe again it will give me the same error. In fact every executable in the everquest directory produces a microsoft error, you know the one that prompts if you want to send a report to microsoft?

The only fix I have found is to run the patcher and not just EverQuest.exe that is in my everquest folder, since it produces said windows error, but a virgin version of EverQuest.exe that I downloaded from SOE. It will launch, replace eqgame.exe, eqhost.txt, and lpatch.exe and then the whole process starts all over again for me. Anyone experiencing something similiar or have any other ideas?

ajjjax
01-01-2004, 10:50 PM
nobody else has experienced this? Hmm, time for a new computer I guess.

kathgar
01-01-2004, 11:06 PM
The only thing you ever have to change in your EQ directory if we are current with live, is eqhost. Thus, there is no reason for eqgame and lpatch to change. You probably have a virus or a trojan messing with them.

ajjjax
01-02-2004, 05:28 PM
Haha, that's what I thinking all along but was just waiting for a confirmation of my suspicions; and from a developer to boot, Thanks! Like I said earlier, time for a new computer.