I looked through the threads and can't seem to find posts similar to the problem I began having. For some reason, when I try to connect SB to my existing FS2004 multiplayer session (using SBrelay), SB crashes about 50 to 75% of the time. It used to work fine, so I'm not sure what happened. Any suggestions?P4 2.4Ghz512M RamWindows XP

Just to make sure you're doing it right1. Start SBrelay - wait until it is fully active before you proceed2. Start FS2004 - activate Multiplayer - find SBrelay - JOIN3. Either start Hostsb.dll (from the FS2004/Modules option) OR run the program SB Host.exe in your SquawkBox folder.4. Run SquawkBoxIf you're doing all these things correctly, and it used to work in FS2004, I'm at a loss to advise further. What changes did you make before it stopped working? What error do you get when it crashes?bf

Anyone else have this problem per chance?

Sorry, didn't see your reply originally..I had ran Norton's registry clean up, which is when it started having issues, so I formatted my hard drive (I know this sounds drastic, but I do this from time to time to clean things up. -but only after backing up the important stuff...) and reloaded windows XP, downloaded all of the windows updates, drivers, etc. I then reloaded a fresh copy of FS9, and installed SB, SBrelay, and a couple of other addons that I always use.Unfortunately, my problem remained. I know it wasn't a corruption, due to the fact that I completely formatted my drive. This is what occurrs:Run SBrelayRun FS9Connect multiplayer session (goes fine)Open Host.dll (from within FS9)attempt to connect SB to the existing multiplayer session (this is where it goes bad):Normally, about 75 percent of the time, SB crashes, and I get the standard "windows XP error reporting" window, and SB closes down. No additional errors occurr. I did notice, however that if I imediately launch SB again, that it has about an 80% or so chance of working fine. Although this seems to work, it is a major nuiscence, and I am curious what garbage may be running in the background that may affect framerates.If I run squawkbox in the "non multiplayer" mode, it launches fine every time. It seems to be a problem with the multiplayer portion. I tried to allow the ports in my router, as well, I told my router that my PC was to be exposed to the internet without being hidden behind the firewall. None of these things were required before, but just as a precaution, I tried them. To no avail, however.

OK, in your reinstall did you remember to make sure that the fs9.cfg file includes the [Oldmodules] option with the entry Hostsb.dll=1XP is very stable and constant reinstalls are generally unecessary but I do know some people love to do it, like my brother who must get some kind of satisfaction from the process.bf

If you are referring to the " [oldmodules] entry, yes. I remembered to add that one.

Yep, same thing happens to me and about 75% of the time,had it from day one of using FS9, butI just load SB again and it loads ok, and as such I have not tried to resolve this yet, FPS are still the bigger concern!But I never had this problem in FS2002.Dave

Your Squawkbox is SquawkBox 2.3 Build 5 606265 bytes?I have that working here without fail unless I forget to start HostSB.dll from within FS9 prior to launching SquawkBox.exe.Larry

I have the problem too, but no 70%, 98% crashes. I dont understand, because as first i cant connect /same problem/ later problem fixed alone.. and now i have problem again .. /changes only scenery and i buy PMDG / ..I watch opened ports trough firewall. I think squawkbox have to connect to localy opened ports, but he try find sesion outside .. /all packets sent to the router (gate to the internet)/ and after directplay send message .. unable to connect and after cancel .. crash, sometimes i am connected after pushing CANCEL .. uuuffff

I normally have 2 problems:1. Getting the SBRelay-Fs2004 session in FS2004 multiplayer setup and2. SB normally crash when I get the multiplayer session set upIt's the unpredictability that drove me mad. Nowadays, I use FS2002 for flying at VATSIM.Michael TanCanberra

I have heard that systems with P4 HT chips have trouble with SBRelay when HT is enabled. I have had similar problems with my system. I prefer to leave HT enabled due to the other programs open during my flights and I found a very simple workaround for FS9 that never fails. I use the SBHost window for FS2002 rather than the .dll module. Also, "join" rather than "host" the session in the FS9 multiplayer menu. That has always worked for me with HT enabled.

I have HT too, and enabled, and use the same method as you, but without sucsess. today i try turn off HP ... maybe ... ufff

I have this exact same problem but connecting to vatsim with SB outside or inside FS9 it will always crash FS9. My only method was this one,1) Start SBrelay2) In FS9 Host a session3) Start SBhost outside FS94) Start SB5) Join your Hosted session and connect to Vatsim6) Back in FS9 Disconnect from your Session7) Join the SBrelay one that appears8) Now you can see other traffic and avoid any crashes. I have not yet tested hosting SBhost inside FS9 yet.This evening however i minimized FS9 to change ATC frequency in SB but i couldn't get back into FS9.RegardsG-MIDYhttp://www.airliners.net/open.file/265713/L/

I find all my problems are realted to HOSTSB.When I use the default one that comes with SB I can connect everytime.RonCVA1701

I have a similar problem. I follow all steps and in most cases I get up and going on the second try. What usually happens is when I start SB, Shortcut on desktop, SB will not open , but the fs window opens and HOST SB is froze. I have to close all and start over, and all goes well.....except..I cannot see a/c visually, I see them on TCAS??MB