By Philip Churchill on June 12th, 2008
Badly Coded Add-Ins No Longer Break WHS
Microsoft’s code man Brendan Grant tells us that badly coded add-ins should not break the console no more. How? By some clever code being added to Power Pack 1 that watches out for tabs which take too long or throw exceptions on load.
If either of these occur the Console will stop trying to load it and on the next load of the Console offer the user the choice if they want to continue to try to use it.
Read the full story here.
Share this WHS Article with Others:
This only proves that all those poorly coded third party add-ins were breaking WHS. What’s to believe this sort of thing isn’t going to continue here, as rather than poorly, what about unfavorable, inadequate and sort that are not 100% badly coded?
Why is a paid software application using beta software, copying the free open source community?
Paid software shouldn’t be BETA grade! It’s suppose to be READY…
It would save a lot of time if you applied even the tiniest bit of thinking and logic before you write.
ANY operating system can be brought down (Yes, even your precious free open source OS’s) by badly written BETA software or, for example, even badly written release version drivers.
If a user decides to install BETA software, then they are KNOWINGLY running the risk of potentially causing problems with their system.
For example, if I decide to install a BETA version of my video driver, then if my system crashes because of bugs in my bad video driver, I don’t blame the OS or the manufacturer of the OS – it’s MY fault and MY responsibility because I decided to install potentially problematic software that could cause a problem.
One takes responsibilty for ones own actions. WOW – what a radical concept!
The people who decide to install the BETA versions of the WHS add-ins are not stupid. They know what they are getting into.
On the other hand, since WHS introduced the ability for people to write add-ins for the console should WHS version 1.0 have been more robust in handling hung or buggy add-ins – Yes, it should have been. Microsoft has clearly addressed this now in PP1.
Another stupid arguement over. Case closed.
Jimmy Brown is not the sharpest tool in the shed.
[...] WHS – Badly Coded Add-Ins No Longer Break WHS [...]
@Aaron
Hold on – Are you trying to say that Jimmy Brown is “not the brightest bulb in the chandelier”?
How can that be? He uses Open Source.
No, no, no…..I’m merely trying to say that Jimmy Brown is one shingle shy of a roof and the water is getting in.
Ah, I see. So basically you are saying that Jimmy Brown fell out of the Stupid tree and hit every branch on the way down.
Now I got it. Thanks for clearing that up for me.
Precisely. In fact, if Jimmy Brown was any dumber then he’d have to be watered twice a week.
Windows Home Server software has a very long history of major bugs, defects and flaws in their software.
http://www.support.microsoft.com/kb/946676 and 950190, 939424, 939425, 939758, 939759, 939426, 939217, 939427, 939428 and so on…
Anyone doubting, need only look at Microsoft’s WHS KB articles, and the list just keeps growing bigger all the time!
This is not a hardware fault or virus, these are design faults in WHS!
And YES, as Jimmy Brown stated, WHS doesn’t include the PC backup database in PP1 which was advertised since January!
Microsoft pulls Windows Home Server backup feature
http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9086258
WHS remains NOT READY for the public even with PP1.
I’m part of the public. I use WHS. And it works wonderfully.
These folks (also part of the public) who write about hard drive crashes and stolen computers who have managed to recover their data using WHS, also use WHS, and apparently it works wonderfully for them, too.
I’d say that makes it ready for the public.
And while you’re digesting that, find me another, non-Microsoft solution that performs exactly the same functionality, out-of-the-box, that is bug-free. That should keep you busy for a while.
Peter cracks me up. Hey Peter, while you’re at it, please make sure to provide links to all of the defects that have been logged against the open source applications.
Foe example, FreeNAS seems to be a popular open source backup solution. But OH MY GOD FEENAS BUG NUMBER 1517765 HAS BEEN OPEN FOR ALMOST TWO YEARS AND IT’S A PROVEN DESIGN DEFECT! Oh wow, and then there’s 1720333, 1720588, 1725779, 1755228 and the list goes on!
Here’s the moral of the story: All software products have bugs. Once again, you’re proving yourself not very intelligent.
Peter is another example of why they have first-cousin marriage laws. It is hard to believe that he beat out half a billion other sperm. I think that he is proof-positive that evolution CAN go in reverse.
I bet if you stand close enough to him you can hear the ocean.
Then again, I can say the same about Jimmy Brown. And yet, I don’t have to because odds are they are the same person!
How lame is that!