Mammoth Patch Tuesday planned for next week

[sup3rsprt]

I'm just curious as to WHAT the future update's via MS for Windows 7 will include... but i honestly think the security for W7 is fine..

Then you're in for a surprise. Security patches for years to come.

(Not that security isn't already good, it's just that people will always be trying to hack it and find problems. Believe me they will)

 

[Night Hawk]

GP version is? Wont RTM versions get support like the ones released later?

RTM=Released To Manufacturers The only thing different about the RTM downloads seen for TechNet/MSDN subscribers is the lack of the optical media unless ordering the backup disk to be shipped on the 22nd. Release means released to the manufacturing for pressing to disk.

 

[toughbook]

GP is General Public Release. This is the version that one will buy from MS, or wherever else.

 

[sup3rsprt]

In that case we might as well say GP = RTM

 

[Jordus]

Its a good thing. MS has been shown to be the best OS company in reference to exploit to patch time.

Meaning, how fast they patch an exploit from when its reported to them.

EVERY OS has security flaws, so id rather see patches that fix them than none at all.

 

[sup3rsprt]

Of course. I never meant security updates were a bad idea. I am only answering the question, "What will future updates include?".

 

[Jordus]

Oh i know, i wasnt directly replying to you. It just kind of fell in there like that. lol

 

[Night Hawk]

Any new version will still need time and eventually see the service packs that come out later. One good thing seen with Vista apart from XP by MS there was not wasting time releasing the second service pack in 2yrs. time where XP's SP2 was a 3yr. wait showing they shaved a full year off of the time!

(I guess they needed to get something in gear for a change! :roflmao

 

[sup3rsprt]

The only reason service packs came out so fast for Vista is because it had such a bad rep (because so few people actually liked using it with all of its problems). I doubt that any service packs will come so soon for Windows 7 because it is already highly polished.

 

[Duesco]

Or the service packs will be like, 4 MB.

"We...uh...ran out of stuff to fix. Sorry. Just some security thingies."

 

[sup3rsprt]

As long as they don't take hours to install I'll be happy.

I still wish they were as easy to slipstream as they are in Windows XP. Whenever I do a clean install I would like the service packs to already be built-in the install disc. It leaves me with a much cleaner system.

 

[Night Hawk]

The first service out in a year's time usually rolls up all of the security updates as well as any changes to support something new. For XP the SP1 there broke the 137gb barrier for seeing Windows run a larger primary due to the increased capacities of newer hard drives then.

With 7 one thing new will be as far as hardware support from the start namely the new USB 3.0 standard that will be seen on new boards coming out in 2010. That will require some obvious fixes, patches, updates in some form at some time where the first service pack would be seeing those included. Then you add the security updates for Windows Defender and other things on top of that.

 

[toughbook]

I wonder what time they will start releasing the updates?

 

[toughbook]

Just found the answer. 10:00 AM Pacific.

 

[swarfega]

My updates usually arrive around 3am for me since thats when the scheduler is checked for.

 

[Mercurial]

it might be the first modern Windows OS without a service pack


who knows? !

 

[Zardoc]

I'm just curious as to WHAT the future update's via MS for Windows 7 will include...
Like really...? What is their left to fix? Besides getting compatible drivers/BIOS/.etc etc.. but i honestly think the security for W7 is fine.. and i don't even use IE8

A few major issues still floating is the HAL error that a lot of users are getting. Intel needs to update bios firmware for S3 issues with certain chipsets still giving errors. Also USB disk errors.

Some software still has sidebyside coding issues

PGP needs to get their act together. They still have Hive issues since Vista

 

[Teerex]

A few major issues still floating is the HAL error that a lot of users are getting. Also Intel needs to update bios firmware for S3 issues with certain chipsets still giving errors. Also USB disk errors.

I have posted the explanation for the HAL error, it is not up to Microsoft to fix that.

 

[Zardoc]

A few major issues still floating is the HAL error that a lot of users are getting. Also Intel needs to update bios firmware for S3 issues with certain chipsets still giving errors. Also USB disk errors.

I have posted the explanation for the HAL error, it is not up to Microsoft to fix that.

Not Microsoft?? I know about the white paper, thanks SEE MY REPLY 3 WEEKS AGO IN A POST

I said, A few major issues still floating are the HAL error that a lot of users are getting. Intel needs to update bios firmware for S3 issues with certain chipsets still giving errors.

Most issues, like the dreaded Nvidia and ATI and creative problems when XP launched were issues that had to be worked out by both Microsoft and hardware distributors.

Now ask who will take the blame? Intel says it's Microsoft (besides, they won't confirm a thing until the official release of RTM). Microsoft says it's Intel.

Intel even put out a bios update for their X48 chipsets (which has the firmware problem) look and see if there is a mention about S3 errors fixed. Yep. Now has the problem gone away? Nope. It could be Intel only and it could be both Microsoft and Intel that haven't figured out the right combination. Fact of the matter is that the problem is still there.

Here is what Microsoft says

Resolution Steps


System manufacturers or firmware developers must investigate and resolve corruption across a sleep transition. In many cases, the resolution of the issue requires a more recent BIOS update for the platform.
System manufacturers should cycle all new Windows-based platforms through sleep transitions and check for the HAL event. If the HAL detects and logs the event, engage the firmware developer to resolve the issue.
Firmware developers can use the event details, including the number of corrupted pages and the first corrupted page, to determine the exact code defect that caused the memory corruption.

Now, can we seriously think that this issue was only documented in June? No. It's just a way for Microsoft to put at ease users (and to pressure manufacturers) to work together in correcting a flaw with coding
It's an issue (amongst others) that both manufacturers and Microsoft must fix. It was really bad with Creative SoundBlaster in XP

All these things will eventually be fixed (depending on priority)

 

[Teerex]

If you actually read the whitepaper you find out that Vista and Win 7 don't store any data into that lowest 1 MB of RAM affected by this error. That is a purely diagnostic error event meant to alert firmware developers, so that a future version of Windows can store OS data there again.

Therefore, this HAL error is not 'related' to other BIOS/Windows incompatibilities out there.

Believe me - I had an issue that was driving me wild - my BIOS was slowing down both CPU and RAM for no reason and without showing any signs of its nefarious activities in that respect within its own UI.

Reset to factory defaults and all was back to normal - but I had the HAL error in the Event log then and I have it now.