Showing posts with label microsoft. Show all posts
Showing posts with label microsoft. Show all posts

2010-02-14

Problematic KB971033 update for Windows7

I recommend that you strongly consider rejecting the manual installation of the Windows Activation Technologies update KB971033, and do not permit Windows Update to install it (this will require that you not have your PC configured in update automatic installation mode, which has other ramifications -- so you may wish to consult a knowledgeable associate if you're not familiar with Windows Update configuration issues).

And if at some point in the future you find that the update has been installed and your PC is still running normally, remove the update as soon as possible.

http://lauren.vortex.com/archive/000681.html

2009-05-16

Windows7 UAC whitelist: code-injection vulnerability (and more)

And when I thought the RC for Windows 7 is going to be a hit, it turns out that while running an administrative account, most of original Windows 7 .exe's auto-eleviate their rights by default, without asking user for a permission. Given that many people are accustomed to run on administrative accounts, this poses a security hole.

More: http://www.pretentiousname.com/misc/win7_uac_whitelist2.html

2009-05-05

No One Ever Got Fired For Using Microsoft

I dug out a nice writing by helios, from his old blog. Actually this is one of the best his posts that hook me up into reading them. And they are numerous...

http://blog.lobby4linux.com/index.php?/archives/83-No-One-Ever-Got-Fired-For-Using-Microsoft.-Yes-They-Did..html
(note: original site is inaccessible right now, the above link is provided by the Wayback Machine)

Find more interesting readings on the current Blog of helios.

2009-02-07

Logout Vista button required 43 people

I read this once but I lost the URL, and now I've found it! It's an old one, but a good one:

http://moishelettvin.blogspot.com/2006/11/windows-shutdown-crapfest.html

And the moral of this story? Weekly meetings, multiple layers of management and the end result which people still don't like much. Shame on you, Microsoft. :-(

2009-02-01

Good news on ASP.NET MVC

Fine description of MVC pattern implementation in ASP.NET can be found on ScottGu's blog. This post accompanies the Release Candidate of ASP.NET MVC 1.0:

http://weblogs.asp.net/scottgu/archive/2009/01/27/asp-net-mvc-1-0-release-candidate-now-available.aspx

2008-08-10

Microsoft's plans for post-Windows OS revealed

The new name is Midori, and it's going to be a new OS without Windows legacy:

http://www.sdtimes.com/MICROSOFT_S_PLANS_FOR_POST_WINDOWS_OS_REVEALED/About_CLOUDCOMPUTING_and_MOBILEDEVELOPMENT_and_NET_and_SOASAAS_and_SOFTWAREDEVELOPMENT_and_WINDOWS_and_MICROSOFT/32627

I just wonder if any other visionary would create such a new operating system, similarly to what Linus Torvalds once did? And at the same time I doubt it, alas.

2008-06-15

Microsoft works against mankind?

Analysis of why an open source Windows is inevitable contains such quote:

Well, let's just say that, while Microsoft's success was due in large part for being at the right place at the right time, it now finds itself in the way of progress and the betterment of mankind.

While I find it humorous, there is some sad truth in this...

From:
http://temporaryland.wordpress.com/2008/06/12/the-inevitability-of-open-source-windows/

2008-05-31

How Microsoft lost the office file format battle

http://www.linuxworld.com.au/index.php/id;535961040;fp;2;fpid;3
There are two main ways to fail at the standards game: You can create software that handles documents in formats for which no true standards exist, or you can create a standard that exists only on paper and in committee, with no reference software implementation. Amazingly, for all its hype and bluster, with OOXML Microsoft has managed to do both.

I couldn't describe it better. OXML seems to be a dead standard at this point! Even if it it's no longer "MS OOXML" and is managed by ISO. In short: OOXML is defective by design

2008-05-17

Fight Microsoft with their own weapon

So, Microsoft puts out its hand and offers help with porting open-source software, to make it run best on the Windows platform. How mean. Understandable from marketing and business point of view, but mean anyway (and hey, that's my opinion!).

I have a proposal then, a simple one. Since Windows users are already used to trial versions, time-limited, feature-limited, shareware and other pieces of software which they constantly have to "unlock" by using codes found on the net (or keygens), so let it be!

Let's give Windows users what they already know:

1. Limited editions of Free and Open-Source Software for Windows.
2. Full-featured versions, including source code, for all other Operating Systems.


So if someone from Microsoft (or other third-party company) wants to keep working on a port for Windows, let it be. Let them even capitalize on the effort! This way THEY will have to keep up with the upstream. Or if they create substantial improvements, they will HAVE TO release their modified source code (that's the beauty of the GPL license!)

Your offer was insincere, so you won't get what you asked for.
Have it your way, Microsoft!

Ballmer: We'll outsmart open source

http://news.zdnet.com/2100-3513_22-959112.html

"Linux is a serious competitor," said Ballmer. "We have to compete with free software, on value, but in a smart way. We cannot price at zero, so we need to justify our posture and pricing. Linux isn't going to go away--our job is to provide a better product in the marketplace."

And Thomas Lee said about "most valued professionals" on Microsoft platform:

The [MVP] title is highly regarded. "You are recognized by your peers, not by an exam that you can cheat in." Linux and its community have a symbiotic relationship, he said: "You don't have that same thing at Microsoft, but there are people who are passionate and technical who are committed to doing a great job."


In FOSS, such people are called Hackers, or the White Hats (compare with Black Hat).

Groklaw - Microsoft emails Blender

This should be remembered!

http://www.groklaw.net/article.php?story=20080511115151164

And I have a solution!

2008-05-01

OOXML ISO aftermath in Poland

Not even ordinary people and experts in the field find the OOXML standardization procedure scandalous. Even members of the country standardization committees have concerns. Just read the letter to the president of the Polish Standardization Committee:
http://polishlinux.org/poland/ooxml-iso-aftermath-in-poland/

Here's the original letter (in Polish):
http://jakilinux.org/stuff/pkn/pismo_do_prezesa_PKN_21-03-2008.pdf

And here's the original answer (in Polish):
http://jakilinux.org/stuff/pkn/odpowiedz_prezesa_PKN_na_pismo_21-03-2008.pdf