ibishop Posted November 22, 2005 Report Share Posted November 22, 2005 I have just downloaded and installed SB 3.0 but on loading FS9, I get the following error message "The Squawkbox module was unable to start FSUIPC because FSUIPC could not be initialized. Ensure that FSUIPC is properly installed and restart Flight Simulator" I am running a registered and up-to-date version of FSUIPC and have had no problems with other 3rd party add-ons. I have re-installed FSUIPC but error message persists. Any (polite) suggestions? Regards Ian Bishop Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 22, 2005 Report Share Posted November 22, 2005 I have just downloaded and installed SB 3.0 but on loading FS9, I get the following error message"The Squawkbox module was unable to start FSUIPC because FSUIPC could not be initialized. Ensure that FSUIPC is properly installed and restart Flight Simulator" That's not a message from FSUIPC, so I can't really say what its problem is -- FSUIPC does not need "initialising". It just runs when it is loaded as a Module by FS. You may need to contact SB support. If you want me to take a look, please try again, then close down FS altogether, find the FSUIPC.LOG file (it'll be in the FS Modules folder), and show me what it says. Keep the 'session' short and show the whole log. Regards, Pete Link to comment Share on other sites More sharing options...
ibishop Posted November 27, 2005 Author Report Share Posted November 27, 2005 Pete Many thanks for your reply. Sorry for delay in responding as I have been away for a few days. Here is most recent example of FSUIPC Log ********* FSUIPC, Version 3.50 by Pete Dowson ********* Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="Ian Bishop" User Addr="i.bishop@blueyonder.co.uk" FSUIPC Key is provided WIDEFS not user registered, or expired Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=48143605[48143605] InitDelay: 0 seconds WeatherReadInterval=4 MakeItVersionFS2002 is set! LogOptions=00000001 DebugStatus=15 18797 System time = 15:57:12 18817 D:\Program Files\Microsoft Games\Flight Simulator 9\ 18817 System time = 15:57:12, FS2004 time = 12:00:00 (00:00Z) 79264 FLIGHTS\OTHER\FLTSIM.flt 79744 AIRCRAFT\c172\Cessna172SP.air 80235 Aircraft="Cessna Skyhawk 172SP" 85943 Module [M1] identified = "sbmpjoin9.dll" 85953 Module [M1] "sbmpjoin9.dll" access registration is okay 101776 Module [M2] identified = "sbmod9.dll" 101776 Module [M3] identified = "sbtrans9.dll" 101786 Module [M3] "sbtrans9.dll" access registration is okay 102828 Advanced Weather Interface Enabled 106373 C:\Documents and Settings\Ian Bishop.STUDY\My Documents\Flight Simulator Files\UI generated flight.flt 106833 Clear All Weather requested: external weather discarded 151468 Traffic File #15 = "scenery\world\scenery\traffic" 152840 Traffic File #16 = "scenery\world\scenery\traffic030528" 181351 WeatherOptions set, now 48143605 (timer=0) 184735 Traffic File #26 = "scenery\world\scenery\traffic_pai" 199076 System time = 16:00:13, FS2004 time = 15:58:24 (23:58Z) 199076 *** FSUIPC log file being closed Memory managed: 2 Allocs, 164 Freed ********* FSUIPC Log file closed **** Doesn't seem to say a lot to a layman like me so given your previous comment, I will take this up with Squawkbox people (unless you can identify anything from log). Many thanks again Regards Ian Bishop Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 27, 2005 Report Share Posted November 27, 2005 Here is most recent example of FSUIPC Log Okay. These parts: 85943 Module [M1] identified = "sbmpjoin9.dll" 85953 Module [M1] "sbmpjoin9.dll" access registration is okay 101776 Module [M2] identified = "sbmod9.dll" 101776 Module [M3] identified = "sbtrans9.dll" 101786 Module [M3] "sbtrans9.dll" access registration is okay 199076 *** FSUIPC log file being closed certainly indicate that 2 parts of SB3 connected okay -- SBMPJOIN9 and SBTRANS9.DLL. The part called SBMOD9.DLL hasn't realy done anything by the time you terminated 90 seconds later, so it was neither accepted nor rejected. There is certainly nothing wrong with the SB3 access to FSUIPC. I really don't know what they mean by the message you say they give. I can only suggest you ask SB3 support. BTW, is SB3 formally released now, or still in Beta testing phase? A lot of folks seems to be using it with no problems at all. Regards, Pete Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now