Windows 7 Build 7048 discussion and bugs

[Examinus]

I hope everyone who notices bugs are submitting them to MS!

Hmm, I'm sure people from Microsoft have posted and said that's a waste of time when it comes to leaked builds.

[Jorkand]

Amazingly the memory usage has been reduced compared to 7000. 380MB out 1GB on my laptop. Its almost netbook worthy now. Next release I am going to try on a 512MB thinkpad.

[terroradagio]

Hmm, I'm sure people from Microsoft have posted and said that's a waste of time when it comes to leaked builds.

Its an official build for select testers. Doesn't matter if it was leaked. They will look at all bugs.

[+Elі Subscriber²]

I just tried to understand but if you don't mind, any chance for a video on youtube ? :p

I'll see if I can do this later on today, and yes memory usage has been greatly reduced in this build.

[Examinus]

Its an official build for select testers. Doesn't matter if it was leaked. They will look at all bugs.

O rly?

[wguimb]

Yes, there are already bug reports for 7048 submitted on Connect. MS is responding to them.

[Ambroos]

Ah right, thanks. I think I'll skip it then until a build leaks thats definitely the RC, or just get the RC. Now the main question is whether to go 32 or 64bit.

64bit if your pc can handle it! I've been running it with 2 gigs of ram for aaaages and I've yet to experience any problems (except one old game that didn't want to install copy protection driver).

[Examinus]

64bit if your pc can handle it! I've been running it with 2 gigs of ram for aaaages and I've yet to experience any problems (except one old game that didn't want to install copy protection driver).

I think I'll give it a go. All the drivers are available and I'd get to use an extra 3MBs of RAM. Woo!

Will I notice speed improvements in things, specifically stuff like Photoshop and video editing?

[terroradagio]

O rly?

Doesn't say anywhere they won't examine the bug reports. And as someone already stated, they are looking at bugs from 7048..

[Examinus]

Doesn't say anywhere they won't examine the bug reports. And as someone already stated, they are looking at bugs from 7048..

It backs up what I said. I'm just repeating what others in a more knowledgeable position have said.

[wguimb]

Here's an example bug report on Connect.

Type Bug ID 421723

Status Active Access Restriction Public

Opened By portos Blocking Issue No

Opened 3/8/2009 Submission Language English

Description

Fantastic! Excellent work, i love!

The new icon, the new design is very good!

Continuation of a Great job!

Comments

Repro Steps

No Bugs!

Regression

Frequency

Customer Area

Color Management

Platform

amd64

SKU

Ultimate

Open Build

7048

UI Language

English

File Upload Status

In Process

Open Revision#

File Attachments listed below do not include those sent with the feedback tool. When they have been processed successfully the File Upload Status status (listed above) will show "Completed". There is no need to attach them again.

[Examinus]

Here's an example bug report on Connect.

Type Bug ID 421723

Status Active Access Restriction Public

Opened By portos Blocking Issue No

Opened 3/8/2009 Submission Language English

Description

Fantastic! Excellent work, i love!

The new icon, the new design is very good!

Continuation of a Great job!

Comments

Repro Steps

No Bugs!

Regression

Frequency

Customer Area

Color Management

Platform

amd64

SKU

Ultimate

Open Build

7048

UI Language

English

File Upload Status

In Process

Open Revision#

File Attachments listed below do not include those sent with the feedback tool. When they have been processed successfully the File Upload Status status (listed above) will show "Completed". There is no need to attach them again.

Yes, very good - well done. But I didn't say they would be ignored, I said people from Microsoft have said it's a waste of time, so I'm not sure what you're trying to show.

[wguimb]

I'm not trying to prove anything. Just FYI, no reflection on your post. :)

However, I agree that MSFT is not paying much attention to bug reports from 7000 now. Because they are close to RC now. Build 7048 feedback is probably getting their attention though, regardless of the fact that it is a leaked build. :)

[Examinus]

I'm not trying to prove anything. Just FYI, no reflection on your post. :)

However, I agree that MSFT is not paying much attention to bug reports from 7000 now. Because they are close to RC now. Build 7048 feedback is probably getting their attention though, regardless of the fact that it is a leaked build. :)

I'm sure they're pleased people are so keen to get involved, but like I said I'm just repeating what people in the know have said. I'm open to correction though, because obviously I'm just repeating them.

Also, I frankly wouldn't want to publish the fact too much that I've downloaded a leaked copy without the owner's permission. ;)

[terroradagio]

I'm sure they're pleased people are so keen to get involved, but like I said I'm just repeating what people in the know have said. I'm open to correction though, because obviously I'm just repeating them.

Also, I frankly wouldn't want to publish the fact too much that I've downloaded a leaked copy without the owner's permission. ;)

Buddy, 7048 is the latest build released to testers because they WANT feedback, so suffice it to say they are listening to feedback from 7048.

[dcoaster]

I sure hope we see a cleaned up RC, because personally, it seems like 7048 has had more bugs than did 7022 or 7000. I have a few problems with both my physical and virtual PCs. (Yes, I understand it is an internal build...) But hopefully, things don't go backwards...

[Examinus]

Buddy, 7048 is the latest build released to testers because they WANT feedback, so suffice it to say they are listening to feedback from 7048.

Thanks, "buddy", but I've already made my point very clear.

[terroradagio]

Thanks, "buddy", but I've already made my point very clear.

Actually no one knows what your point is really. You are just being argumentative.

If MS didn't want feedback, they wouldn't have released 7048 and still included Send Feedback.

[Examinus]

Actually no one knows what your point is really.

Nah.

[terroradagio]

Nah.

Now my point is clear. Argumentative. If I am correct, you didn't even install the build. Move on.

[Examinus]

Now my point is clear. Argumentative. If I am correct, you didn't even install the build.

No, it means I don't want to carry this on because you obviously lack the ability to follow a simple discussion. I don't even know why you think me installing the build has got anything to do with it, seeing as though I've just repeated the words of other people. That's all I've done, but obviously your sense of self-importance in telling people to send feedback, then deciding that you apparently speak for everybody, is obviously causing issues.

So, for the benefit of my point, I'll sum it up:

It's been said by some people that sending feedback is counter-productive. I've made no assertions about the feedback being ignored and have said I'm open to correction, albeit by people that actually know what they're talking about.

Edited March 8, 2009 by Examinus

[doug_jnr]

there is always one!

[terroradagio]

No, it means I don't want to carry this on because you obviously lack the ability to follow a simple discussion. I don't even know why you think me installing the build has got anything to do with it, seeing as though I've just repeated the words of other people. That's all I've done, but obviously your sense of self-importance in telling people to send feedback, then deciding that you apparently speak for everybody, is obviously causing issues.

So, for the benefit of my point, I'll sum it up:

It's been said by some people that sending feedback is counter-productive. I've made no assertions about the feedback being ignored and have said I'm open to correction, albeit by people that actually know what they're talking about.

RIGHT, they put in the abiltiy to Send Feedback for the fun of it to make people think they are helping.

It's funny you actually believe they would put in a feature to make things purposely "counter productive". You seem to misunderstood what the person you quoted said. He said what was counter productive is the reporting of bugs on old builds, use 7000 for example, that are now known or fixed. Reporting bugs on older builds is indeed counter productive. But 7048 isn't an old build. It is newly released for testers.

[Examinus]

You seem to misunderstood what the person you quoted said. He said what was counter productive is the reporting of bugs on old builds, use 7000 for example, that are now known or fixed. Reporting bugs on older builds is indeed counter productive. But 7048 isn't an old build. It is newly released for testers.

What? No. It was a post made in a thread about interim builds, with specific reference to those leaked, just like the one being discussed here. As I understand it, and has been explained in this thread, 7048 is a leaked interim build after Beta 1 but before RC1. It's completely applicable.

I also believe the Send Feedback feature is included in all builds, public or not, and doesn't discriminate between a leaked or legitimate copy. See build 6956 that was obviously not meant for public usage, but still had the Send Feedback option: http://www.mydigitallife.info/wp-content/u...ows-7-69561.jpg

Ultimately I think we both have the same goal. We want to help make Win7 as good as can be and give our feedback, but my point was sending feedback may not always be as productive as you think. That assertion is based on what I've read from people that work at Microsoft, and as I've said a number of times I'm open to correction.

Edited March 8, 2009 by Examinus

[Guest neo7]

?Define with Encarta?

<?xml version="1.0" encoding="UTF-16"?><WinSAT><ProgramInfo><Name>WinSAT</Name><Version>V6.1 Build-7048.0</Version><WinEIVersionWindows7-RC-0.1</WinEIVersion><Title>Windows System Assessment Tool</Title><ModulePath>C:\Windows\system32\winsat.exe</ModulePath><CmdLine...