Yes but if they are endemic of the original genetics of the install program's DNA like blueprints, then in reality it really is OUR Vendor's problem and responsibility to deal with this properly once and for all. As Steve just said above this is happening on all of the various OS's because it is AC herself that is installing an older and not cooperative, does not play well with other version of the piece of the puzzle.
So my question here again is, since you guys seem to actually "Understand" this and can properly explain it and convey the correct stuff to others at AC who would understand likewise, Has anyone, have any of you Tech Savvy folks contacted AC directly and let them know your research and findings? It's time to put this Monkey to bed already... Please....
Paul
I'm confused as to how this would be your vendors (AC) problem. This is an operating system specific error, this in no means, has anything to do with AC software. I deal with XP operating systems all the time with this error.
