Windows 7 reliable enough to release?

[echrada]

Earlier today, I read about the latest leaked build of Windows 7 to appear on BitTorrent. The text on the desktop suggests that build 7057 is part of the release candidate branch. With the exception of some new wallpapers and default account pictures, it appears to be mostly unchanged from build 7048, which means most of the RC changes are checked in, and it’s now crunch time in Redmond.

Is Windows 7 reliable enough to release now? | Ed Bott’s Microsoft Report | ZDNet.com

 

[jfar]

Thanks,nice read.

 

[Romulinx2]

Interesting, thanks.

 

[Digger]

wouldnt the security update for 7 be included in 57? This would be ONE huge change... may not be many eye popping changes for a bit.... how much can MS revamp the OS by swapping out places or changing names of things to render a new beta build, some of this is just out right silly if you ask me.... 57 shoulda been the next wrap after the public... instead of 4 wraps in 2.5 months

 

[Digger]

also, has no ONE mentioned how much ram that 7 tends to use? it seems as tho the more you keep putting in there, the more 7 keeps wanting to use. For example on that read, guy has 4gig, and only 875 free???? omg is all i can say

 

[black dog]

I'm still using Build 7000 and it is easily stable enough for me to use it for my
everyday operating system. I dual boot with XP Pro but only ever boot XP to update the AV and AntiSpy programs.
I am using the 64 bit version with 2 gigs of ram and have no problems at all, even when recoding AVI's etc .
Most reviewers seem to have an agenda or a need to be noticed . I can't be bothered with most of them, and prefer to try things for myself.

 

[Slimy]

also, has no ONE mentioned how much ram that 7 tends to use? it seems as tho the more you keep putting in there, the more 7 keeps wanting to use. For example on that read, guy has 4gig, and only 875 free???? omg is all i can say

Then it's using it right. RAM is supposed to be used by the OS, and when applications need it, the OS gives it to them. That's the beautiful thing about Vista and 7

 

[abuttino]

I see a lot of problems with Win7 and the Media Center and 7048 makes my wifi card crash about once a day. Have to do a "no-shutdown" power-off.

When watching the Media Center and it switches channels for a recording, the "info" screen will not update and it makes you think you are recording a different show.

WTV Converter seems ALMOST stable. I made a script for DVRMS Toolbox that you can find on that site to automatically convert the files and scan them for commercials for removing them while watching or totally removing them.

 

[win7]

Install hangs as it starts on pc with 7057, works fine on laptop.. mmm so i say no way..

Though this has not happened with any previous builds...

 

[wguimb]

Then it's using it right. RAM is supposed to be used by the OS, and when applications need it, the OS gives it to them. That's the beautiful thing about Vista and 7

Man, that was well said. There is not much sense to adding more memory if you're not going to use it.

On Topic, build 7057 is working great for me but it's not ready for RC IMHO.

 

[Firestrider]

also, has no ONE mentioned how much ram that 7 tends to use? it seems as tho the more you keep putting in there, the more 7 keeps wanting to use. For example on that read, guy has 4gig, and only 875 free???? omg is all i can say

The memory usage at idle is based on what programs you most frequently use. The more programs you frequently use the more RAM that is "cached" in both Windows Vista and Windows 7. Overall I say that 7 is smarter with memory caching and has a smaller footprint on memory than Vista did.

Since I mostly use IE, WMP, and Office my RAM usage sits less than 1 GB idle and I have 4 GB installed. I notice a big speedup from opening programs I frequently use compared to my roommate who uses XP with faster hardware.

 

[jimbo45]

Install hangs as it starts on pc with 7057, works fine on laptop.. mmm so i say no way..

Though this has not happened with any previous builds...

Be patient --install on some machines LOOKS like its hanging but can take up to 10 - 15 mins before you actually see the "Choose Language etc " screen.

This seems to take longer on "Better specced" machines with more memory -- you don't even see any Disk activity either so it will seem to some that the installation has actually "Hung up".

Not sure what its doing but just to add to "conspiracy theorists" -- I hope its not making a totally hidden file on your PC whichh eventually will get sent to Microsfoft for whatever purpose.

There's a rumour going around that instead of a "Per Seat" license (and I hate that model as well)

Microsoft want to get a royalty fee based on the NUMBER OF KEYSTOKES made when using something like Office -- beware you have been warned.

Cheers
Jimbo

 

[win7]

Be patient --install on some machines it LOOKS like its hanging but can take up to 10 mins before you actually see the "Choose Language etc " screen.

This seems to take longer on "Better specced" machines with more memory -- you don't even see any Disk activity either so it will seem to some that the installation has actually "Hung up".

Not sure what its doing but just to add to "conspiracy theorists" -- I hope its not making a totally hidden file on your PC whichh eventually will get sent to Microsfoft for whatever purpose.

There's a rumour going around that instead of a "Per Seat" license (and I hate that model as well)

Microsoft want to get a royalty fee based on the NUMBER OF KEYSTOKES made when using something like Office -- beware you have been warned.

Cheers
Jimbo

I waited for quite some time and it has never happened on older builds, and was not even slightly hanging up on my laptop using exact same disk.

 

[Asgaro]

Be patient --install on some machines LOOKS like its hanging but can take up to 10 - 15 mins before you actually see the "Choose Language etc " screen.

This seems to take longer on "Better specced" machines with more memory -- you don't even see any Disk activity either so it will seem to some that the installation has actually "Hung up".

Not sure what its doing but just to add to "conspiracy theorists" -- I hope its not making a totally hidden file on your PC whichh eventually will get sent to Microsfoft for whatever purpose.

There's a rumour going around that instead of a "Per Seat" license (and I hate that model as well)

Microsoft want to get a royalty fee based on the NUMBER OF KEYSTOKES made when using something like Office -- beware you have been warned.

Cheers
Jimbo

Hey, I've also noticed this! Someone else having another possible explanation for this?

First I installed build 7048 on my main pc with the following specs: intel q6600 2.4ghz - 4gb ram - nvidia 8800 gtx.
And after that on an old laptop with these specs: intel celeron 1.6ghz (i think) - 512mb ram - intel graphics stuff.

And I was suprised by the fact I only had to wait about half the time for the "Choose Language etc " screen to show up on the laptop!

 

[win7]

LOL, i am starting to think maybe i was slightly impatient but why would this happen? I have used 7 from 6801 on this machine and not had any issues on any build until now, also this does not happen on my laptop (of lower spec) on any build including 7057.

 

[Barman58]

Hi Win7,

What we have to remember here is we do not know why Build 7057 was built in the particular way it was. Maybe the purpose of it was to test certain parts of the install and start up routines.

AFAIK, whilst 7048 was intended to be a release to certain testers - it was I understand a Beta Refresh for developers - 7057 is probably just a daily build and therefor is likely to have any amount of debug code included.

Often in development you have to take a step back to take three forward. The fact that lots of nice changes were in this build is probably why it was "released"

The only real test will be when the actual RC is released, (or escapes ), I know I am finding 7057 to be a bit less snappy than 7048 but will await the actual RC with interest

 

[win7]

Hi Win7,

What we have to remember here is we do not know why Build 7057 was built in the particular way it was. Maybe the purpose of it was to test certain parts of the install and start up routines.

AFAIK, whilst 7048 was intended to be a release to certain testers - it was I understand a Beta Refresh for developers - 7057 is probably just a daily build and therefor is likely to have any amount of debug code included.

Often in development you have to take a step back to take three forward. The fact that lots of nice changes were in this build is probably why it was "released"

The only real test will be when the actual RC is released, (or escapes ), I know I am finding 7057 to be a bit less snappy than 7048 but will await the actual RC with interest

Yes your right but i was just slightly disapointed as its running great on my laptop and had no problems with any other builds.

Its ok i switched my setup and now for 7 on laptop and vista sp2 on desktop

It won't be long before more builds official or not. I will just have to wait and see if the next one works.

 

[ChudaPati09]

Is it just me,
Or is the boot time gone up.
In Other builds After that new boot video it would go stright to login.
But in this one, a slight black screen with the mouse, in between boot and login.

 

[Barman58]

Hello ChudaPati09

Yes I agree it seems like the delay on vista when they checked for the presence of dual monitors - But as I said above it could just as likely be an enhanced boot log or something similar, It maybe of course something which ignores mobile chipsets hence the issues not being present in laptops.

Only MS know

 

[jimbo45]

Yes your right but i was just slightly disapointed as its running great on my laptop and had no problems with any other builds.

Its ok i switched my setup and now for 7 on laptop and vista sp2 on desktop

It won't be long before more builds official or not. I will just have to wait and see if the next one works.

Don't forget Vista SP2 also expires in MAR 2010 (Co-incidence perhaps ?)

I'm not sure what is to be gained by having VISTA SP2 -- you might as well go the whole piggy (hog ?) hog and upgrade to W7 straight away.

You'll have to do something to th Vista SP2 system anyway before that date.

Cheers
jimbo