Windows 7 Does Not Have A Critical Bug

[...] the whole story here: Ron Schenone aggregated by [...]

[...] See original here: Windows 7 Does Not Have A Critical Bug ~ The Blade by Ron Schenone [...]

Why are you even linking to Randall Kennedy?

That guy doesn’t even bother to research what he’s writing about.

So far he’s written anti-Ubuntu, anti-Linux, anti-Mac, and even a few anti-Windows diatribes just to sucker people into clicking on his articles so thatIinfoWorld can get more ad money.

Actually, it’s not just Kennedy, InfoWorld is crap

Hi Ryan,
Thanks for the info. I’ll steer clear from IW.

[...] Read the original:  Windows 7 Does Not Have A Critical Bug ~ The Blade by Ron Schenone [...]

The lesson time has taught is that Microsoft would never admit there was such a bug, if there actually was one, it would quietly get repaired, with an explanation that included some minor cosmetic flaw repair.

To admit such a bug existed this close to General Release would be anathema to many, especially those at MS. As a matter of fact, this is exactly the type of non-event that might be used to hide such a bug.

I’m not to worried about it. I’m one of those users who hasn’t even heard of that tool and probably won’t be using it, anyway.

After looking at this article and other info out there closer, we have the following:

Running chkdsk won’t ever cause a problem, unless you run it with the /r switch, which verifies every sector on the hard disk exhaustively and tries to salvage data on bad physical sectors of the disk.

Windows never uses chkdsk with /r, it uses chkdsk with /f every once in a while to scan the file system’s overall structure and fix inconsistencies. (Such as after a power outage)

A typical user would probably never invoke chkdsk /r, and likely doesn’t know what it is.

Randall Kennedy admitted he could never get Windows to outright crash.

The problem most likely doesn’t even affect 99% of users because the problem is triggered by a bug in some specific models of SATA controller.

The fact that nobody even ran into it despite millions of people using the technical beta and the release candidate over the last 8 months, and the internal testing, and closed distribution milestone builds shows that this is a fringe issue.

There are things that Windows has been far more stupid about in the past that people have complained about far less, such as Vista not properly supporting Coordinated Universal Time, or the bug that made tooltips go behind the taskbar for no reason that was introduced in Windows 95/NT 4 and not fixed until Windows 7.

You could argue that neither of those cause a memory leak, but having Vista fight Linux over the system clock and make you log out and in whenever it decides to go haywire with your tooltips is every bit as aggravating as a crash.

Why isn’t anyone mentioning all the stupid crap that Windows has done for the last 15 years that Microsoft has finally fixed?

Conflict sells copies. Randall Kennedy is a synonym for “yellow journalism”

All of that being said, I am quite sure that Windows 7 DOES have a critical bug… or 10, or 12.

We just don’t know what they are …yet.

Why bother with this, there are great tools offered by the hardware manufacturers to correct problems than the slow *** CHSDSK method. I for one use the WD Drive tools which has yet to fail me once. However there are some things I would like to see fixed such as the obviously broken DVD authoring tool Windows DVD Maker. The DVD maker app is stupidly easy to use in Vista and it works and it is litterally the only broken part of Windows 7 I have found.

Hi mhz,
Good point! I’m waiting for SP1. LOL

Justine,
Agree.