I'm know that more than a few of you have encountered problems with the TIP
after installing the .NET 1.1 update. I've been bringing a brand new Fujitsu
5022 tablet up to speed and downloaded the .NET update over the weekend.
Since then, I've been having all the problems that have been so amply
reported here at the Newsgroup (blank TIP keyboard, missing logon keyboard,
non-operative floating TIP, etc...)

Over the last 24 hours, I've done a lot of reading and uninstalled the .NET
update, which has largely restored the TIP... but not entirely.

So, that leads me to ask: Is anyone aware of a comprehensive fix for this
problem, or is the jury still out?

Looking at past threads, several fixes have been proposed, but nothing seems
to work consistently:

* Do a system rollback, turn off anti-virus, do a reinstall, or...

* Go to Language and Settings in the Control Panel and reset the language
settings for consistency, or...

* Use Run to reinstall two key TIP .dll's, or...

* Do what looks like a really scary forced reinstallation of about 8 or 10
data files including finding them and expanding them from the XP installation
CD...

Can anybody tell me what the latest story on this whole situation is...?
Thanks in advance.

(To answer the inevitable questions, I am running a relatively new copy of
Windows XP with SP2 already incorporated by the manufacturer. Early on, I
loaded NAV 2005 (with firewall). Thereafter, I'd download and install a few
Windows updates each evening, and yes, I forgot to turn NAV off on the
evening that I did the .NET 1.1 update. Native language is English and I do
not have any language updates installed. I tried the Language and Settings
"fix," but none of the problems changed or improved. I then uninstalled .NET
1.1, which is where I am now. TIP function has mostly been restored, but IE
will frequently not accept a password from the TIP (will in KB mode, won't in
Word Pad mode). I'm seriously considering a system rollback to before the
weekend, then rebuilding the updates all over again. If I run into problems
with .NET again, what's the best current fix...?)