A
Anne Onimos
Every time I make a remote connection from my Win2K at work to my WinXp Pro
at home, I get the message "RDP Clip Monitor has encountered an error and
needs to close". The error signature info is "AppName: rdpclip.exe
AppVer:5.1.2600.1106 ModName lameacm.acm ModVer: 0.0.9.0 Offset: 0005d0f1"
Oddly enough, the rdp clip functionality seems to work until I clear the
error message from the screen. That is, while the message is on the screen,
I can copy from the XP session and paste in the 2K session. Once I've
cleared the error from the XP screen and terminated the session, the
mstsc.exe process on the Win2k box does not stop, and the app receiving the
paste will hang until I kill the mstsc.exe process.
Any ideas on how to stop this? I don't really need the functionality, but
the error is really annoying, and seems to leave the XP session in an
unstable state (I get random crashes sometimes after it occurs).
Thanks in advance for any assistance.
Anne Onimos
at home, I get the message "RDP Clip Monitor has encountered an error and
needs to close". The error signature info is "AppName: rdpclip.exe
AppVer:5.1.2600.1106 ModName lameacm.acm ModVer: 0.0.9.0 Offset: 0005d0f1"
Oddly enough, the rdp clip functionality seems to work until I clear the
error message from the screen. That is, while the message is on the screen,
I can copy from the XP session and paste in the 2K session. Once I've
cleared the error from the XP screen and terminated the session, the
mstsc.exe process on the Win2k box does not stop, and the app receiving the
paste will hang until I kill the mstsc.exe process.
Any ideas on how to stop this? I don't really need the functionality, but
the error is really annoying, and seems to leave the XP session in an
unstable state (I get random crashes sometimes after it occurs).
Thanks in advance for any assistance.
Anne Onimos