Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Questwizard

Members
  • Posts

    4
  • Joined

  • Last visited

    Never

Questwizard's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Still getting the ame error here as well. See this as well: http://www.touchofdeathforums.com/smf/index.php/topic,49574.0.html . Its really starting to drive me nuts. Every version I try has this problem (I've now tried 2.7 and 2.6 as well), and I've pinpointed the most likely causes to be the news retrieval or server status check upon starting the client. I tried on XP SP2, and just tried SP3 to see if that worked, and still no luck. Its crash heaven every single time as long as the server is up.
  2. I'm on XP SP2, on an Admin account anyway. That can't be the problem. EDIT: I get the same error on my desktop computer (also XP SP2), so its not my laptop causing it. Could running both the server and client on the same computer be causing the problem? I can't hook both of my computers to the internet at once, so I can't try running them separately at the moment.
  3. Hmm. Still no luck. Its still giving the same error as before.
  4. I just downloaded version 2.8 about an hour ago, installed the library files with ELI, and started up the server to make sure it works so i can start working on my new game. Now, every time I start the client with the server running, after about 3-5 seconds, I get error 9 and the client shuts down. I suspect it has something to do with retrieving the text for the news box, as I don't get the error as long as the server is down, or with an invalid IP in Config.ini. If I put a bad IP in there, run the client, and change the IP to 127.0.0.1 again after starting the server, the client crashes instantly. I've already looked around the forum and can't find anything on how to fix it, and the error guide doesn't cover this particular case of error 9. Keep in mind that this is a clean, unmodified install with absolutely no source mods, script edits, or anything. The only thing I've touched is Config.ini, and that was to change the IP to 0.0.0.0 to see if it still crashed, but that's been changed back to 127.0.0.1 now, so its the same as a clean install. Does anyone have any ideas on how to fix it?
×
×
  • Create New...