View Single Post
  #1  
Old 01-24-2002, 09:18 AM
madborg
Banned
 
Join Date: Jan 2002
Posts: 322
Default Let's resolve this "patch" problem

The problem? You get a loss of connectivity message in the client and something that makes it sound like you need to re-patch

I am still puzzled. One camp says "don't use eqw 2.2 at all cause it has problems, use eqgame patchme". The other camp says "don't use eqgame patchme, use eqw 2.2".

First, I am not doubting that each camp is convinced that their method works. I am sort of neutral where I use "patchme" but haven't tried eqw 2.2.

Second, who is in the third camp that can say "either method works for them?"

And of course there are still couple or more that say "neither method works for them".

I need to know which camp you are in:
-camp 1: ewq 2.2 only
-camp 2: eqgame patchme only
-camp 3: either is fine
-camp 4: neither works

Quote:

The following is the user scenario, at least I think so:

1. user has set up their own minilogin server

2. running minilogin, world. zone on one box

3. user logs in either on same box, or second machine same internal network [let's keep this simple for right now]

4. all the servers are up, no error messages, gtg

5. user has the correct eqhost.txt file in their client directory

6. user selects either eqw 2.2 or uses eqgame patchme.

7. all screens are okay, user gets to server select screen
[at this point should only be one server, your own]
8. user selects server, then what?
A. user gets to char select screen then selects character and gets message '------------'

B. User selects server and then gets message '---------'

Is there a third case to this?

Then using the same setup, methods, user/passwords
if user changes the choice of eqw 2.2 or eqgame patchme, then they don't get condition A or B, and can login.

I am only interested in the loss of connectivity message, the one that says something about running the patch server.

**added**
Only report your own server issues, not when you try to connect to some XYZ server.

The deadlock issue should not show up because you havn't been running long enough to do anything.
Reply With Quote