| ??? 03/04/10 01:26 Read: times |
#173810 - Blame-shifting Responding to: ???'s previous message |
It's basically blame-shifting/backside-covering.
There's a specific set of hoops that you can jump through to get your software "qualified" with this "Windows Logo" stuff - and that may or may not result in it being any more or less unstable than anything else. a) is this Redmondian bullshit? probably mostly; although it might cause you to question NXP's commitment in not bothering to do it "by the book" - have they really Done The Right Thing everywhere else, and just not got the final rubber stamp, or have they also skimped other things...? b) if not will an uninstall take care of problems that may occur? Hopefully, one of the things that the "logo testing" would verify is that the uninstall does, in fact, work properly - but even "qualified" stuff is renowned for leaving the odd bits lying around... Definitely worth setting a Restore Point... |
| Topic | Author | Date |
| wanting answer from an unbiased forum ... | 01/01/70 00:00 | |
| Blame-shifting | 01/01/70 00:00 | |
| A Lot of stuff Says it | 01/01/70 00:00 | |
Microsoft too | 01/01/70 00:00 | |
| Big pile of BS. | 01/01/70 00:00 | |
| You are on your own | 01/01/70 00:00 | |
| I thought you were on your own when you installed Windows? | 01/01/70 00:00 | |
| Backup Registry First | 01/01/70 00:00 | |
| Use the System Restore feature instead. | 01/01/70 00:00 | |
| Just how would you do that? | 01/01/70 00:00 |