kj@hotmale.com Posted August 30, 2005 Report Posted August 30, 2005 I just registered FSUIPC and when I open the module inside FS2004 it works fine but it's not connecting to any outside programs i.e squawkbox. Please help me!
kj@hotmale.com Posted August 30, 2005 Author Report Posted August 30, 2005 I've been trying to reinstall FSUIPC over and over but it just doesnt work, I don't know what to do. I enter the name, email and key correct, it works and tells me to restart FS before the effect can take place, so I do then I can't use any programs with FSUIPC e.g Squawkbox. It's like FSUIPC isnt even there. :cry:
Pete Dowson Posted August 30, 2005 Report Posted August 30, 2005 I just registered FSUIPC and when I open the module inside FS2004 it works fine but it's not connecting to any outside programs i.e squawkbox. Please help me! Squawkbox doesn't need a user-registered copy of FSUIPC in any case. I cannot help you without any information. Please try again, then close FS. Find the FSUIPC.LOG file (in the FS Modules folder) and show it to me. Or you can Zip together both the FSUIPC.LOG and FSUIPC.KEY files and send them to me at petedowson@btconnect.com. Regards, Pete
Pete Dowson Posted August 30, 2005 Report Posted August 30, 2005 I've been trying to reinstall FSUIPC over and over but it just doesnt work, I don't know what to do. I enter the name, email and key correct, it works and tells me to restart FS before the effect can take place, so I do then I can't use any programs with FSUIPC e.g Squawkbox. It's like FSUIPC isnt even there. :cry: Again, you supply no information at all. Please see my previous reply. Pete
kj@hotmale.com Posted August 31, 2005 Author Report Posted August 31, 2005 hello Pete, thx for the quick reply, I sent the files to you via email but just incase you dont receive them here is my FSUIPC.log file: [General] History=C5XXB86G1BZS7OMTFG9TW TCASid=Flight TCASrange=40 TrafficScanPerFrame=10 AxisCalibration=No CentredDialogue=Yes ClearWeatherDynamics=Yes OwnWeatherChanges=No WeatherReadInterval=4 MoveBGLvariables=Yes TimeForSelect=4 MainMenu=&Modules SubMenu=&FSUIPC ... WindSmoothing=No AutoTaxiWind=No PropTaxiWind=No TimeSetMode=Partial WhiteMessages=No ThrottleSyncAll=No GraduatedVisibility=No LowerVisAltitude=0 UpperVisAltitude=25000 UpperVisibility=6000 GenerateCirrus=Yes WindShearSharp=No UpperWindGusts=No ExtendMetarMaxVis=Yes PatchSimApAlt=Yes DisconnTrimForAP=No ZeroElevForAPAlt=No AutoClearWeather=Yes ExtendTopWind=Yes WindSmoothness=5 SmoothPressure=No PressureSmoothness=5 SmoothVisibility=No VisibilitySmoothness=2 MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 MinimumVisibility=0 MaximumVisibilityFewClouds=0 MaximumVisibility=0 MaximumVisibilityOvercast=0 MaximumVisibilityRainy=0 OneCloudLayer=No ThinClouds=No ThinThunderClouds=No CloudThinness=1000 ThunderCloudThinness=10000 CloudTurbulence=No CloudIcing=No WindTurbulence=No SuppressAllGusts=No ExternalOptionControl=Yes AutoTuneADF=No KeepFS98CloudCover=No ShowPMcontrols=No MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No TrapUserInterrupt=Yes NavFreq50KHz=No ClockSync=No SmoothIAS=Yes SetVisUpperAlt=No VisUpperAltLimit=6000 MaxIce=3 WindSmoothingDelay=0 WindSmoothAirborneOnly=No VisSmoothingDelay=0 VisSmoothAirborneOnly=No SuppressCloudTurbulence=No SuppressWindTurbulence=No SpoilerIncrement=512 ShortAircraftNameOk=No FixWindows=No FixControlAccel=No [JoystickCalibration] ExclThrottleSet=No SepRevsJetsOnly=No FlapsSetControl=0 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 SlopeAileron=0 SlopeElevator=0 SlopeRudder=0
Pete Dowson Posted August 31, 2005 Report Posted August 31, 2005 hello Pete, thx for the quick reply, I sent the files to you via email but just incase you dont receive them here is my FSUIPC.log file: No, that is not a Log fle, that is the INI file. I have received files from a "Joseph Janica". I assume they are yours? If so, then I cannot access the KEY file because you didn't ZIP up the files and the KEY file is prohibited because they can be Registry files too. Please always ZIP files when sending them. The Log shows the SB3 modules connecting okay: 32109 Module [M1] identified = "sbmpjoin9.dll" 38000 Module [M2] identified = "sbmod9.dll" 38000 Module [M3] identified = "sb3gaugebridge.dll" 38000 Module [M4] identified = "sbtrans9.dll" I don't know if there should be any others. Unfortunately, the Log you sent is only a partial one -- you need to run FS, get whatever problem it is you think you have, then close FS, THEN ZIP up the FSUIPC.LOG file and the FSUIPC.KEY file. the INI file is not at all relevant. Anyway, from the little scrap of information you've supplied so far I see nothing wrong. The SB3 modules are present and connecting. I think you will need to describe your problems in much more detail before we can proceed. If it is simply that you cannot make SB3 work for you, then I'm afraid you are really in the wrong place -- I don't use SB3 and don't know anything about it. Possibly you have some multiplayer problem, in which case it isn't involving FSUIPC at all. You will probably have to go to SB3 support. Regards, Pete
Dieter Brugger Posted August 31, 2005 Report Posted August 31, 2005 I just registered FSUIPC and when I open the module inside FS2004 it works fine but it's not connecting to any outside programs i.e squawkbox. Please help me! Maybe put it the other way around. FSUIPC does not need to connect to SB3. SB3 will connect to FS through FSUIPC. So to connect to the VATSIM network nothing has to be done in FSUIPC. After having installed FSUIPC into the modules folder of FS just start SB3 and connect via SB3 to the VATSIM network.
kj@hotmale.com Posted September 1, 2005 Author Report Posted September 1, 2005 Sorry this is my FSUIPC.log and i will send you there rest via email: ********* FSUIPC, Version 3.48 by Pete Dowson ********* Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="Konrad Janica" User Addr="konnet@iprimus.com.au" FSUIPC Key is provided WIDEFS not user registered, or expired Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=40003605[40003605] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=15 5062 System time = 17:42:14 5062 C:\Documents and Settings\Konrad Janica\My Documents\Games\Flight Simulator 9\ 5062 System time = 17:42:14, FS2004 time = 12:00:00 (00:00Z) 28844 FLIGHTS\OTHER\FLTSIM.flt 28890 AIRCRAFT\c172\Cessna172SP.air 29437 Aircraft="Cessna Skyhawk 172SP" 32109 Module [M1] identified = "sbmpjoin9.dll" 38000 Module [M2] identified = "sbmod9.dll" 38000 Module [M3] identified = "sb3gaugebridge.dll" 38000 Module [M4] identified = "sbtrans9.dll" 38890 Advanced Weather Interface Enabled 43140 C:\Documents and Settings\Konrad Janica\My Documents\Flight Simulator Files\UI generated flight.flt 43594 Clear All Weather requested: external weather discarded 61640 WeatherOptions set, now 40003605 (timer=0)
kj@hotmale.com Posted September 1, 2005 Author Report Posted September 1, 2005 my problem is that since I registered FSUIPC it seems to be not active e.g cant use squawkbox (could before) and cant use tcas. But I can open the module inside FS and see all the settings and stuff.
Pete Dowson Posted September 1, 2005 Report Posted September 1, 2005 Sorry this is my FSUIPC.log and i will send you there rest via email As I said before, the Log shows the SB3 modules connecting to FSUIPC okay. The KEY file you sent shows you are using an illegally generated FSUIPC access key. Where did you get it? You are not listed as a registered user and you are breaking the law by using this counterfeit key. Unless you have an excellent explanation I will be reporting this This will no doubt be the entire reason for your troubles. I cannot tell any more because the Log you show here, and the one you sent by email, is not complete. I asked you to run FS, get the problem, then CLOSE FS before getting the Log. I cannot do anything with an incomplete log. You need to close FS first. Pete
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