#11
|
|||
|
Okay, went diving for an answer to this and came up with a surprising solution. This post says it has found a solution to this issue by reducing the clock speed of their processor.
https://www.project1999.com/forums/s...=253854&page=3 | ||
#12
|
|||
|
This also seems to be resolved by setting a single core to run Windows. Have either of you tried that?
I cover how to do that here | ||
#13
|
||||
|
Quote:
| |||
#14
|
|||
|
Okay, we may want to try and get your log file and see if an error is popping up.
Here is a post about where to find and enable them. Also, this Reddit post talks about flushing your DNS as a potential fix to not seeing the servers/being able to log in.Find that here. | ||
#15
|
|||
|
Hey,
Below seems to be the error generated when trying to login to Blue. I can paste the wholes sequence, but this appears to be the issue terminating my connection. 2022-07-16 16:32:30 WorldAuthenticate: Initiating Login. 2022-07-16 16:33:00 Networking: Connection Closed [0] with 0 pending bytes. 2022-07-16 16:33:00 *** ERROR: WorldAuthenticate. My message arrival was NULL, the net has been shutdown. 2022-07-16 16:33:00 *** WorldAuthenticate. Checkpoint 3. Flushed my DNS Windows IP Configuration Successfully flushed the DNS Resolver Cache. Still unable to login into Blue. Same error as above. Just fyi, i really appreciate all the suggestions. | ||
#16
|
|||
|
I reset my router & flushed again and was able to login to blue...
| ||
#17
|
|||
|
YOU DA MAN
| ||
#18
|
|||
|
Yyyyessss!
| ||
#19
|
|||
|
Here's my log.
2022-07-16 17:13:44 World initialized: load 2022-07-16 17:13:44 load done. 2022-07-16 17:13:44 2022-07-16 17:13:44 Starting char select. 2022-07-16 17:13:44 2022-07-16 17:13:44 Clearing display buffers. 2022-07-16 17:13:44 2022-07-16 17:13:44 Display buffers cleared. 2022-07-16 17:13:44 2022-07-16 17:13:44 Initializing character select UI. 2022-07-16 17:13:44 Resetting game UI. 2022-07-16 17:13:50 Zone Connect -- 0 -- Received MSG_ZONE_ADDRESS 2022-07-16 17:13:50 Zone addr [160.72.227.57:25627] received... 2022-07-16 17:14:20 ERROR: World did not drop the connection. 2022-07-16 17:14:20 Failed to connect to zoneserver (160.72.227.57, port 7012), result = 5, for MSG_ZONE_ADDRESS. 2022-07-16 17:14:20 2022-07-16 17:14:20 THE SERVER IS NOT RESPONDING. 2022-07-16 17:14:20 2022-07-16 17:14:20 end of DisplayScreen 2022-07-16 17:14:20 | ||
#20
|
||||
|
Quote:
The closest thing I've found is an incompatibility between screen dimensions. Found at this article here. | |||
|
|