ID:293752
 
BYOND Build Number: 422.1022
Operating System: Windows XP
Video/Graphics Card:
Game Hub/Link:
Internet Connection Type:
Firewalls/Routers:

Problem Description: I can open BYOND, but when I try to open a game to play, I get an error involving dreamseeker.exe and tells me I should problem reinstall BYOND.
Note this is NOT everytime. Once I reinstall and restart my computer I have no problems for a day or two.

Steps to Reproduce Problem: No clue. You tell me? Happens randomly.
What exactlydoes the error message say?
Does this happen with every game or only a special one?
What colour depth are you running on and are you using hardware accelerated mode?
In response to Schnitzelnagler
C:\Program Files\BYOND\bin\dreamseeker.exe "byond://insert game ip address here" -pager

And then another pops up saying "Could not run dreamseeker.exe perhaps you should reinstall BYOND?"


All games, as you can see by the error message. Not sure what the deal is.
In response to SSJ Radditz
I'll have to discuss this with someone more familiar of the internal processing.
Please be patient. Thank you in advance.
In response to SSJ Radditz
I was a little confused by your report at first because the version number you put in is incorrect. I assume you meant 442 and not 422. Not only does 422 not start Dream Seeker with a -pager argument, but it doesn't have a build number over 1020.

The message that dreamseeker.exe could not be started and perhaps you should reinstall is genertated by the pager. The pager is going through this sequence of events:

1) Lookup world URL you tried to join to get the byond://ip:port -- which it does.
2) Find the path where dreamseeker.exe is stored so the game can be launched -- which it does.
3) Attempt to launch a new Dream Seeker process.

Step 3 is where it's failing. Because the path it reported is presumably valid, I can think of only two possibilities. Either you have insufficient memory or other system resources to launch Dream Seeker, or a virus is corrupting (or deleting) dreamseeker.exe or one of its associated DLL files so that it won't launch.

To me this sounds like your system is running low on memory or resources. You did mention that you're fine after a reboot for a few days, so probably the only thing you have to do to fix this is restart your computer more often; I doubt the reinstallation is necessary. However, a full scan for malware would not go amiss (run your virus scanner, and also try out Malwarebytes). I'd also check into what else you might have started running recently that might be sucking up resources, perhaps due to a memory or GDI leak. And if you have a small amount of memory, upgrading that would probably also be a good idea; then even if you didn't find the source of the problem you could make it happen less often.

Lummox JR