Web Kracked wrote: > bg wrote: >>>> Rob Clement wrote: >>>>> I am running Ooo 3.1.0 under Vista. I onstalled the program >>>>> earlier today >>>>> and it ran fine. I switched off my computer as I was going out for >>>>> a while >>>>> and then I came back and rebooted I started up OOo 3.1.0 and was >>>>> asked if I >>>>> was prepared to take part in a project to help improve OOo. I >>>>> clicked on the >>>>> OK button and since that OOo has not functioned. When I double >>>>> click the >>>>> icon nothing happens. >> >> Brewster replies: >> >> My theory is, Vista saw that you were running a non-MicroSquish >> office suite, and decided to punish you by giving you some grief. >> >> I'm only half kidding :-) >> >> Brewster > > half kidding? > there are people who thing somewhere in the OS, there is a little > script that does look for such non-MS stuff and will not let it > call the OS routines properly someway, somehow. I think MS would > see if they could get away with that.
Actually, they have tried that a few times in the past. I had mentioned DR-DOS, someone else mentioned the PowerQuest boot manager, then there was the bogus error message when DOS CD drivers found they were being run under OS/2. Then you've got the hidden APIs, that gave MS apps an advantage over the opposition. This one was found by Borland. There are many other examples of Microsoft deliberately interfering with interoperability, to force their advantage. Microsoft is one company you cannot trust to work fairly with others. The further the world stays from MS "standards", the better. For more on OOXML vs ODF, read up on the recent news, where MS is trying to get Rob Wier out of the ODF committee and compare with how they used similar tactics to force OOXML through ISO. -- Use OpenOffice.org <http://www.openoffice.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
