Hello Mike, Jhon & wild,
I kenw all to well what wild meant. Being a strong "Ride For The Brand"
man, to me, when you insult one you insult all . Wilde is most likely using
programs not compat. with SP2.
That is looking like the real problem. What irks is that they're from
different manufacturers, and all worked fine under SP1 (I always lose
some programs when changing from one version of Windows to another,
but to lose my top four all at once is very disconcerting).
You can cry about or you can fix it. Wild,
Actually, there's a third option.

I just went back to the original
(with all updates other than SP2), and everything works fine. If I
just ignore SP2, there won't be a problem.
I didn't want to go that route and was hoping that there was some
stupid little thing that I overlooked in installing SP2, but (alas!)
it looks like SP2 just isn't an option.
you will have to go deeper into programs thagt are compat.
with SP2 or drop SP2 altoghter. Ms has the info it takes work to find it.
It simply isn't economic for me to replace what I have with programs
that are SP2 compatible -- if I'm going to spend over $2000 for new
programs, ones that might not work on the next item in the MS product
line, it makes far more sense to switch over to Linux which will
maintain compatibility (or at least is open-source enough that I can
go in and make alterations ((I knew there was a reason I kept my
manual for C programming under Unix!!! ;-) )) ).
Best of luck to all,. Ron J
Thanks for all your time and effort -- pointing out that I didn't make
any obvious mistakes saved me from many hours of head-meet-brick-wall.
Much appreciated.