"jstaclwn" <> wrote in message
news:E8530FFA-D5DC-4501-8BE2-...
> Dear Mr. Arnold:
>
> I think if you ahd read my post all the way through you would know that
> this
> program says right on it that it IS Windows VISTA compatible and it still
> does not work.
I read your post, and the fact that you installed that non Vista compatible
application and I would assume you uninstalled the solution, it doesn't mean
that it uninstalled all the XP componets like DLL(s) from the machine.
>
> I do not wnat to keep buying programs that won't work. That can become
> incredibly expensive.
>
> If this one is supposed to be Vista compatible then how can I trust what
> is
> and what isn't?
You got other non Vista solutions you have installed on the machine? What's
to say that those non Vista solutions are causing other problems with Vista
solutions, because both types of the solutions share/use common components?
One common component happens to be for XP and a Vista application/solution
is trying to use that component, and it can't and it doesn't work, because
the component was for XP that was installed on the machine, as an example.
My rule of thumb at this time about installing non Vista solutions on the
machine is it's never going to happen with me. I'll either find a Vista
equivalent for the solution or I'll wait until the vendor comes out with
one. But, not one bit or byte from a non Vista compliant software solution
will touch this machine in order to circumvent/reduce potential problems.
If it comes down to I have to go to a legacy non Vista compatible solution,
then I am going to Virtual PC 2007 and approach it that way.
http://www.microsoft.com/windows/pro...c/default.mspx