DaveNC Posted January 14, 2005 Report Posted January 14, 2005 ****** FSUIPC, Version 3.44 by Pete Dowson ********* Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="" User Addr="" FSUIPC not user registered WIDEFS not user registered, or expired Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=0000B027[0000B027] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=0 6531 System time = 20:10:25 6562 C:\Program Files\Microsoft Games\Flight Simulator 9\ 6562 System time = 20:10:25, FS2004 time = 12:00:00 (00:00Z) 16859 FLIGHTS\other\FLTSIM.flt 16953 AIRCRAFT\c172\Cessna172SP.air 17094 Aircraft="Cessna Skyhawk 172SP" 21156 Client Application: "AS2004" (Id=3412) 21156 C:\Program Files\Microsoft Games\Flight Simulator 9\Modules\ActiveSky2004\AS2004.exe 21156 Product="ActiveSky2004" 21156 Company="HiFi Simulation Software" 21172 Module [M0] "FSAutoStartup.dll" access registration is okay 21187 Module [M1] identified = "ActiveRadar.dll" 21187 Module [M1] "ActiveRadar.dll" access registration is okay 21187 Module [M2] identified = "PMDGOptions.DLL" 21187 Module [M2] "PMDGOptions.DLL" access registration is okay 21812 Module [M3] identified = "FSUI.DLL" 22250 Program [3412] "AS2004" access registration is okay 23578 Module [M4] identified = "FSUI.DLL" 24594 Module [M5] identified = "FSUI.DLL" 37297 AIRCRAFT\Pavehawk\Blackhawk.air 37437 Aircraft="Pavehawk GREY" 39562 Illegal read attempt: offset 0310, size 8 [P0] 39562Program or module not accredited for use with this unregistered FSUIPC 42734 ### IPC Message processed in 3172mSecs ### 44250 Module [M3] identified = "FSUI.DLL" 44250 Illegal read attempt: offset 0310, size 8 [M3] 44250Program or module not accredited for use with this unregistered FSUIPC 44640 Module [M1] identified = "ActiveRadar.dll" Happens each time I click on an aircraft the first time on startup
Pete Dowson Posted January 14, 2005 Report Posted January 14, 2005 21812 Module [M3] identified = "FSUI.DLL" 23578 Module [M4] identified = "FSUI.DLL" 24594 Module [M5] identified = "FSUI.DLL" 37297 AIRCRAFT\Pavehawk\Blackhawk.air 37437 Aircraft="Pavehawk GREY" 39562 Illegal read attempt: offset 0310, size 8 [P0] 39562Program or module not accredited for use with this unregistered FSUIPC 42734 ### IPC Message processed in 3172mSecs ### 44250 Module [M3] identified = "FSUI.DLL" 44250 Illegal read attempt: offset 0310, size 8 [M3] 44250Program or module not accredited for use with this unregistered FSUIPC Happens each time I click on an aircraft the first time on startup It looks like your aircraft has about three gauges which are attempting to access FSUIPC using the external application methods, which have not been "legal" since the special internal access facilities were provided in the SDK in the FS2000 era. The method of identifying the caller so that it can be accredited goes wrong when the wrong entry calls are made. Furthermore, even if your copy of FSUIPC were to be user-registered (which would certainly overcome the illegal access problem), it is still possible for the separate callers to clash with each other, on occasion, because the external entry method depends upon process IDs and they will all be the same for internal gauges and DLLs. Is the aircraft you are using an old one? You say it happens each time you "click on an aircraft", which is ambiguous. Do you mean any aircraft or just this specific one (Blackhawk)? If it is occurring every time, then maybe it is an add-in DLL which is doing it? If you'd like me to investigate further please do this: 1. Before loading FS, edit the FSUIPC.INI file, adding the lines Debug=Please LogExtras=2048 LogReads=Yes LogWrites=Yes to the [General] section. 2. Run FS, but please, for this, do not run any extra external programs like AS2004 -- the Log will get too big. 3. After the error, close FS. Then ZIP up the Log file and send it to me at petedowson@btconnect.com. 4. Edit the FSUIPC.INI file again and remove those lines you added above. Please also tell me what operating system you are using on your PC. Regards, 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