Windows 7 RC1 Branch Builds

[Airbot]

Something interesting. The guy is whining but suggests build 7048.winmain_win7rc1.090211-1625 has already been compiled...

News has come down the grapevine that Microsoft has already branched off winmain and started compiling RC1 branch builds, no doubt preparing for the public release of Windows 7 RC. This tells me that Microsoft is far ahead of schedule with Windows 7 development and are going full speed ahead to get this release polished up and done.

This news has come to us in the form of a build tag which sports the typical naming scheme for milestone branch builds. 7048.winmain_win7rc1.090211-1625 is the tag. As you can see, this build was compiled on February 11th 2009 at 4:25 PM. On one hand it is good to see Microsoft moving this quickly with the development of Windows 7, but on the other it is a little concerning. Microsoft have only officially released one build (7000) which went to beta testers and the public alike. One build is not enough to gather enough feedback to move ahead this quickly IMO. Windows is a far more complex piece of software than Office and I hope Mr. Sinofsky can learn that before this beta cycle is over.

more at source: Windows 7 RC1 Branch Builds being Compiled?

 

[Romulinx2]

I have been looking around Microsoft sites.
Hardware developers etc, and it looks like win 7 RC will be released in April?

Just my thoughts, but?

 

[Barman58]

Thanks for the info Aaron

I can't see what the guy is on about with the Public Beta being the only one outside of MS, I'm sure the partners and other semi-insiders have seen later builds than 7000

 

[Paulz0r]

The guy is whining but suggests build 7048.winmain_win7rc1.090211-1625 has already been compiled...

This is part news story and part editorial.

 

[win7]

Let the games begin xD (if true)

But as stated surely not enough feedback yet for RC??

My soundblaster issue is not resolved yet in 7022 (though its fixed by using kxproject drivers), unless such old devices are now disregarded?

 

[jfar]

Oh I laughed when I read that, (hey there’s a chance, it’s not like we’re dealing with the Windows Live team, those people don’t know the meaning of the word feedback).

 

[wguimb]

Oh grow up everybody. Chris is not whining. He is making a very valid point that I agree with. MSFT is keeping the testing of the pre-RC builds close to the nest. It's all based on Mr. Sinofsky's strategy. This is a change that many do not like.

 

[davehc]

Thanks for the info Aaron

I can't see what the guy is on about with the Public Beta being the only one outside of MS, I'm sure the partners and other semi-insiders have seen later builds than 7000

I don't think partners get builds , only viable releases with which they can work to write new drivers etc.
semi-insiders I do not know.
But, my memory fails me, but I think there were only two public (Beta) releases for Vista? As Microsoft, in their wisdom, have decided that a second Beta will not be needed, in view of the succesful feefback on Beta1, it fits the normal pattern.
Don,t forget, also, that there is an official Tech Beta test program ongoing, for those selected - quite a large number of people.. They are feeding back a lot of information from the Beta and subsequent builds.

 

[smarteyeball]

Oh grow up everybody. Chris is not whining.

To a degree he is though. Regardless of the validity of his argument, it does come across as a little "I'm on the TechBeta, but I'm not special anymore-boo hoo". He even admits to 'drifting off into a rant". Ranting/whining is tantamount to the same thing.

It does make you wonder what is being done with a lot of the current feedback data though, if a RC has already been compiled.

 

[benmandude]

This is great news. I tried out build 7000, it was nice. But I think I'll install full time when RC1 comes out.

 

[Chappy]

Well I guess if they've been able to work thru most of the feedback issues so far, and they remain stable..why not start the RC builds.

This thing is pretty darn close to being release-able and they have 1000's of engineers working on it 24/7, so they could possibly be at that point by now. I'm still curious to see what number of known bugs MS will report that the RTM contains. XP had 1500, Vista had 500, and I think W7 will be under 500. Probably 300 or less is my guess

 

[Chappy]

Let the games begin xD (if true)

But as stated surely not enough feedback yet for RC??

My soundblaster issue is not resolved yet in 7022 (though its fixed by using kxproject drivers), unless such old devices are now disregarded?

Don't forget tho, it's not MS's job to build drivers for 3rd party devices, that's Creative's job and until they get an RTM to work with, I doubt they'll have anything soon.

 

[win7]

Don't forget tho, it's not MS's job to build drivers for 3rd party devices, that's Creative's job and until they get an RTM to work with, I doubt they'll have anything soon.

True but they did release a driver through win update, if used its worse than having no sound at all, its useless and they should either fix it or remove it from the list.

I very much doubt creative will support the card for 7 when they didn't with vista.

 

[davehc]

The drivers which MS send through updates, are normally the latest received from the producer. As such, they are often untested by Microsoft..
Many savvy users get drivers from third party sources, other than the original, or have an older driver which is working satisfactory. The MS offers will overwrite these.It is a good precaution to disable the option to automatically download drivers.

 

[win7]

Either way it does not work properly and should be fixed, i have a fix (that actually won't work unless that driver is installed first) but still i fail to see how it would have been creative who made the driver when its not been supported for vista or 7, surely they would not just include the last xp driver hoping it may work?

 

[Chappy]

Either way it does not work properly and should be fixed, i have a fix (that actually won't work unless that driver is installed first) but still i fail to see how it would have been creative who made the driver when its not been supported for vista or 7, surely they would not just include the last xp driver hoping it may work?

You're right there, they wouldn't do that.
And I also can't see Creative getting a driver signed and released thru WinUpdate for a card they no longer support.
So, I have no idea what that driver is for but obviously, it's not for your card. Something must be telling the WU utility the wrng device ID and it's thinking you have something else for a sound card..maybe?

 

[win7]

You're right there, they wouldn't do that.
And I also can't see Creative getting a driver signed and released thru WinUpdate for a card they no longer support.
So, I have no idea what that driver is for but obviously, it's not for your card. Something must be telling the WU utility the wrng device ID and it's thinking you have something else for a sound card..maybe?

Yes i think your right, and the driver from win update is for a broad range of similar cards running the same/similar chipset but its just not the correct one for my dated card.

 

[djhallucn8]

They will get this sorted out before final release I hope.

 

[davehc]

Driver updates sem to be a major issue with most of the 7 builds to date. If your equipment is working OK, then it can be a good idea to turn off the Driver update, through the System - Advanced system settings - Hardware - Device installation settings.
At this stage of Windows 7, perhaps it is better to run with what you have?