IO cards

[01runway01]

Can anyone help please I have tried so many times to get the IO card (Insim 8000) to be recocognised in fsuicp. I can see it in FSX in settings and I am able to program within FSX however when I try to progrom same button in fsuipc nothing happens. It seems as if FSX does recognise the card OK but FSUIPC does not. any suggestions would be welcome. I have fully registered Fsuipc and widewhich is showing in the FSX moduls. Dennis

[Pete Dowson]

You posted into one of the subforums, where it wouldn't get answered. I've moved your post to the Support Forum.

Can anyone help please I have tried so many times to get the IO card (Insim 8000) to be recocognised in fsuicp. I can see it in FSX in settings and I am able to program within FSX however when I try to progrom same button in fsuipc nothing happens. It seems as if FSX does recognise the card OK but FSUIPC does not.

I do not know the card. What sort of inputs does it provide? Buttons or Axes? What button numbers?

FSUIPC4 uses exactly the same mechanism for reading devices which Windows classifies as 'joysticks' as FSX. I don't know of any way it won't see your card if FSX does.

But please state the Version number of FSUIPC4. If it isn't the current supported version, 4.80, please update first amd try again. Then close FSX and show me, please, the FSUIPC4.LOG and FSUIPC4.INI files from the FSX Modules folder. You can paste the contents into a message here.

Regards

Pete

[01runway01]

Thanks for your reply Peter I forward below the FSUIPC4 log and FSUIPC4 .INI files as requested I confirm I do have the latest versions installed 4.8.Kind regards. Dennis

******** FSUIPC4, Version 4.80 by Pete Dowson *********

User Name="dennis price"

User Addr="d.price1@btconnect.com"

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside FSX on Windows 7

Module base=61000000

93 System time = 17/02/2012 16:54:41

171 FLT UNC path = "\\D-PC\Users\D\Documents\Flight Simulator X Files\"

234 Trying to connect to SimConnect Acc/SP2 Oct07 ...

249 FS UNC path = "\\D-PC\FSX\"

1154 LogOptions=00000000 00000003

1154 Wind smoothing fix is fully installed

1154 G3D.DLL fix attempt installed ok

1154 SimConnect_Open succeeded: waiting to check version okay

1154 Trying to use SimConnect Acc/SP2 Oct07

8314 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

8314 Initialising SimConnect data requests now

8314 FSUIPC Menu entry added

8408 \\D-PC\Users\D\Documents\Flight Simulator X Files\737ng-Gatwick-Day.FLT

8408 \\D-PC\FSX\SimObjects\Airplanes\PMDG 737-800NGX\B737-800.AIR

45973 System time = 17/02/2012 16:55:27

45973 *** FSUIPC log file being closed

G3D fix: Passes 4192, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 2 Allocs, 2 Freed

********* FSUIPC Log file closed ***********

[General]

UpdatedByVersion=4800

History=0QZU1CO5IWGXAPLCFHBWE

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

DeleteVehiclesForAES=Yes

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=3

MinIce=-1

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=No

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=Yes

EnableMouseLook=No

AxesWrongRange=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=No

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

LogWeather=Yes

FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=No

[buttons]

ButtonRepeat=20,10

1=P2,10,C0,0

[AutoSave]

Next=1

Interval=60

Files=10

SaveOnGround=No

AutoSaveEnabled=No

[GPSout]

GPSoutEnabled=No

Port=COM1

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[GPSout2]

GPSoutEnabled=No

Port=<none set>

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[WideServer]

WideFSenabled=Yes

AdvertiseService=1

Port=8002

Port2=9002

[sounds]

Path=C:\FSX\Sound\

Device1=Primary Sound Driver

Device2=Speakers (High Definition Audio Device)

Device3=Speakers (High Definition Audio Device)

Device4=Digital Audio (HDMI) (High Definition Audio Device)

Device5=Digital Audio (S/PDIF) (High Definition Audio Device)

[Profile.beechcraft]

1=Beech King Air 350 Paint1

[Profile.aa]

1=Boeing 737-800NGX PMDG House

[JoystickCalibration.beechcraft]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Aileron=-16380,-512,512,16380

Elevator=-16380,-512,512,16380

Rudder=-16380,-512,512,16380

Throttle=-16380,16380

[Profile.737 microsioft]

1=Boeing 737-800 Paint1

[JoystickCalibration.aa]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Aileron=-16380,-512,512,16380

Elevator=-16380,-512,512,16380

Rudder=-16380,-512,512,16380

Throttle=-16380,16380

[Pete Dowson]

I forward below the FSUIPC4 log and FSUIPC4 .INI files as requested

All those show is FSIPC4 working okay with no recognisable joysticks connected.

I did ask about your "card" which I've never heard of. You say FSX recognises it as a regular joystick, which I find hard to accept at present as there is no response to any on the first 16 IDs (0-15), so FSUIPC doesn't see it.

I asked you what sort of inputs does it provide? Buttons or Axes? What button numbers?

Are you sure it isn't using some sort of driver to send stuff to FS? Depending what it was doing FSUIPC might not see it anyway

Otherwise I'm stumped. I've never met any true joystick device which was not recognisable as such by FSUIPC4. It uses DirectInput, same as FSX, but it also looks up the device in the Registry in order to recover the lower level ID number 9the 0-15 I mentioned). Mybe somehow this device doesn't get the normal entries in the Registry?

I might need to ask you to export some Registry entries for me, But first please get "HIDscanner" here HidScanner, run it and paste the resulting log.

Regards

Pete

[01runway01]

This is not a joystick device, FSX recoginses it as what it is an IO card for buttons,switches not axis. I believe it can also be used for leds. It can not be found in the windows game controller either but it does show in fsx within the control settings and sitches can be programmed. I have clicked onto Hidscanner link this opens in dos I am unable to copy and paste for some reason.

[Pete Dowson]

This is not a joystick device, FSX recoginses it as what it is an IO card for buttons,switches not axis.

That means it is seeing it as a joystick device, also known as a "game controller". Game controllers are the subset of HID (Human Interface Devices) which optionally have up to 32 buttons, 6 axes., 2 sliders and 4 POVs ("points of view, also known as Hats).

It can not be found in the windows game controller either

Ah, that's why FSUIPC can't see it either then. I'm amazed FSX can see it then. That's really weird.

I have clicked onto Hidscanner link this opens in dos I am unable to copy and paste for some reason.

DOS? It isn't "DOS", it's just a console window. But it only shows a real-time copy of the Log file it makes - in the same folder you placed it into. The log is only a normal text file. Surely you can load it into an editor and cut/paste from there, same as the others you posted!?

It has a console log window (same as FSUIPC4 has -- an option in its Logging window) so you can see devices come and go as you plug them in or remove them. It is useful for doing all sorts of HID device chekcing.

Regards

Pete

[01runway01]

Hello Pete, Had problems with copy and paste fo som reason. I have the INSIM 8000 card plugged in which is that last item on this list.. Regards Dennis

********* HidScanner, Version 2.00 by Pete Dowson *********

Device at "\\?\hid#vid_0425&pid_69ff#6&1d133dee&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

Vendor=0425, Product=69FF (Version 0.145)

Manufacturer= Cockpitsonic_UK

Product= Insim_8000_FF

Serial Number= Insim_8000_FF

Usage Page: 1

Input Report Byte Length: 7

Output Report Byte Length: 7

Feature Report Byte Length: 7

Number of Link Collection Nodes: 2

Number of Input Button Caps: 1

Number of InputValue Caps: 8

Number of InputData Indices: 56

Number of Output Button Caps: 0

Number of Output Value Caps: 1

Number of Output Data Indices: 6

Number of Feature Button Caps: 0

Number of Feature Value Caps: 0

Number of Feature Data Indices: 0

Buttons range 1 -> 48 at indices 0 -> 47

Value Y at index 48, range 0 -> 1023, using 16 bits

Value X at index 49, range 0 -> 1023, using 16 bits

Value Rdr at index 50, range 0 -> 1023, using 16 bits

Value Thr at index 51, range 0 -> 1023, using 16 bits

Value Z at index 52, range 0 -> 1023, using 16 bits

Value Sldr at index 53, range 0 -> 1023, using 16 bits

Value V/RY at index 54, range 0 -> 1023, using 16 bits

Value U/RX at index 55, range 0 -> 1023, using 16 bits

**************************************************************************

Device at "\\?\hid#vid_046d&pid_c316&mi_00#8&1951c61b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

Vendor=046D, Product=C316 (Version 40.0)

Manufacturer= Logitech

Product= Logitech USB Keyboard

Serial Number=

Device is a keyboard

Usage Page: 1

Input Report Byte Length: 9

Output Report Byte Length: 2

Feature Report Byte Length: 0

Number of Link Collection Nodes: 1

Number of Input Button Caps: 2

Number of InputValue Caps: 0

Number of InputData Indices: 173

Number of Output Button Caps: 1

Number of Output Value Caps: 0

Number of Output Data Indices: 5

Number of Feature Button Caps: 0

Number of Feature Value Caps: 0

Number of Feature Data Indices: 0

**************************************************************************

Device at "\\?\hid#vid_046d&pid_c316&mi_01&col01#8&18e39d6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

Vendor=046D, Product=C316 (Version 40.0)

Manufacturer= Logitech

Product= Logitech USB Keyboard

Serial Number=

Usage Page: C

Input Report Byte Length: 3

Output Report Byte Length: 0

Feature Report Byte Length: 0

Number of Link Collection Nodes: 1

Number of Input Button Caps: 31

Number of InputValue Caps: 0

Number of InputData Indices: 34

Number of Output Button Caps: 0

Number of Output Value Caps: 0

Number of Output Data Indices: 0

Number of Feature Button Caps: 0

Number of Feature Value Caps: 0

Number of Feature Data Indices: 0

Buttons 45 at index 30

Buttons 1 at index 29

Buttons range 73 -> 76 at indices 25 -> 28

Buttons 64 at index 16

**************************************************************************

Device at "\\?\hid#vid_046d&pid_c316&mi_01&col02#8&18e39d6&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}"

Vendor=046D, Product=C316 (Version 40.0)

Manufacturer= Logitech

Product= Logitech USB Keyboard

Serial Number=

Usage Page: 1

Input Report Byte Length: 2

Output Report Byte Length: 0

Feature Report Byte Length: 0

Number of Link Collection Nodes: 1

Number of Input Button Caps: 3

Number of InputValue Caps: 0

Number of InputData Indices: 3

Number of Output Button Caps: 0

Number of Output Value Caps: 0

Number of Output Data Indices: 0

Number of Feature Button Caps: 0

Number of Feature Value Caps: 0

Number of Feature Data Indices: 0

**************************************************************************

Device at "\\?\hid#vid_192f&pid_0416#7&3314a98f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

Vendor=192F, Product=0416 (Version 2.0)

Manufacturer=

Product= USB Optical Mouse

Serial Number=

Device is a mouse

Usage Page: 1

Input Report Byte Length: 7

Output Report Byte Length: 0

Feature Report Byte Length: 0

Number of Link Collection Nodes: 2

Number of Input Button Caps: 1

Number of InputValue Caps: 4

Number of InputData Indices: 7

Number of Output Button Caps: 0

Number of Output Value Caps: 0

Number of Output Data Indices: 0

Number of Feature Button Caps: 0

Number of Feature Value Caps: 0

Number of Feature Data Indices: 0

Buttons range 1 -> 3 at indices 0 -> 2

Value Y at index 3, range -2047 -> 2047, using 12 bits

Value X at index 4, range -2047 -> 2047, using 12 bits

Value Wh at index 5, range -127 -> 127, using 8 bits

Value Wh at index 6, range -127 -> 127, using 8 bits

**************************************************************************

379924: Device change detected ...

***** This device has been removed:

Device at "\\?\HID#VID_0425&PID_69FF#6&1d133dee&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

386118: Device change detected ...

A device has been attached!

Device at "\\?\HID#VID_0425&PID_69FF#6&1d133dee&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

Vendor=0425, Product=69FF (Version 0.145)

Manufacturer= Cockpitsonic_UK

Product= Insim_8000_FF

Serial Number= Insim_8000_FF

Usage Page: 1

Input Report Byte Length: 7

Output Report Byte Length: 7

Feature Report Byte Length: 7

Number of Link Collection Nodes: 2

Number of Input Button Caps: 1

Number of InputValue Caps: 8

Number of InputData Indices: 56

Number of Output Button Caps: 0

Number of Output Value Caps: 1

Number of Output Data Indices: 6

Number of Feature Button Caps: 0

Number of Feature Value Caps: 0

Number of Feature Data Indices: 0

Buttons range 1 -> 48 at indices 0 -> 47

Value Y at index 48, range 0 -> 1023, using 16 bits

Value X at index 49, range 0 -> 1023, using 16 bits

Value Rdr at index 50, range 0 -> 1023, using 16 bits

Value Thr at index 51, range 0 -> 1023, using 16 bits

Value Z at index 52, range 0 -> 1023, using 16 bits

Value Sldr at index 53, range 0 -> 1023, using 16 bits

Value V/RY at index 54, range 0 -> 1023, using 16 bits

Value U/RX at index 55, range 0 -> 1023, using 16 bits

**************************************************************************

[Pete Dowson]

Hello Pete, Had problems with copy and paste fo som reason. I have the INSIM 8000 card plugged in which is that last item on this list..

The last in the list is also the first. HidScanner recorded it being removed and then reconnected. Look:

First:

Device at "\\?\hid#vid_0425&pid_69ff#6&1d133dee&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

Vendor=0425, Product=69FF (Version 0.145)

Manufacturer= Cockpitsonic_UK

Product= Insim_8000_FF

At end:

379924: Device change detected ...

***** This device has been removed:

Device at "\\?\HID#VID_0425&PID_69FF#6&1d133dee&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

386118: Device change detected ...

Then:

A device has been attached!

Device at "\\?\HID#VID_0425&PID_69FF#6&1d133dee&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

Vendor=0425, Product=69FF (Version 0.145)

Manufacturer= Cockpitsonic_UK

Product= Insim_8000_FF

Did you remove and reconnect it? If not maybe this is one possible reason FSUIPC doesn't see it -- if it isn't connected when it scans.

Otherwise it looks okay, with 48 buttons (or which FSUIPC can only see the first 32), and the maximum of 8 axes/sliders, of which FSUIPC4 should see all but FSUIPC3 only 6.

Buttons range 1 -> 48 at indices 0 -> 47

Value Y at index 48, range 0 -> 1023, using 16 bits

Value X at index 49, range 0 -> 1023, using 16 bits

Value Rdr at index 50, range 0 -> 1023, using 16 bits

Value Thr at index 51, range 0 -> 1023, using 16 bits

Value Z at index 52, range 0 -> 1023, using 16 bits

Value Sldr at index 53, range 0 -> 1023, using 16 bits

Value V/RY at index 54, range 0 -> 1023, using 16 bits

Value U/RX at index 55, range 0 -> 1023, using 16 bits

Are the buttons you've connected within the first 32, do you think?

Please add this to the [General] section of the FSUIPC4.INI file, then run FSX with your device properly connected. You don't need to do anything in FSX, just close it down and show me the FSUIPC4.LOG file please.

Debug=Please

LogExtras=x200000

Regards

Pete

[01runway01]

Hello Pete, I think I have done what you have asked for as below. regards Dennis

*** FSUIPC4, Version 4.80 by Pete Dowson *********

User Name="dennis price"

User Addr="d.price1@btconnect.com"

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside FSX on Windows 7

Module base=61000000

406 System time = 23/02/2012 19:51:12

484 FLT UNC path = "\\D-PC\Users\D\Documents\Flight Simulator X Files\"

827 Trying to connect to SimConnect Acc/SP2 Oct07 ...

858 FS UNC path = "\\D-PC\FSX\"

1716 #### Initialising Dlrectinput Axis Scanning ...

1779 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0425&PID_69FF\Calibration\0"

1779 Found correct "Joystick Id"

1779 ... and a "GUID" value

1794 DirectInput8Create failed, return = 80004005

1810 joyGetDevCaps for device 1 returned error 165 [000000A5]

1810 joyGetDevCaps for device 2 returned error 165 [000000A5]

1825 joyGetDevCaps for device 3 returned error 165 [000000A5]

1825 joyGetDevCaps for device 4 returned error 165 [000000A5]

1825 joyGetDevCaps for device 5 returned error 165 [000000A5]

1825 joyGetDevCaps for device 6 returned error 165 [000000A5]

1825 joyGetDevCaps for device 7 returned error 165 [000000A5]

1825 joyGetDevCaps for device 8 returned error 165 [000000A5]

1825 joyGetDevCaps for device 9 returned error 165 [000000A5]

1825 joyGetDevCaps for device 10 returned error 165 [000000A5]

1825 joyGetDevCaps for device 11 returned error 165 [000000A5]

1825 joyGetDevCaps for device 12 returned error 165 [000000A5]

1825 joyGetDevCaps for device 13 returned error 165 [000000A5]

1825 joyGetDevCaps for device 14 returned error 165 [000000A5]

1825 joyGetDevCaps for device 15 returned error 165 [000000A5]

1825 #### Completed Dlrectinput Axis Scanning

1825 LogOptions=00000000 02000013

1841 Wind smoothing fix is fully installed

1841 G3D.DLL fix attempt installed ok

1841 SimConnect_Open succeeded: waiting to check version okay

1841 Trying to use SimConnect Acc/SP2 Oct07

18283 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N

20015 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

20015 Initialising SimConnect data requests now

20015 FSUIPC Menu entry added

26567 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y

26661 \\D-PC\Users\D\Documents\Flight Simulator X Files\737ng-Gatwick-Day.FLT

26661 \\D-PC\FSX\SimObjects\Airplanes\PMDG 737-800NGX\B737-800.AIR

60201 System time = 23/02/2012 19:52:12

60201 *** FSUIPC log file being closed

G3D fix: Passes 4327, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 2 Allocs, 2 Freed

********* FSUIPC Log file closed ***********

[01runway01]

Hello Pete, Further to my last post I think you were right when you said I did reconnect the IO card. regards Dennis

[Pete Dowson]

1716 #### Initialising Dlrectinput Axis Scanning ...

1779 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0425&PID_69FF\Calibration\0"

1779 Found correct "Joystick Id"

1779 ... and a "GUID" value

1794 DirectInput8Create failed, return = 80004005

Not sure how your post ended up with miniscule typefacing and triple spaced lines. What are you using to view and copy/paste ordinary text files? Try Notepad next time if you don't have any other ordinary text editor.

The problem is there, the failure of FSUIPC to even get DirectInput open for business. It isn't going to see any possible Joystick devices. You device is correctly entered into the Registry as device ID 0, but FSUIPC cannot read it because of that serious Windows problem.

I've never seen this error occur before in this context, but it does signify a Windows error I'm afraid. It is probably some sort of screw-up between the Registry and the WinSxS (side-by-side) library system. The only other times I've seen that error number (80004005) is was when folks had tried uninstalling and reinstalling FSX and getting the SimConnect stuff messed up.

I suspect that some Windows 7 installation or update has gone awry in some way. Try a Windows repair, or just try to make sure your installation is fully up to date.

Regards

Pete

[01runway01]

Hello Pete, I will try and use notepad in future I had used word in this instance. I will try a windows repair and see what happens. I trust you mean my windows installation needs to be updated. I will come back to you soon but thanks for your patience and assistance with my problem I know you help so many people. Kind regards Dennis

[01runway01]

Hello Pete, just a thought would older versions of fsuipc still on my computer cause these sort of problems. regards Dennis

[Pete Dowson]

just a thought would older versions of fsuipc still on my computer cause these sort of problems.

You misunderstand. FSUIPC isn't "causing" any problems, it is suffering from problems on your system. There's something wrong with your Windows installation.

Try running the Windows DirectX update: Microsoft DirectX download page. Maybe that will repair the error.

Regards

Pete