OK, so I've been getting RC1-related questions a lot, both via blog comments and directly over email: Will Microsoft open testing sign-ups again when RC1 is released?
Will the Customer Preview Program be available for those who missed out on Beta 2 to sign up and get RC1?
If I participated in Beta 2 by downloading a PID and the build, will I be able to participate in RC1 automatically?
I know you're excited. So am I -- and I'm using a newer build (5505) ! More news when it's available.
PingBack from http://www.mstechtoday.com/2006/08/10/windows-vista-cpp-rc1-availability-update/
PingBack from http://www.backwhack.com/2006/08/11/windows-vista-rc1-availability-update/
PingBack from http://puntodivista.wordpress.com/2006/08/11/dal-team-di-sviluppo-alcune-faq-sulla-rc1-di-vista/
PingBack from http://puntodivista.wordpress.com/2006/08/11/dal-team-di-sviluppo-alcune-faq-sulla-rc1-di-vista-2/
Is the build number has a particular significance or is it juste a kind of water mark. Maybe a post on build number should be in order :D
PingBack from http://www.winboard.org/forum/news/43363-windows-vista-offentlicher-test-auch-fuer-den-rc-1-a.html#post289301
PingBack from http://www.windowsxlive.net/?p=85
On apprend sur le blog de l'équipe Vista que la RC1 sera disponible au public et automatiquement pour...
PingBack from http://technicalitch.wordpress.com/2006/08/11/vista-rc1/
compugab: Youre right, it's really only significant as a watermark and in relation to Beta 2, which was build 5384.
Will RC1 be first available for technical beta testers and msdn, and later for CPP, or simultaneously?
Vista Release Candidate 1 is coming. No word how soon, but it will be open to new testers. More Vista coupon buzz: Unusual motherboard sales patterns support the idea, according to a Friday report by investment bank Goldman Sachs. The company cited
***Vista Must Have 6 More Months--Someone Needs to Tutor Steve Sinofsky on How Windows Should Work and Nick White’s Launch Team Should be Launching 6 months later than January****
Let's discuss what's essential and vital to Vista that Nick White and Paul Donnelly have not discussed to date.
**Reopening CPP* (aka Sales)
Of course they will reopen it. What is comical and disingenuous is why they would ever have closed it. It's not as if the Redmond campus is out of servers and can’t afford it. The only reason it was closed was to tease the public and whet their whistles and ala-Apple to try to build a sales mystique.
Cutting off public downloads was an extension of priming the sales tool with a head fake. There was no reason at all to do so. MSFT has the servers—but it was an imitation Apple move to build cachet and curiosity and to create desire to buy it. You have created a black market on Ebay as well forVista Beta DVDs at ridiculous prices by closing the downloads. At no loss to MSFT you could have kept them open until RC1 goes CPP, and avoided the hundreds of posts for people who forgot their keys or get a corrupt ISO error in Vista who are complaining en mass on your public newsgroups.
MSFT must back off the ship Date 5-6 Months Nick, or they will embarrass Jim Allchin and badly dilute Vista, who has probably contributed as much as anyone to the current Windows OS and server programs, will be embarrassed in his last at bat and MSFT will lose a significant amount of enterprise migrations and individual retail sales. OEM sales increased last quarter by 20% and OEM sales decreased.
I know Ballmer said this cryptically at the financial analyst meeting in late July. It had all the detail of an enigma enshrouded in a mystery.
Ballmer Analyzes Microsoft's 'One Big' Vista Mistake
"We made an upfront decision that was, I'll say, incredibly strategic and brilliant and wise -- and was not implementable," Ballmer said. "We tried to incubate too many new innovations and integrate them simultaneously, as opposed to letting them bake and then integrating them, which is essentially where we wound up."
Can you explain and elaborate to your customers what this mistake is (I believe it was a broad agenda that developers found hard to implement concomitantly), but a lot of people would like to understand what Steve Ballmer meant. It would be a great MSDN Channel 9 topic for an interview, and would give your customers insight into how Windows is projected and envisioned and the process towards implementing that vision..
Right now the Vista team developers must be going nuts there as they see principle after principle compromised by panicky PMs and Windows Platform VPs who just want something out and slapped into a box as the code is not debugged, and major features are not made to work. I think I know now what people mean when they widely write that “Sinofsky made the trains run on time when he ran Office.” He also left a lot of good features on the cutting room floor every version of Office he presided over, because MSFT and Sinofsky believed Office (the cash cow) would be less palatable and less marketable unless it was “dumbed down” for the masses.
***MSFT Restricts Information on Bugs to the Public, and they Fail to Provide Adequate Information on Vista to anyone—the public unwashed or even the TAP tester because the technical writers on teams have failed to do their jobs.
You refuse to give the public access to bugs in any decent way on Connect (despite the fact that you have plenty of SQL, Cluster, Virtual R2 servers and Paul Donnelly has bugs served up to him, sliced, and diced 100 ways to Christmas). To do so would reveal in vivid detail what has been fixed, what won't be fixed, what might be fixed, and what has been deferred when to attempt fixing.
Typical comments on your public Vista newsgroup:
“Have raised lots of bugs, and get closure and/or feedback reports most days regarding vista bug reports I have submitted, however, I am not on Connect Vista, so cannot view or the reqested followup comments, because I got my Vista via MSDN CTP. If someone can help from MS, I would much
“I have the same problem and after receiving a reply to an error report and not being able to view the "fix" on Connect I send an error report to Connect and as a reply received a statement that says this will be fixed in
Please stand by”
“If you have the feedback ID numbers I can try to get you the information you
From one of the MSFT MVPs who is by definition on the TBT and trying to help solve the Connect blind alley with bug reporting:
“Several of us have tried that. Good luck, but I think you will get an error. One problem is that almost none of the bugs are posted public and there is no way to change it after it has been filed.”
Several messages are that MSFT is contemplating the problem when people email the near worthless so-called "Connect Help." This is as thoroughly disingenuous as it is contemptuous of your customers. The bugs and their contexts are on many computers and there is no reason not to organize the categories and make them and their fix or lack of fix context public.
There is also this very disappointing aphorism about Windows Operating Systems that has held up in the last three of them, including that 16 bit-32 bit horror show that is now the butt of jokes at some of the live MSFT events , the copiously memoryleaking and character building ME. No subsequent hotfix or service pack, or any kind of update or in the case of ME MSKBs and regedits has ever corrected significant architectural and functional defects in the OS. Essentially what you see will be what you get when Vista RTMs and it could be Windows ME Redux or as some people have called it Windows Apathy, “foggy, tentative, and in disarray” rather than “Clear, Confident and Connected.” It would be very easy to detail this, but you know your way around Vista on the surface of the UI and under the hood, and you see it on your box.
MSFT has chosen to *deliberately cut off educational opportunities* in Vista during the long foreplay to RTM.
Instead of seizing the opportunity to further education and improving learning curves for your customers on the features, and “how tos” of Vista, MSFT closes off Live Meetings on Vista held from 1-3 times per week that go into detail, and closes off nearly every frequent TBT Chat on Vista.
There are a few Technet Live Meetings, but there is no reason to hide the others from public view. Bloggers and Vista site keepers were free to post chats on their sites, but this came to an abrupt halt in June. Why would be a great question. Live Meetings on Vista features have deliberately not been archived for the public to become educated This is a real waste of time. I have no idea if you can access the number of them downloaded from Connect, but it is probably relatively small and the numbers that attend those chats is not large in terms of 2+ million CPP participants and a large additional number of the public that would like to learn Vista’s features. MSFT has deliberately forclosed on education of the public in respect to vista. Nothing remotely proprietary for MSFT is presented at those chats and Live Meetings. Take a look at them Nick.
Instead of furthering education on the features of Vista, MSFT closes off most of the Live Meetings on Vista, and closes off nearly every frequent TBT Chat on Vista. Bloggers and Vista site keepers were free to post chats on their sites, but this came to an abrupt halt in June. Live Meetings on Vista features have deliberately not been archived for the public to become eduated. MSFT has deliberately forclosed on education of the public in respect to vista. Nothing remotely propitiary for MSFT is presented at those chats and Live Meetings. Take a look at them Nick.
There is absolutely no reason that those teaching opportunities should be closed to the public. It runs counter to the culture of the Gates Foundation that promotes education and donates computers and studies educational mechanisms.
Although there is a large budget for technical writers on Beta teams, none of them are producing significant in depth information on key components of Vista that are being made publicly available on MSFT sites.
There is also an unprecedented budget for the promotion of Vista toward RTM. $100 million for Partner resources, and $4-500 million in advertising to Wagner-Edstrom, McCann Ericson Worldwide, and other ad shops. How about a fraction of that to get information out that is quality and detailed on major Vista components like System File Protection, System Restore, and the Windows Repair Environment? You can't find detailed information on those now Nick, and I'm not talking about the Help site, and you know I'm not talking about the very superficial cheer-leading Product Guide that is aimed towards people who are complete novices.
There is an exponentially growing ground swell of MSFT MVPs and widely read knowledgable bloggers, users and frequent news group helpers exhorting MSFT to give Vista another 6 months before RTM. They should heed this for the sake of quality in Vista. There has never been a service pack in Windows since they began in Win 2K that significantly fixed functionality or added many features. They have all been predominantly security driven.
Your own former chief evangelist and MSDN 9 blogger Robert Scoble, who has also been a VB MVP and filmed scores of indepth interviews with Vista team members, (arguably by far your best known ever blogger on the planet and the only one written up by multiple major media outlets) has written at
Looking at Vista
"I’ve been on the betas of every Windows OS since Windows 3.1 and Vista is starting to feel good, but it doesn’t feel good enough to release to the factory in October. It feels like it needs a good six more months than that, which would mean a mid-year release next year."
Paul Thurott has written at
We might call Windows Vista a "train wreck" for simplicity's sake...Is Windows Vista ready?
No. God, no. Today's Windows Vista builds are a study in frustration, and trust me, I use the darn thing day in and day out, and I've seen what happens when you subject yourself to it wholeheartedly."
Ed Bott has sold well over 900,000 copies of MSFT Press' "Windows Vista Inside Out" already. His Inside Out books are read by thousands of MSFT employees to learn about parts of the operating system they are less familiar with.
Ed Bott has agreed with Robert McLaws of Longhorn Blogs that you should hold Vista to fix its systemically broken components. Bott writes in his blog:
July 31, 2006 - 4:44 pm
Robert’s right: Windows Vista needs more time
Vista Needs More Time: The Entry I Didn't Want To Write
“Time For a Sanity Check” by Robert McLaws Longhorn Blogs
Microsoft has been pushing it's developers too hard to meet this deadline, and Vista is too complicated to allow it to be reached. Many people will twist my words and construe Vista's complexity as a bad thing; it's not, just the nature of software development. But that means that new realities have to be addressed in new ways. So I have a proposal for solving this problem and getting Vista out the door in the first quarter, without sacrificing product quality to the God of Everyone Else's Expectations:
"Step 1: Push the launch back 4-6 weeks and launch at the end of February. Yeah, you're going to get A LOT of flack for it. The stock price will probably drop a percent or two. The Slashdotters will go apeshit. But trust me, your long-term issues will be far worse than your short-term ones if the product is not up to par out of the gate."
"Robert McLaws says Microsoft needs to delay Windows Vista. I agree with about 90% of what he says:
"I’ve been defending Microsoft’s ship schedule for Windows Vista for quite some time. Up to this point, I’ve been confident that Vista would be at the quality level it needs to be by RC1 to make the launch fantastic. Having tested several builds between Beta 2 and today, I hate to say that I no longer feel that way."
The author of the Windows Inside Out Books (mine on XP is 1435 pages and I think that MSFT press is connected to the same MSFT that pays you):
"There’s some truly great stuff in Windows Vista, but current builds are not at the quality level they need to be at for a release candidate to appear in the next few weeks. If management insists on hitting an arbitrary January ship date, the results will be disappointing at best, and potentially nightmarish.
Jim, [Allchin] are you listening"
Nick, it looks like the RSS feed isnt updating - anyone else getting this issue or is it another IE7/OL2007 RSS bug!!
Microsoft avait dit que cette version (la RC1)&nbsp;serait uniquement pour les utilisateurs ayant téléchargé...