Pcanywhere F1 key problem

Archive
1

Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.

2

I have been using pcanywhere 11 with no problems until I installed Microsoft Internet Explorer 7.

I am running Windows XP professional.  My remote application is Medical Manager that uses the F1 key

as a PROCESS or SAVE key. After upgrading to IE7, when I press F1 during a remote session(even when IE7 is not running) the Windows help screen pops up over my remote session and I have to close it.  The F1 key code is also sent to my remote app.

 

I wrestled with this and swore at it for a while, searched and found no way to disable the F1 help key.

 

Finally, I figured out this solution:

 

Rename  the file pcAnywhere.chm to pcAnywhere.chm.xxx  in C:\Program Files\Symantec\pcAnywhere

 

It now works the way it did before the upgrade. Should work for others apps that use the F1 key also.

1 Like
3

Hi Cheese_Merchant,

 

I must congratulate you on your very innovative solution to the problem you were experiencing. I am impressed. :-)

 

Incidentally, I wanted to let you know that you weren't the only one who ran into this problem, and in fact we wound up fixing the very problem you mentioned below, but I can't remember whether we fixed it in an update to version 11 or if it was fixed in version 11.5 but we definitely wound up fixing it. (I used to work on the pcAnywhere development team)

 

You should try running LiveUpdate to see if there are any updates for your version of pcAnywhere. If that doesn't do the trick then my guess would be that we wound up fixing that in a later version of pcAnywhere which came out after the version you have now.

 

Thanks for writing in.

 

Cheers,

 

Alan