Archived from groups: alt.games.diablo (
More info?)
On 21 Jan 2005 09:35:35 -0800, "Mickey" <mickeyb@comcast.net> wrote:
>Why can't you get on? Dog eat your LoD CD again?
>
>Mickey
No, as a matter of fact I have a brand new second CD, waiting for me
to get this problem ironed out. I gave you the short version before,
but apparently you missed it, so I'll try to flesh it out a bit more
here, at least as much as I can remember.
I got this new-to-me-but-definitely-not-new computer back in July. It
was a *great* deal, everything I'd been looking for in a box plus a
19" monitor for about $500. The only problem it has is that it won't
connect to BattleNet, which of course was the purpose I bought it for
:-(
Every time I try to connect to BNut, it hangs at the "checking
versions" screen. I posted here and in ART, asking for suggestions,
and received plenty, all except one of which I've tried (coming
later). The Hamster and I (and a few other people) spent many hours
fiddling with the settings on the modem, which ended up optimized for
BNut, but that's not the problem, because I *can* get on with things
like Subbot (and one other way where I ended up in a chat channel, but
I don't remember how), I can host or join TCP/IP games, play SP in the
regular games and now (not when the problem started, as I hadn't
downloaded any then) in various mods, in short I can do everything in
the game except get on BattleNet.
We tried deleting all of the BattleNet settings in the registry, even
before I got the canned reply from Blizz support, and I even had
someone send me their Realms settings and put it into the registry
file. I've done numerous uninstalls and reinstalls of D2 and LoD, IIRC
(and I'm not sure of this) when I try to connect with a new install it
updates it to 1.10 but then hangs again, but I've also tried getting
the patch from Blizz's site. Zone Alarm was *not* the problem, since
apparently it never got to the point where Zone Alarm checked it (in
other words it never actually sent info out or tried to act as a
server), but I went ahead and replaced ZA with Kerio's Personal
Firewall, which IIRC I've manually set to allow D2 (either that or it
came up with the TCP/IP games), since again the program never seems to
get to it.
This *does* bring up the only other problem I've found on the
computer, which is that neither firewall seems to work correctly. Most
(but not all, I found this out the other day) of the time when the
firewall is running, I can't do most things on-line. IIRC I can get
messages in Agent, but sending them is iffy at best, most messages
will not send (and if it won't send the first time, repeated attempts
will not work, until I turn the firewall off), IE gets a can't connect
message, Trillian will say it's connected but no one shows up on my
list (again, most of the time, IIRC, it's been a while since I allowed
this situation to last more than a couple of seconds). This leads me
to believe there's a security setting that I can't find, but I need to
finish detailing the problem first (yeah, I know, this is a lot more
than you were looking for, but I'm trying to be thorough).
Ok, what else haven't I covered? Pinging BNut produces the expected
results, it times out after about 15 or 16 hops, as it should since
Blizz disabled it. A couple of months after I got and responded to the
canned reply from Blizz support, I *did* get one personal reply, where
the tech guy decided I'd hacked the program and gave me various ways
to get it working right (all of which I'd already tried). I replied
asking what led him to think I was a hacker, and haven't heard from
them since. I *think* that's about all, if I've left anything out
please feel free to ask.
The one solution I haven't tried yet was suggested by Ken over in ART.
He sent me disks for both Win 2K Pro (which is what is on here) and XP
Pro and has suggested a format and reinstall. The morning that I had
set aside to do this, the power supply failed on the computer. I took
it back to where I bought it, since it was (barely) still under
warranty, and after waiting about 3 months for the motherboard that
they thought was the problem they decided that maybe I was right and
it was the power supply, and I finally got it back on Christmas Eve.
I'd asked *them* to format and reinstall, but the guy forgot to, and I
didn't want to wait *another* 3 months for him to do it, so I didn't
press the issue.
Now, of course, I've been using this thing for a while and have all
kinds of things on here that I'd hate to lose (and am not smart enough
to find all of them and try to learn how to burn them to CD), so I'm
more than a little hesitant to do the format *if* it isn't going to
work. If I think there's a good chance that it will, I'm willing to
sacrifice everything I have on here, since again the main reason I
bought this silly machine was to be able to play on BattleNet the way
the game is supposed to be. So the question again is: Do you think
that doing a format and reinstall of Windows will solve the problem?
And a second, related question: Given your choice, which would you
install, 2K Pro or XP Pro? I had heard that 2K Pro was the most
stable, and indeed other than IE closing a few times I've had no
problems with it, but I've since been advised by other people, my
father being the most notable, that XP Pro is better.
ald
"Knowledge is Power"
VK`Sister`ald level 47 Rogue (HF V&K) (RIP :-( )
Matriarch Sis-West level 82 Bowazon (US West)
Champion RingsNThngs level 61 Bowazon (US West)
Slayer ZannEsu-ald level 51 Sorceress (US West)
Matriarch Sis-AR level 99 Bowazon (Ancestral Recall Mod)
Champion Creepy-AR Level 91 Necromancer (AR)
Slayer Zan-AR Level 79 Sorceress (AR)
Slayer SisEight-AR Level 78 Bowazon (AR)
Gems-AR Level 55 Barbarian (AR)
Matriarch Sis-otSEye Level 78 Bowazon (US West, co-op)
BtaSisEight-ald Level 50 Bowazon (LoD 1.10 SP)
Aragorn-AR Level 51 Zealadin (AR)
Champion LTwoSis-ald Level 79 Bowazon (US West Ladder)
CotSRSig #16
Facebook
Twitter
Instagram