OS: Win98
Current Emu Ver. 4.3
Last Patch 01/06/2003
This has always been the way to correct the 1017's for me. Like you, I get them with every patch release. However, I only get them when I patch from EQLive & EQEmu. Both at once <~~ Take note of that.
The problem, as far as I can tell, is normally based in the 'eqhost.txt' file.
Most of the 'Readme.txt' releases in the past year have always given the same example of "Cut and Paste this into your 'EQHost.txt' file . . . but that never worked for me. Ever. I had to get in there and tinker with it.
Now, this is theory here, not fact . . . I believe that EQ has a built in way of detecting whether there is something wrong with the 'eqhost.txt' or not. I believe the software checks for how many lines long the document is, and the exact size, or more to the point, a mix of both I haven't been able to pinpoint.
Example time !!
This is my current configuration:
----------------------------------------------------------
[Registration Servers]
{
"localhost:5999"
"localhost:5999"
}
[Login Servers]
{
"localhost:5999"
"localhost:5999"
"localhost:5999"
"localhost:5999"
}
----------------------------------------------------------
See, now, that looks like a bit of overkill, right? It works, sure. But why not just use:
----------------------------------------------------------
[Registration Servers]
{
"localhost:5999"
}
[Login Servers]
{
"localhost:5999"
}
----------------------------------------------------------
BANG !! 1017 !! Why? No clue. . . . now, one more:
----------------------------------------------------------
[Registration Servers]
{
"localhost:5999"
;
;
;
;
;
}
[Login Servers]
{
"localhost:5999"
;
;
;
;
}
----------------------------------------------------------
Working fine. No 1017. That is perfectly functional. I have no idea why, because it makes no sense. But, oh well.
These examples work fine on my system. You can test them out yourself and see if you come up with the same results.
One aspect of this (and a lot of other similar problems) that has never fully been explored is whether the system of theoretical checks and balances by the software is expansion-specific. IE: Basic EQ doesn't have it, but EQ:SoL does. That would explain the random occurance of the 'Notorious 1017'. But it could also be simply the OS. Win95, Win95 OSR2, Win98, Win2k, Win2kProf, WinXP, . . . all of these have a moderately different way of handling networking. From the top it all looks pretty much the same (Big words, cryptic anagrams, bad math) but there's a lot of differences in there.
Now, the mind boggling part . . . there's a good chance we're dealing with a combination of OS-Based networking flukes & EQExpansion-Based checks and balances . . . which leaves, roughly, 12,000 possible combination configurations, not including Windows Program Setup configuration for different networking software/drivers (which would push it well over 500,000 probably) then tossing in Firewall software, AOL-specialty TCP/IP drivers, etc, etc, . . . there's no point in even bothering thinking about it . . . Especially when chances are there is 1 single thing all these cases have in common.
Now, back to Earth, in conclusion, from my year of research into the 1017, I'd tell everyone who followed the readme exactly and is still pulling a 1017, to tinker with their 'EQHost.txt' file. Not the addresses or anything, just the length, number of lines, etc. Patch your EQLive (after backing up your files) and compare VI's 'eqhost.txt' with the one you're currently using. Try to make them as similar as possible. Trimming here, fluffing there, never actually changing addresses, just the number of them. This will normally fix it for you. Well, theoretically anyway.
