Comments on: No quick fix for Windows Home Server bug

Microsoft says a patch for a known bug in its Windows Home Server software won't come until June.

[rstinnett]

You can't just snap your fingers...

... and fix code that is buried so deep within the OS itself. As any large software company can tell you that changing one line of code takes several man hours of coordination and testing. I would rather Microsoft take the time to get it right then to rush something to market that could break the entire system.

Considering WHS servers and the OEM OS itself is routinely out of stock, someone is using it. Furthermore, numerous companies have launched WHS versions of their software -- something you don't do if there is no market for it.

[gsekse]

Oh Please...

If this was a bug in the COMMERCIAL side server, every engineer would have been sleeping at the office until it was fixed. It's just another example of MS not using code that works. They didn't want to just use the regular server software without crippling it so businesses would not use it. They just went too far with the hamstring and made it useless.

That is why my home server is a little dedicated box with a linux samba server on it. Small, simple, and reliable. AND... it doesn't try to check the legalities of my files or other such crap. KISS...

[Penguinisto]

Eh?

While it is true that fixing bugs does take time, one would think that with other server products already on the shelves (e.g. Win2k3 Server), they would've had this one hashed out long before RTM.

Maybe if they dropped the DRM?

[i]"Considering WHS servers and the OEM OS itself is routinely out of stock, someone is using it."[/i]

If I only put three of something on the shelves in a market of maybe 1,000 customers, odds are good that it'll be out of stock. ;)

And where are you getting this information, anyway?

[i]"Furthermore, numerous companies have launched WHS versions of their software..."[/i]

Such as ...?

/P

[ittesi259]

You're kidding me right?

While yes, proper patch work takes time and blah blah blah....3 months? Better yet...its a flaw the corrupts files...that NEVER should have been released with that kind of flaw in it. MS has a long established history of removing key selling point features and delaying release dates....this would have been a good reason to delay the release date.

[Dalkorian]

rush to market

Rstinnett posted:

"I would rather Microsoft take the time to get it right then to
rush something to market that could break the entire system."

You mean like they obviously did with WHS to begin with? It's a
home server that corrupts your files, I'd say it wasn't ready when
they released it. Given the history of winblows, I'd argue it'll
NEVER be ready. The last thing Joe Sixpack needs is a server in
the home that's vulnerable to millions of viruses and can be
hacked by any 12 year old! Corrupting files is just icing on the
cake.

[Penguinisto]

Newsflash: Microsoft Produces Buggy Code!

Oh, wait... that isn't news.

Heh.

/P

[ittesi259]

A little unfair

Thats kinda harsh Penguinisto, and remember someone can always point somewhere to say "That Linux product was buggy" or "Look at Apple's fun mistakes" blah blah blah

But yeah, this one is pretty friggin big.

[rapier1]

News Flash EVERYONE makes buggy code

everyone.

[Lee in San Diego]

Cut them some slack Bro

Sooner later everyone pulls a Spitzer and as Rapier says software
publisher has bugs in their code.

No wait, your in Britain right? Sooner or later everyone pulls a Profumo

[Piric]

If you read the report!

If you read what was reported on the bug, was that if you modify a certain files (Quicken, Pictures, Music) on the server it-self and then save the modify work file back to the server you may have problems. To me the server was for backing up my machines and store files that I want others on my home network to be able to use. Not to be used as a working directory for files that would be modify. Now I agree that Microsoft should fix the issue and sorry to see that it will take to June, but rather one fix than two. So you know I was one of the thousands who was a beta tester and I never tried the Home Server in the reported bug fashion. So maybe all us beta testers should be blamed for missing this problem....