Windows 7 RTM

[dangel]

Won't be our time - yanks are behind us so i'm guessing afternoon (would love to be wrong).

MS' servers are probably going to melt though..

[Timmy!!!]

Yep it will probably be in the evening unfortunately. I'm guessing they will make it available during their working day so that's from 5pm for us.

Can't wait to get the RTM though. Can't complain getting it for free via MSDN from the university

[this_is_gav]

Originally Posted by shaithis

I wonder how the Microsoft site will hold up......especially if W2008 R2 RTM is made available at the same time......

I think 2008 R2 is on the 14th or something near that.

[Singh400]

Originally Posted by shaithis

I wonder how the Microsoft site will hold up...

It won't simple as. It'll be brought down, that's for sure. I'd love to see some statistics comparing the demand for Vista vs Seven, including stuff like which country grabbed the most, how much bandwidth was used in the first 24 hours and stuff like that. But I don't think Microsoft publish that kind of info do they?

[Splash]

Originally Posted by Singh400

It won't simple as. It'll be brought down, that's for sure. I'd love to see some statistics comparing the demand for Vista vs Seven, including stuff like which country grabbed the most, how much bandwidth was used in the first 24 hours and stuff like that. But I don't think Microsoft publish that kind of info do they?

Unless I'm much mistaken they'll be using Akamai to manage the downloads, so things *should* be reasonably stable.





*should*

[Singh400]

Originally Posted by Splash

Unless I'm much mistaken they'll be using Akamai to manage the downloads, so things *should* be reasonably stable.

*should*

Didn't they use Akamai to manage the Windows 7 RC & Beta? And IIRC it still crumpled under the demand for a couple of hours.

[Grey M@a]

Could this be the issue why Windows 7 is worse than Vista on my Shuttle:

"The company has blamed a chip-set controller issue rather than a critical bug in the Windows 7 chkdsk /r tool that could cause a memory leak capable of causing your PC to seize up and crash."

Mine does more than crash though, the windows explorer will crash numerous times over and over and then it will blue screen :/

From this source:

http://www.theregister.co.uk/2009/08...w_stopper_bug/

Looks like I am pot out of luck then as Intel still don't have drivers for the x38 and Windows 7 64 Bit. Guess I will have to stick with Vista until I get a new PC built in a few years or Intel get off their backsides and sort it out with a chipset driver.

[this_is_gav]

Originally Posted by Singh400

Didn't they use Akamai to manage the Windows 7 RC & Beta?

Keep in mind that the beta and RC were available to the general public.... many, many times the load that will be experienced here.

Also, it wasn't just the downloads that dragged the system to a halt - the key generation system suffered more, to the point where they started issuing the same 10 keys to everyone.

[Singh400]

I would disagree that this is a show stopper bug. From what I can tell/read/heard, it only releases that much memory if it is available.

A show stopper would be something that complete breaks the system at random or during installation.

Plus, how many people actually use CHKDSK that often? It's nothing that can't be fixed (well nothing to fix imo) with a 0-day patch over WU.

[shaithis]

Originally Posted by Grey M@a

http://www.theregister.co.uk/2009/08...w_stopper_bug/

Looks like I am pot out of luck then as Intel still don't have drivers for the x38 and Windows 7 64 Bit. Guess I will have to stick with Vista until I get a new PC built in a few years or Intel get off their backsides and sort it out with a chipset driver.

As the article says, it not the drivers, it happens within a VMWare Workstation machine using the VM drivers. It's not an Intel (or any other manufacturer) issue.

Have you been runnign "chkdsk /r"?

[Grey M@a]

Originally Posted by shaithis

As the article says, it not the drivers, it happens within a VMWare Workstation machine using the VM drivers. It's not an Intel (or any other manufacturer) issue.

Have you been runnign "chkdsk /r"?

I ended up getting a whole new HD as the HD would crap out, Win 7 would reboot and it did its check disk runs before logging in again. I just can't get Win 7 stable on this Shuttle with the x38 chipset. Intel just don't have the Win 7 drivers for it and the built in Windows 7 ones are shady at best and cause random stutters in games and then the blue screens happen. Roll back to Vista Ultimate x64 and its flawless

I may just end up peddling on the copy of Windows 7 I have on pre-order.

[dangel]

Mine's maxed out at 1,993,324k without error - i have read it's designed to use a lot more memory to speed things up. Looks to me it's hit the memory process limit..

[Grey M@a]

Well currently with the Win 7 RTM from work, its still massively inferior to Vista Ultimate 64 for me. Until it's stable or Intel actually decide they may want to support chipsets they got shot of within 3 months with newer chips, Windows 7 will be shelved or binned for me. Gone are the days where I can be bothered to spend weeks on end tweaking and testing every little last thing to get it working.

[Timmy!!!]

Originally Posted by Grey M@a

I ended up getting a whole new HD as the HD would crap out, Win 7 would reboot and it did its check disk runs before logging in again. I just can't get Win 7 stable on this Shuttle with the x38 chipset. Intel just don't have the Win 7 drivers for it and the built in Windows 7 ones are shady at best and cause random stutters in games and then the blue screens happen. Roll back to Vista Ultimate x64 and its flawless

I may just end up peddling on the copy of Windows 7 I have on pre-order.

You may have done this already but try using the windows vista drivers under win 7 - the driver model is incredibly similar which is why 7 has been so stable for the vast majority of people. Also how much ram are you using? If you're up to 8 gigs then on some chipsets the northbridge needs a little more voltage to stabalise it. Before doing this check temperatures as well to see if everything is ok. Other than that I'm out of ideas!

Can't wait for the RTM to become available. Any indication of when microsoft are releasing it on MSDN/Technet yet?

[Grey M@a]

Originally Posted by Timmy!!!

You may have done this already but try using the windows vista drivers under win 7 - the driver model is incredibly similar which is why 7 has been so stable for the vast majority of people. Also how much ram are you using? If you're up to 8 gigs then on some chipsets the northbridge needs a little more voltage to stabalise it. Before doing this check temperatures as well to see if everything is ok. Other than that I'm out of ideas!

Can't wait for the RTM to become available. Any indication of when microsoft are releasing it on MSDN/Technet yet?

Tried with the built in drivers, tried with the vista drivers and everything on board the manufacturers all have windows 7 drivers which work great, apart from the Intel x38 chipset which is where the problem lies

[dangel]

Originally Posted by Steven Sinofsky of the small software house known as 'microsoft'

"Hi there…sorry to get dragged into this. Of course always want to investigate each and every report of any unexpected behavior.

In this case, we haven’t reproduced the crash and we’re not seeing any crashes with chkdsk on teh stack reported in any measurable number that we could find. We had one beta report on the memory usage, but that was resolved by design since we actually did design it to use more memory. But the design was to use more memory on purpose to speed things up, but never unbounded — we requset the available memory and operate within that leaving at least 50M of physical memory. Our assumption was that using /r means your disk is such that you would prefer to get the repair done and over with rather than keep working.
While we appreciate the drama of “critical bug” and then the pickup of “showstopper” that I’ve seen, we might take a step back and realize that this might not have that defcon level. Bugs that are so severe as to require immediate patches and attention would have to have no workarounds and would generally be such that a large set of people would run across them in the normal course of using their PC.

We appreciate the kind words that such a bug as above is “out of place” with Windows 7–we’re working hard. We are certainly going to continue to look for, monitor, and address issues as they arise if required. So far this is not one of those issues.

Some have reported (as above) that this specific issue repros and then goes away with updated drivers. We haven’t yet confirmed that either but continue to try. We just kicked off overnight stress testing of 40 machines of variants as reported by FireRx. We’ll see.

Let’s see if we can work on this one and future issues together. Deep breath

–Steven"

Panic over it seems!