Hi Jonathan,
Thanks for your reply. Ya know, that's a good question. Being that the
contact I'm referring to is my 92 year old dad, I suppose anything is
possible. If I understand you, I think you're suggesting that I'm running
Windows Live Messenger while he's still running an older version, the one
before Live was available? Wasn't the Handwriting Tab available in the older
version? Seems I remember using it before I upgraded. Either way, there was a
time, about a year ago that I could send handwriting to him and he was
receiving it. Perhaps both of us have to be running the same version? Still a
bit confused and I guess I don't fully understand the main difference between
Live and Net. Could you elaborate a little more?
TIA,
Barb
"Jonathan Kay [MVP]" wrote:
> Greetings Barb,
>
> This message typically appears if your contact is not using the real Messenger client. Are
> you sure they haven't switched to something else (that just supports the .NET Messenger
> network)? Trillian, Pidgin, etc. come to mind.
>
> --
> Jonathan Kay
> Microsoft MVP - Windows Live Messenger
> MSN Messenger/Windows Messenger
> MessengerGeek Blog: http://www.messengergeek.com
> Messenger Resources: http://messenger.jonathankay.com
> (c) 2008 Jonathan Kay - If redistributing, you must include this signature or citation
> --
>
>
> "artgal" <> wrote in message
> news:88574F1E-C4F8-445A-8E60-...
> > Hi group -
> > I'm having a problem using the Handwrite Tab, not sure why because it used
> > to work just fine. When I click on the Handwrite Tab and try to use it, this
> > is what happens: The curser remains a text curser and a message is
> > automatically sent to my contact saying "Not all participants can view
> > handwriting, so your messages will be sent as text". The contact I'm trying
> > to send handwriting to is cable of receiving it and has received handwriting
> > from me in the past. I'm using the same mouse (Logitech Wireless). My Windows
> > Live Messenger is version 2008 (Build 8.5.1302.1018). My OS is WinXP 2002
> > Home Edition SP2. Does anyone have any idea what the fix might be for this
> > issue? I suspect it's just a setting somewhere, but I've looked through the
> > tools and options and can't find anything that would help.
> > TIA,
> > Barb
>
>