I was flying succesfully in vatsim before, but after a lockup caused by, i think, sb, I had to restart winxp and do a system restore, i couldn't start flying in vatsim again. After i start sb relay12 i get the following line "Error 0x80004001 creating 2004 address for TCP/IP". What is wrong? What should i do?Thanks Petteri Pulkkinen

Try reinstalling Sb & SBRelay.

I tried... with no success, but for your information an extract from my letter.."...Referring to my first letter: I booted my computer and WinXP told aboutproblems offering the safe mode etc.I chose the option "Previous setup" - sorry I don't know the exact phrase inEnglish as I have a Finnish version.The problem was still on.. then on Monday I decided to fly off-line andstarted fs2004. The first screen with dc3 appeared but nothing after that.The shutting down of the fs ( via task manager) gave a MS Error Report witha phrase "apphung" in fs9.exe.I installed fs9 again with no new results. Then I made a real cleanre-install of the fs9 deleting everything I thought having sth to do withit... no new experiences... the sim just hang on the opening screen.After this I ran dxdiag, which gave me bad results on the network(directplay) screen... so I had a close look. My DirectX was version 8.1again.. (!?) ( I indeed had DX9.0b from the very beginning). So I think thatthe violent shutting-down and booting of my computer threw me back to theold version of DirectX because I - after the seeing the dxdiag results-re-installed dx9.0b and succeeded in starting the fs9. I even managed tofly again in VATSIM.One more question: three weeks ago I had my old computer xp1700+, 512mb rametc. with win2000. I always had a very fast sbrelay connection and insquawkbox I only entered an empty search-box for a "flight". Now I havesince 3 weeks AMD xp3000+, 1024 ram and win XP. Both the sbrelay andsquawkbox are "very slow" and I have to enter in SB every time 127.0.0.1when searching for a play... is this due to winXP or my computer?"So this case is closed for now. :)