Windows Vista Service Pack 2 Expected Tomorrow
arcticstoat writes "After dishing out a few copies of the beta of Windows Vista Service Pack 2 to select customers in October, Microsoft has now decided to let the general public get their hands on the beta of the service pack, starting from tomorrow. The beta of the service pack will be made available via Microsoft's Customer Preview Program on 4 December, and it includes all the updates since Service Pack 1, as well as a few other bits and pieces. Most notably, Microsoft says that Service Pack 2 'improves performance for Wi-Fi connection after resuming from sleep mode,' and adds the Bluetooth 2.1 Feature Pack, ID strings for VIA's Nano CPU and support for the exFAT file system for large flash devices."
Trying to cash in on XP sp2's stigma, they're pushing vista as an aged operating system, that's been through the ropes. Now we've got a mature system, unlike that horrible old Vista RTM, that didn't do well.
Have no fear! SP2 is here! Really, though. It's safe now! It's the standard!
Guys? Guys? Is anybody listening?
Belief? Hope? Preference?The Existential Vortex
Thank God, that really annoys the shit out of me.
Wow, MS actually fixed something! Who would've thunk it?
Who is crazy enough to install a beta Microsoft service pack?
"If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
OK, so they have added a new filesystem for external flash drives...
What about filesystems for the C: drive? It's not like using other filesystems will allow so much interoperability that it encourages switching away from Windows.
So what's wrong? The NIH-syndrome?
It was rumored earlier that they would add tvpack-2008 with SP2, but that's not happening. So no support for un-encrypted QAM, no support for mixing and matching ATSC and QAM channels. Sucks..
The beta is expected tomorrow. The story title forgot that word.
Finally, double glazing for windows vista
Fix the misleading title.
I thought everybody on Slashdot hated Microsoft and used either Mac OS X or Linux. So why do you guys still tell us about whatever Microsoft is doing? (or in this case, speculation as to something they're going to do, which only affects Windows Vista users in particular).
Seriously... Can't they fix Vista's performance problems already? I/O is a huge step backwards compared to XP. Many people have complained. Why don't they profile and fix the damn thing already?!
...about their products that are in beta for lengthy periods.
I, for one, will NOT be installing any beta service packs from Microsoft and I'll be recommending my company do the same. If you were unfortunate to test the SP1 beta, you'll recall that you were forced to re-front your machines after the beta period was over. Until Microsoft guarantees that it will provide a reasonable upgrade path from the beta to production, there is no point in testing until this becomes public.
...I'll buy it only when I can easily crack the fucking "product activation" bullshit, and not a second before.
Ok, does this mean that vista will finally let me use my stereo Bluetooth headset to listen to winamp? I bought this thing for music, only to find out vista doesn't do stero a2dp, I think it is... Apparently having that is up to the chipset driver writers. I got a dell BT keyboard/mouse combo, which is a rebranded Logitech one... doesn't work out of the box. From what I've read you can download alternative drivers for the same chipset (widcomm) that are from another manufacturer (toshiba) or you can try your hand at 3rd party drivers (blue soliel) but you have to pay. Have you ever seen a DEMO DRIVER! It times out after 5MB of data has been pushed! Oh, and this 2.1 stack has been out for a while now, but only to OEM's who wanted to package it for customers. Well, Dell didn't seem to think it was worth it, neither did logitech. So, I can't really tell if it's going to help me or not. Frustrating.
Do not meddle in the affairs of sysadmins, for they are subtle, and quick to anger.
I've been using vista at home since RTM. Was having issues until my most recent reformat in July. Now Vista runs happily on my main home machine (C2D E8300 w/3GB RAM and 6mo old Motherboard) and my mediacenter (AMD x2 5000+ 3GB RAM and some HP motherboard). I've had issues here and there but mostly related to either old software or hardware that has no updated drivers.
At work though, its a different story. Using the management console to connect to 2k3 servers is, well, odd. Missing options (like properties so you can reboot via advanced settings on the Terminal service crashes), annoying updated admin tools that really don't seem to be meant for 2003 and again, incompatibility with various older business applications. Also have this pain with the USB dock for my Lenovo X300. The USB dock is connected to a usb lan device and vista will at times not identify the network until I disable and reenable. New drivers haven't helped. Not sure if its a Vista issue with USB or just bad driver implementation.
Personally, I think they should move back to XP or XP-like with some vista upgrades for business. Like back in the day when you had business and home versions of windows (NT days). To me, it makes more sense.
The additional I/O overhead in Vista, which seems to be partly related to internal mechanisms to prevent "wiretapping" media streams by kernel components, is hardly going to show up in idle CPU overhead. I can not comprehend the confusion in the mind that would lead to someone supposing otherwise.
I don't get it. Why are people installing beta software?
Beta should be for beta testers. If a company releases beta software and you're silly enough to install it, you should expect it to run...like beta software. For an OS, that means you should assume it will destroy your system and eat your data. Are you installing this on a disposable "test" machine?
Honestly, Given the sorry quality of released software, I can't understand why people are rushing to blow up their computers with _pre_release software.
"People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
Can someone explain why "masturbation" is a tag for this story? Is this an inside joke or something?
If you don't know where you are going, you will wind up somewhere else.
Stop the presses, everyone, a real world expert, ravepunk, has spoken, and he is putting his foot DOWN. No-one in his company will be installing the beta of SP2 after his horrible experiences with the first SP beta, because he had to re-install machines to upgrade to SP1 fin... wait, what? You're the decision maker for a company in this regard, and you decided to place a beta service pack for something as fundamental as the operating system on actively in-use machines, and were shocked to find that there maybe have been changes between the beta and production release that couldn't easily be reverted? I'm not sure what's worse, the fact that you expect "upgrade path" trouble-free beta installs of an OS, or that perhaps you don't have a test machine/network/virtualization and felt compelled to install this on production machines, or that seemingly you think your actions played no responsibility in any of the above.
Used to be "Windows ain't done 'til SP1", then XP broke that and Vista followed suit. Question now is is Vista "done" like XP was with SP2 or will it be "Vista ain't for me 'til SP3"?
will be complete when they finish pushing out all the automatic "updates" that slow XP down below its current, tragic level.
It has been said before, and I love to repeat it:
"The day M$ makes a product that doesn't suck is the day they start making vacuum cleaners".
Prior to SP1 I used ICS to share my connection with my PS3 from my laptops ethernet, due to the fact that wireless speeds from my PS3 are wretched even though my signal is 100%. After 'upgrading' to SP1 I found that the speeds from ICS were worse than the speeds I used to get using the wireless on my PS3.
I doubt SP2 will restore the connection to what it used to be...
Posting this on the off chance that anyone has a solution/work around for either fixing the PS3 wireless or the ICS issue.
Cheers
Kevin
Anyone with any brain knows that in order to determine with any degree of certainty you need to test under real-world conditions. Real-world conditions include things like identifying beta users in several departments of a large company and allowing them to run beta software in order to test for the masses. Testing under virtualization is just smoke testing - verifying that your users don't have any serious difficulties with the new OS. Vista has a "burn in time" - from initial installation to some level of full capability. The file indexing database, for example, is a serious piece of technology which requires days upon days of use in order to reach a steady state. As operating systems become more complex and include more heuristic features, testers who take the attitude of just virtualizing and following a script will find themselves with more of a support headache than testers who opted to not only script test, but also put the beta product in real-world situations and find any issues.
... and here's where we went wrong with SP1: Don't believe the vendor when they tell you there will be an upgrade path from SP1 Beta to SP1.
Real-world testing uncovers many more issues (and more complex issues) than virtual script testing can ever hope to. This is, in fact, one reason that Microsoft chooses to release betas to the public.
In testing a beta product, a certain amount of resource overhead should be calculated in order to effectively allow for testing. For something as wide-ranging as an OS release, 10% of a beta user's time would need to be allocated to work with tech teams in diagnosing, reporting, and working around problems that are uncovered. Once the beta period is complete, I expect users to be able to upgraded to production with a minimal hassle. During SP1, we had users that were down for more than a day - not to mention loss of productivity post re-installation due to the OS's burn-in time.
I won't say that this approach doesn't have risk. Of course the action of placing real-world users on a beta product has profound implications especially with respect to an OS product.
Some ways to reduce risks associated with users running beta software under real-world conditions are:
- Smoke-testing in virtualized systems prior to even allowing the beta to continue. Pay attention to "show stoppers" AND their potential aggregate effects. Don't ignore issues because you think you have a work-around.
- Build contingencies for disastrous events (such as backing up or replicating offside more aggressively than for typical users).
- Have a reversion plan tested and in-place prior to beta go-live.