Win7 64 WideFS com3 only on client & badly behaving

[mtjoeng]

Win7 64 WideFS com3 only on client & badly behaving

have a moving map on a client running

this worked with Vista 64 on FSX box & Vista 86 on notebook

upgraded FSX box with new Win7 64 & Win7 86 on notebook

(switched to DX10 Preview now, really nice looking)

and moving map (ancient Jeppesen Flitedeck) doesnt work any more

needs to connect to a COM port (preferably COM1 or COM3, but setup would chk any COM)

or 'cannot open port'

or 'no data coming from port'

1 of the porblems might be that WideFS "WideClient 6.899"

in Win7 can only open COM3 (on my client)

"842 Opening GPSout port COM3, speed=9600 -- OK!"

any other port:

"686 Opening GPSout port COM4, speed=9600 -- FAILED!"

and tried COM1 (connecting OK, but no data = a hardware port, oops)

COM2/4/5/7/9/11/13

did a VSPE Pair with 3/4 3/2 3/5, no data

did a MixW_ComEmul, ditto, no data

i suspect it's Win7 'new&improved' security settings, but ..

- i'm giving up (back to Flightsim Commander, oh dear)

anyone has the same problem?

(P.S.

I have a line in my widefs log:

"889 LUA: "F:\WinUPD\FSX\FSUIPC & Widefs\WideClientLATEST\Initial.LUA": not found"

what is this about?)

[Pete Dowson]

1 of the porblems might be that WideFS "WideClient 6.899"

in Win7 can only open COM3 (on my client)

"842 Opening GPSout port COM3, speed=9600 -- OK!"

any other port:

"686 Opening GPSout port COM4, speed=9600 -- FAILED!"

and tried COM1 (connecting OK, but no data = a hardware port, oops)

COM2/4/5/7/9/11/13

did a VSPE Pair with 3/4 3/2 3/5, no data

did a MixW_ComEmul, ditto, no data

i suspect it's Win7 'new&improved' security settings, but ..

No, security settings will have no effect whatsoever on COM port access. If only COM3 is opening with WideClient then you aren't establishing the pair correctly with VSPE or MixW -- both ports in the pair should be openable (providing you aren't already running the FliteMap software), so you should find two possible assignable ports in WideClient. You need to check the status of the pair you are trying to set up in VSPE itself.

(P.S.

I have a line in my widefs log:

"889 LUA: "F:\WinUPD\FSX\FSUIPC & Widefs\WideClientLATEST\Initial.LUA": not found"

what is this about?)

WideClient supports the full Lua plug-in facilities that FSUIPC does, less a few parts only. The "initial.lua" file is an optional plug-in which will run, if present, as soon as WideClient is started -- other Lua files are only run after connection. The message is there to show you that it looked and didn't find the optional file, so it wasn't run. This obviously doesn't matter if you are not using the facilities, same as the message about IPX/SPX if you aren't using that protocol.

Pete