Quote:
|
Originally Posted by hitchface
Aside from that, my frustration remains with Microsoft for the most part because I think they could go a long way in working with software companies to increase compatibility upon release rather than wait for patches. Sure, the onus is on those providers to create a stable program, but without any type of base to work on, it would be like flying blind. Perhaps the beta programs should extend further so as to include major software companies?
|
You're just assuming that Microsoft develops code in secret and then shoves it down everyone's throats. FYI - there is a HUGE amount of collaboration done between h/w and s/w manufacturers and Microsoft before the release of a major service pack or an OS. You think that MS is lazy or doesnt have enough programmers and thats why it takes them so much time to release SP2 for XP? Hardly the case. All the time goes on testing and retesting to make sure that the broad spectrum of h/w and s/w works right. You'd be surprised to know that MS provides space for the major h/w manufacturers like Intel, AMD, Nvidia etc etc. right on their Redmond campus to make sure that everyone's on the same page. Every s/w manufacturer had access to Vista's beta code so that they could update their products - well before Vista was even called Vista. When you have a manufacturer that isn't up to speed, that really isn't MS' issue, is it? It's just that they haven't done their due diligence.
And this isn't just big name s/w mfgers that throw money to MS to have some sort of an exclusive arrangement. Heck even freeware apps like NOD32 and AVG were up to code before MS partners like Trend Micro released Vista compatible antivirus suites. Is it that they knew someone who gave them Vista's secrets? Or do you think that Microsoft programmers are updating AVG and NOD32 for them? HARDLY! It's just that the people that the programmers have been diligent about making sure that users of their products can move over to the new platform seamlessly.
As
PR mentioned, have you tried contacting your s/w vendor or the developer to find out how they are going to resolve the incompatibilities?