Problem with Keysend on windows Vista

[djlidgley]

Hi Peter

Appologies if this subject is mentioned somewhere else that I have missed, in which case please could you send me a link.

My problem is that the keysend facility does not appear to work within Vista.

I have the latest versions of FSUIPC and WideFS for FS2004 both registered and I am running FS2004 on a windows XP sp3 system.

I have wideclient installed on another XP system and as a check put in the same keysends whick work fine.

On the Vista machine (laptop) WideClient connects OK and launches 2 apps using runready.

I then try to send the keysends to one of the runready programs but nothing happens.

I have tried loading Notpad with runready as a test and nothing is recieved there either.

I have noticed that ActionKeys=Yes is removed from the wideclient.ini files when wideclient runs or shuts down and is not in the new tech pdf file. I assume this no longer required.

Any help would be appreciated.

Dave Lidgley

[Pete Dowson]

My problem is that the keysend facility does not appear to work within Vista.

I have the latest versions of FSUIPC and WideFS for FS2004 both registered and I am running FS2004 on a windows XP sp3 system.

I have wideclient installed on another XP system and as a check put in the same keysends whick work fine.

On the Vista machine (laptop) WideClient connects OK and launches 2 apps using runready.

I then try to send the keysends to one of the runready programs but nothing happens.

I have tried loading Notpad with runready as a test and nothing is recieved there either.

Hmm. strange. I don't know of anything in the normal Keyboard messaging that has changed in Vista. Could you show me the WideClient.INI file please?

I have noticed that ActionKeys=Yes is removed from the wideclient.ini files when wideclient runs or shuts down and is not in the new tech pdf file. I assume this no longer required.

No need to "assume" anything. If you refer to the History document supplied, you will find:

Version 6.50 (August 2005—there were no versions 6.48 or 6.49) includes these changes:

...

• The parameter “ActionKeys” is now abolished. All WideClients listen for KeySends automatically.

Regards

Pete

[djlidgley]

Thanks for the very quick responce.

This is the contents of my wideclient.ini file as requested.

[Config]

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port=8002

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

Window=75,81,601,491

Visible=yes

ServerName=192.168.0.3

Protocol=TCP

; -----------------------------------------------

[user]

log=errors+

runready1=C:\pmGAIFR\gaifr.exe

runready2=C:\Program Files\FSBarIndicators\FSBarIndicators.exe

Keysend1=49,8,runready2

Keysend2=50,8,runready2

Keysend3=51,8,runready2

Keysend4=52,8,runready2

Dave Lidgley

[Pete Dowson]

Thanks for the very quick responce.

I've just tried it here with Vista Home Premium running on by notebook, and it works fine.

This is the contents of my wideclient.ini file as requested.

...

runready2=C:\Program Files\FSBarIndicators\FSBarIndicators.exe

Keysend1=49,8,runready2

Keysend2=50,8,runready2

Keysend3=51,8,runready2

Keysend4=52,8,runready2

Hmm. I just had this:

RunReady1=NotePad.exe

KeySend1=65,8,RunReady1

and it worked fine. So, could it be something about the way you have things set up in Vista? Maybe you have WideClient running with different privileges or something? Although, since it is WideClient running your program it should be able to send it simple keyboard messages.

I assume the WideFS connection is working in other ways, or is it only KeySend you are using it for?

I'm using WideClient 6.763 (from the Downloads announcement above). Just in case there's a difference, could you try that version please?

Regards

Pete

[djlidgley]

HI

The problem is definately something to do with permissions in Vista. I turned of the user account control and everything works fine.

Now the big problem how to sort Vista's permissions with UAC on.

Thanks for your help

Dave Lidgley

[Pete Dowson]

The problem is definately something to do with permissions in Vista. I turned of the user account control and everything works fine.

Now the big problem how to sort Vista's permissions with UAC on.

UAC is a pain, a complete and utter pain.

To start with it is best never to install any non-Vista aware program into "Program Files", because all those folders are protected. Maybe that's part of it. FSUIPC4's installer, when installed into FSX in Program Files, explicitly changes the permissions on the Modules folder it creates itself to allow FSUIPC4 to write its own Log and other files! Ridiculous! Installers can do thisactually any program's whose EXE has "Install" or "Setup" in the name seems to have lots more privileges.

However, I still wouldn't understand why Vista stops the program which starts another (using "CreateProcess") from sending messages to it! Weird!

Check the relative properties of the WideClient EXE against the target program's EXE. Maybe you have one set to run with Admin privileges and the other not. That stops it -- but I've also been informed that that stops the memory-sharing system used for the FSUIPC interface, so I would have thought nothing would connect anyway. But maybe it's one way.

Maybe renaming WideClient "Wideclient Setup Not.exe" would give it the privilege to send messages?

Regards

Pete

[djlidgley]

I will try changeing permissions etc. I did have Wideclient in a folder in Program files but moved it to a folder in c:\ thinking that may have been the problem.

If I do find a solution I'll let you know. In the meen time UAC stays off.

By the way I like the new ButtonScreen. Have to see if I can get a touchscreen monitor like yours.

Thanks again for your help.

Dave Lidgley

[Pete Dowson]

By the way I like the new ButtonScreen.

New? August 2005, nearly THREE YEARS ago? (Version 6.50).

Regards

Pete

[djlidgley]

shows how long since I did an update. Did not need one for the three programs I link on separate systems as all was working well it was only the problem with vista prompted me to see if there was a solution available and downloaded the latest versions in hope.

I've given wideclient folder and exe full permissions but it still does not work with UAC on. Bring Back XP

Dave Lidgley

[Pete Dowson]

I've given wideclient folder and exe full permissions but it still does not work with UAC on. Bring Back XP

Surely the thing needing permissions etc is the target program, the one you awkwardly have installed in "Program Files"? That's the one WideClient is trying to access with messages after all.

Pete

[djlidgley]

Tried that, also moved it to C:\ and set the permissions to full. It does not use the registry so no problems moving it around at will.

Not to worry I'll just leave UAC off for now when I want to use Flight Simulator. I will ask a mate who works in IT to take a look and see if he can figure it out.

Dave Lidgley