Echostorm writes with word that Windows Vista SP1, which began rolling out via Automatic Update, has left some users' machines unbootable. The update loops forever on "Configuring updates: Stage 3 of 3 — 0% complete. Do not turn off your computer." "Shutting down"... restart and loop. Echostorm notes having found traces of what sounds like the same bug in early beta releases of SP1. It's unclear how many users are affected. So far there is no word on a fix from Microsoft.
I think their test setups are entirely Hetero, dude. However, it's rather difficult to have every possible machine configuration represented. I mean, think of the permutations! Why won't anyone think of the permutations?
yeah exactly... its called beta testing. Where you literally give it out to people and say this might not work... and if it doesnt tell us and we'll fix it.
They actually DO beta test their software, right??????????
They did test it in.au and even did a survey to see what people thought of it. Oddly enough everybody thought it was the best thing since sliced bread.
"I'm not the author of the grandparent post, but the constant spew of memes only adds to the overall noise and lack of actual content. I don't see how something that is chanted 500 times is still funny. It becomes trite, expected, and tired."
You sound like you'd be happier with Technocrat.net. Decidedly fewer trolls and 12 year old fanboiz there. I lurk, but don't really post much.Give it a shot.
Just a few days ago with OS X 10.5.2. Several users were complaining of being stuck at the BDOS during boot, slow booting, etc. It seems that there are quite a few issues with 10.5.2, I myself have noticed apps starting much slower since the update. However, for the most part, it's very usable for me. Others however cannot even run some critical apps and has brought them to a complete halt. Not good at all. From what I have read and the trouble I had with using the Software Update version of the update, they needed to test more. I had to use the combo updater just to get the thing to install at all. Now, mod me over-rated.
I know that they're said to have copied the concept of a GUI from apple (who, yes, stole it from PARC) but I didn't think Microsoft would follow the iBrick update also.
the use of irony to mock or convey contempt : his voice, hardened by sarcasm, could not hide his resentment. See note at wit.
ORIGIN mid 16th cent.: from French sarcasme, or via late Latin from late Greek sarkasmos, from Greek sarkazein 'tear flesh,' in late Greek 'gnash the teeth, speak bitterly' (from sarx, sark- 'flesh' ).
Seriously, sounds like a version issue. An SCM (Software Configuration Management). Seriously, I worked for smaller companies that were serious about versioning and regression testing. Is it my imagination or does MS seem more and more like a software organization that is out of control?
more likely they are a software company rolling out tens of millions of copies of an O/S onto completely random hardware. I'd be amazed if there were not a few problems.
Bullshit... The amount of hardware variability has declined over the past 15-odd years due to consolidation and Microsoft's insistence...
* How many CPU makers are out there today? 2. (Transmeta is dead).
* How many companies make chipsets (north/southbridges) today? 4(?)
* GPU makers? 3.
* BIOS vendors? 3(?)
* Sound cards? 2 (Intel & Creative)
* Expansion interfaces? 2 (PCI, PCI-Express)
Now, look back to 1993-1995. How many no-name brand BIOSes caused problems? How many brands of VGA chipsets were there? CPU makers? (Think Intel, AMD, Cyrix, NexGen, C&T,...) How many expansion interfaces were there (ISA, VLB, PCI, MCA). How many brands had their own incompatible hardware, where Microsoft's HIMEM.SYS had special switches for (AST, Everex, IBM PS/2, etc.) All of these worked well with DOS/Win3.x and Win95.
No, this is Microsoft's way of saying "we don't know what's wrong with Vista!"
What are you smoking? S3 is still around. Matrox as well. Then there's Intel, ATi, nVidia, then there's 3DLabs. I think Trident might be around, but only in a pure 2D platform. Cirrus Logic is also still in business, though whether or not they still manufacture GPUs is unknown to myself.
GPU? NVidia has 38 families of chipsets. At ~5 products for each chipset, you're over 190.
What about all of the other hardware on a motherboard? Bluetooth, USB, Firewire, network drivers and modems are some of the largest contributers to OS development overhead/headache; tell me, have you ever tried to load up Feisty Ubuntu using a Broadcomm wireless device?!?
By the way, this doesn't include all of the half-assed components people drop onto their computers like humping dog memory sticks or coffee warmers let alone all of the out of date drivers people have installed on their systems (have you checked your BIOS rev lately?).
This isn't "Microsoft's way of saying 'we don't know what's wrong with Vista,'" it's Microsoft's way of saying, "we're trying our damnedest to clean this up, but you idiots keep pissing in the pool."
Seriously, sounds like a version issue. An SCM (Software Configuration Management). Seriously, I worked for smaller companies that were serious about versioning and regression testing. Is it my imagination or does MS seem more and more like a software organization that is out of control?
It appears that each little division of Microsoft is their own little fiefdom. Take a common DLL - comctl32.dll (common controls). Windows ships with one version. Office ships with another version. Applications (using Visual Studio Redistributables) ship with a third version! Each has features that aren't in the others, so Windows apps get one look, Office another look, and 3rd party apps yet another look.
In addition, the OS team forked the compiler they use from the development team. It makes sense in one aspect - all developers have a stable toolchain. However, if the dev team breaks something, instead of the Windows team making a big stink, people who use Visual Studio do.
As far as anyone's concerned, Microsoft might as well be split up into separate companies - they more or less act that way anyhow. Code's taken from one team and forked, improvements aren't folded back in, etc.
Who modded this Offtopic? The summary says "which began rolling out via Automatic Update", which is just wrong. Admittedly they might want to have caught this a touch earlier, but it's not public yet, nevermind auto updating people's machines. OSS FUD I say...
In fact, all the posts to the thread in the article were made after this article was posted to slashdot and by posters with a post count of 1. They talk about SP1 on auto-update (which the original post didn't) yet that can't possibly be true because that's not the case. And oh look, echostormfury is one of the posters, could he perchance be related to the Echostorm who posted the story? I smell bullshit...
Except for a major difference: unlike the 10.4.11 update, this is NOT a public release and contrary to what the summary is, is NOT available on Windows Update.
Echostorm writes with word that Windows Vista SP1, which began rolling out via Automatic Update, has left some users' machines unbootable.
A forum post from last month about issues with the Vista SP1 Release Candidate (prerelease code, just to let Echostorm know). SP1 does not go out via auto updates until next month, and is only officially available to select system builders and beta testers now.
It's unclear how many users are affected.
I counted 5, including the guy who yanked his power cable and trashed his filesystem.
So far there is no word on a fix from Microsoft.
It might possibly be fixed in the RTM version of SP1. Who knows? Certainly not Echostorm, who is having a poopie because he hosed his own PC and is trying to drum up a whine-fest about it. Definitely not kdawson either, who posted this because, well, it's kdawson.
This is taking slashvertisments to the preschool tantrum level.
of the situation years ago when a patch went that killed ones network connection. The solution from Microsoft? Download a new patch to correct the situation.
A very large number of owners of ASUS P5N-E motherboards are reporting the same issue simply with recent updates. It's quite likely the SP1 update is simply triggering the same issue.
Here's a google search on the issue [google.com]. You'll notice a common thread is that P5N-E owners have the issue, users of other motherboards don't see it.
It's been happening since mid January, from what I can gather, and I'm not finding any solutions to it yet.
That's a dillution of the term "brick", and it's also not true. Except in the case of a really destructive update (as in, corrupts the FS or similar), if an update ever renders my Linux unbootable, I'll just pop in the install CD and use it to roll back the changes.
Certainly not what I'd call an "easy" process -- easy for me, maybe -- but it's by no means a brick.
Vista SP1 isn't available publicly yet, unless you hop on The Pirate Bay.
Microsoft placed 6 weeks between code finalization and public release for 6 weeks of driver testing; some drivers were not properly written, and MS wanted to work with hardware manufacturers/OEMs to find hardware with problems. Everyone bitched about how technical users should get it early.
Then these same people download SP1 from an unauthorized source, and bitch when it breaks their system. They downloaded an update without letting Microsoft work the kinks out, and they didn't get the update from MS. No automatic download was involved in this.
Reading a little more of the forum confirms my theory about it mostly being the Refresh RC 2 ("Which should be the same as the RTM").
I havn't found a single thread about someone saying anything about windows update.
I believe MS said they would not roll it to fully automated updates till they fixes some driver installation problem that was displayed in the RC.
They however failed to tell what drivers were affected, and how you can manually fix it. Yanking the power cord certainly is not the method MS would recommend. It htink you need the install disk and run some kind of recovery mode. (that is how it worked under XP.
The linked forum post is referring to a RC, not to the RTM.
"For broad availability, we are still planning to release in mid-March, since we want to be sure that everyone has the smoothest experience possible.". You can have it earlier if you are want to touch buttons....
You can't make this stuff up. (Score:5, Funny)
Re:You can't make this stuff up. (Score:5, Funny)
There, I fixed that for you.
Parent
Re: (Score:3, Funny)
Only on Slashdot.
Re:You can't make this stuff up. (Score:5, Interesting)
Parent
Re:You can't make this stuff up. (Score:5, Insightful)
Parent
Re:You can't make this stuff up. (Score:5, Interesting)
So, yes. They have quite a large testing environment going on. I know you were kidding, but...
Parent
Re: (Score:3, Insightful)
Re:You can't make this stuff up. (Score:5, Funny)
Oddly enough everybody thought it was the best thing since sliced bread.
Parent
Re:You can't make this stuff up. (Score:5, Funny)
Parent
Re:You can't make this stuff up. (Score:5, Funny)
Oh wait. Never mind.
Parent
Re:You can't make this stuff up. (Score:5, Funny)
In Soviet Russia, memes spew you....
Parent
Re:You can't make this stuff up. (Score:4, Informative)
Parent
Re:You can't make this stuff up. (Score:5, Insightful)
Parent
Taking a leaf out of apple's book? (Score:5, Funny)
ROFLMAO (Score:4, Informative)
Ahhh, Microsoft. Thank you for all the work you throw my way!
The only thing I can confirm so far is yep, Safe Mode don't work.
Re:ROFLMAO (Score:5, Funny)
Parent
Re:ROFLMAO (Score:5, Funny)
Parent
Re:ROFLMAO (Score:4, Insightful)
Parent
SP1 prevents Vista from booting? (Score:5, Funny)
Win a T-Shirt! (Score:5, Funny)
Q: Vista SP1 gets locks up the machines after update.
A: [x] Fiction (wins a T-Shirt)
[ ] Fact (truth but no T-Shirt to you bad boy.)
Re: (Score:3, Informative)
sarcasm |särkazm|
noun
the use of irony to mock or convey contempt : his voice, hardened by sarcasm, could not hide his resentment. See note at wit
ORIGIN mid 16th cent.: from French sarcasme, or via late Latin from late Greek sarkasmos, from Greek sarkazein 'tear flesh,' in late Greek 'gnash the teeth, speak bitterly' (from sarx, sark- 'flesh' ).
Vista is imitating Apple Again! (Score:5, Funny)
Ye who lack faith (Score:5, Funny)
Regression testing, people (Score:5, Insightful)
Re:Regression testing, people (Score:5, Funny)
Parent
Re:Regression testing, people (Score:5, Insightful)
Parent
Re:Regression testing, people (Score:4, Interesting)
* How many CPU makers are out there today? 2. (Transmeta is dead).
* How many companies make chipsets (north/southbridges) today? 4(?)
* GPU makers? 3.
* BIOS vendors? 3(?)
* Sound cards? 2 (Intel & Creative)
* Expansion interfaces? 2 (PCI, PCI-Express)
Now, look back to 1993-1995. How many no-name brand BIOSes caused problems? How many brands of VGA chipsets were there? CPU makers? (Think Intel, AMD, Cyrix, NexGen, C&T,...) How many expansion interfaces were there (ISA, VLB, PCI, MCA). How many brands had their own incompatible hardware, where Microsoft's HIMEM.SYS had special switches for (AST, Everex, IBM PS/2, etc.) All of these worked well with DOS/Win3.x and Win95.
No, this is Microsoft's way of saying "we don't know what's wrong with Vista!"
Parent
3 GPU makers? (Score:4, Informative)
Parent
Re:Regression testing, people (Score:5, Interesting)
Your funny math makes my brain hurt.
The number of vendors is a horrible measurement. Try variants on for size:
How many CPU variants does one of the two manufacturers currently support? Try over 125. http://products.amd.com/en-us/DesktopCPUResult.aspx?f1=&f2=&f3=&f4=&f5=&f6=&f7=&f8=&f9=& [amd.com] Oh, and that's just for the desktop.
GPU? NVidia has 38 families of chipsets. At ~5 products for each chipset, you're over 190.
What about all of the other hardware on a motherboard? Bluetooth, USB, Firewire, network drivers and modems are some of the largest contributers to OS development overhead/headache; tell me, have you ever tried to load up Feisty Ubuntu using a Broadcomm wireless device?!?
By the way, this doesn't include all of the half-assed components people drop onto their computers like humping dog memory sticks or coffee warmers let alone all of the out of date drivers people have installed on their systems (have you checked your BIOS rev lately?).
This isn't "Microsoft's way of saying 'we don't know what's wrong with Vista,'" it's Microsoft's way of saying, "we're trying our damnedest to clean this up, but you idiots keep pissing in the pool."
Parent
Re: (Score:3, Funny)
Re: (Score:3, Funny)
The problem is clearly your imagination. MS has a complete and total grasp on the situation. Their sales rep told me so.
Re:Regression testing, people (Score:5, Interesting)
It appears that each little division of Microsoft is their own little fiefdom. Take a common DLL - comctl32.dll (common controls). Windows ships with one version. Office ships with another version. Applications (using Visual Studio Redistributables) ship with a third version! Each has features that aren't in the others, so Windows apps get one look, Office another look, and 3rd party apps yet another look.
In addition, the OS team forked the compiler they use from the development team. It makes sense in one aspect - all developers have a stable toolchain. However, if the dev team breaks something, instead of the Windows team making a big stink, people who use Visual Studio do.
As far as anyone's concerned, Microsoft might as well be split up into separate companies - they more or less act that way anyhow. Code's taken from one team and forked, improvements aren't folded back in, etc.
Parent
It's not on windows update (Score:5, Informative)
Re:It's not on windows update (Score:5, Insightful)
Parent
Re:It's not on windows update (Score:5, Interesting)
Parent
Don't Panic!!!! (Score:4, Funny)
Brick?!? (Score:5, Funny)
Re:Brick?!? (Score:4, Funny)
Anyway, who cares? I suddenly feel like it's time to can Windows altogether and finally do the switch to Linux.
Parent
For those who say "Get a Mac" (Score:5, Interesting)
Re:For those who say "Get a Mac" (Score:5, Insightful)
Parent
That's some keen fucking reporting (Score:5, Informative)
Echostorm writes with word that Windows Vista SP1, which began rolling out via Automatic Update, has left some users' machines unbootable.
A forum post from last month about issues with the Vista SP1 Release Candidate (prerelease code, just to let Echostorm know). SP1 does not go out via auto updates until next month, and is only officially available to select system builders and beta testers now.
It's unclear how many users are affected.
I counted 5, including the guy who yanked his power cable and trashed his filesystem.
So far there is no word on a fix from Microsoft.
It might possibly be fixed in the RTM version of SP1. Who knows? Certainly not Echostorm, who is having a poopie because he hosed his own PC and is trying to drum up a whine-fest about it. Definitely not kdawson either, who posted this because, well, it's kdawson.
This is taking slashvertisments to the preschool tantrum level.
Repair disk fixes vista problem (Score:5, Funny)
Vista Repair Disk [kernel.org]
I used it as soon as I started having problems with Vista on a new work computer and it's been smooth sailing ever since.
Somewhat reminds me. . . (Score:5, Funny)
Um, yeah.
I call Shenanigans (Score:3, Interesting)
ASUS P5N-E (Score:5, Informative)
A very large number of owners of ASUS P5N-E motherboards are reporting the same issue simply with recent updates. It's quite likely the SP1 update is simply triggering the same issue.
Here's a google search on the issue [google.com]. You'll notice a common thread is that P5N-E owners have the issue, users of other motherboards don't see it.
It's been happening since mid January, from what I can gather, and I'm not finding any solutions to it yet.
Re: (Score:3, Insightful)
Certainly not what I'd call an "easy" process -- easy for me, maybe -- but it's by no means a brick.
Vista SP1 isn't public yet, unless you pirate it. (Score:5, Informative)
Microsoft placed 6 weeks between code finalization and public release for 6 weeks of driver testing; some drivers were not properly written, and MS wanted to work with hardware manufacturers/OEMs to find hardware with problems. Everyone bitched about how technical users should get it early.
Then these same people download SP1 from an unauthorized source, and bitch when it breaks their system. They downloaded an update without letting Microsoft work the kinks out, and they didn't get the update from MS. No automatic download was involved in this.
Parent
Re: (Score:3, Informative)
I havn't found a single thread about someone saying anything about windows update.
Re:Popping Sound (Score:5, Funny)
Sanctus, Sanctus, Sanctus, Dominus Deus Sabaoth Pleni sunt caeli et terra gloria tua...
Parent
automatic updates? (Score:5, Informative)
They however failed to tell what drivers were affected, and how you can manually fix it. Yanking the power cord certainly is not the method MS would recommend. It htink you need the install disk and run some kind of recovery mode. (that is how it worked under XP.
The linked forum post is referring to a RC, not to the RTM.
http://windowsvistablog.com/blogs/windowsvista/archive/2008/02/11/windows-vista-sp1-availability-for-technical-customers.aspx [windowsvistablog.com]
"For broad availability, we are still planning to release in mid-March, since we want to be sure that everyone has the smoothest experience possible.". You can have it earlier if you are want to touch buttons....
windows update is only pushing
the final two of three prerequisite updates needed to install Windows Vista SP1 [windowsvistablog.com]
basically it says you still need 2 more reboots before you can have sp1 automatically.
Parent