|
Windows 7 beta discussion thread (pg. 23)
|
View this Thread in Original format
| gehzumteufel |
| quote: | Originally posted by Jer
It'll likely be build 76XX or 7700 that she recieves. As far as I know, MS won't be supporting a method to upgrade from the RC to GA so I'd advise her to hold off. |
No offense, but why didn't you just search google? The final build number, ISO names, etc have been leaked for a bit and was confirmed a week ago.
7600.16385.090713-1255 is the final build string.
You are correct though, that MS does not officially support the upgrade path from Beta to Final/RTM. |
|
|
| gehzumteufel |
This bug is not critical first off. This has be debunked. Is it important to fix? Yes. And second, if it was critical, they would find and fix the problem before PCs ship with this issue. So, again, a non-issue.
Also, have you read how you have to reproduce this bug? And have you seen that most people can't even reproduce it?
| quote: | Originally posted by Jer
ing double post |
Then delete it. |
|
|
| LKD |
| quote: | Originally posted by Jer
ing double post |
n00b |
|
|
| DigiNut |
I don't know all of the details behind this supposed "chkdsk bug", but judging by the screen shot, it looks like a lot of people still think they can look at the task manager to measure how much actual memory a program is using, which has never been a valid method (memory usage is not the same as addressable space).
If it's crashing the computer, fine, that's an issue, but really, who runs chkdsk /r in a command prompt? To me this is a textbook example of a "just don't do that" bug. If I worked at Microsoft, you can bet that I would bury a "show stopper" (lol) like that, because it will be encountered by maybe 1 in every 100,000 users, if that. In close to 2 years running Vista I don't think I've ever manually run a disk check at all, much less through a command prompt. |
|
|
| VERTiG0 |
| quote: | Originally posted by gehzumteufel
7600.16386
|
fixed
Almost bought an Intel X25-M last night, then realized that the 1st-gen doesn't support TRIM in Win7, and the 2nd-gen that was just released that does support TRIM has some nasty data corruption bug.
More waiting! |
|
|
| Jer |
| quote: | Originally posted by DigiNut
I don't know all of the details behind this supposed "chkdsk bug", but judging by the screen shot, it looks like a lot of people still think they can look at the task manager to measure how much actual memory a program is using, which has never been a valid method (memory usage is not the same as addressable space).
If it's crashing the computer, fine, that's an issue, but really, who runs chkdsk /r in a command prompt? To me this is a textbook example of a "just don't do that" bug. If I worked at Microsoft, you can bet that I would bury a "show stopper" (lol) like that, because it will be encountered by maybe 1 in every 100,000 users, if that. In close to 2 years running Vista I don't think I've ever manually run a disk check at all, much less through a command prompt. |
That's all well and good, I've run CHKDSK maybe three times in my years working with Vista (in both pre-release and GA) - All I'm pointing out is that there is a flaw in the code, no matter how small or inconsequential it may be to the general public. While most people would probably be a-ok with this and never think twice about using build 7600.16386.090713-1255, I'm just pointing out that they'll likely alter the code to address this, thus changing the build and who knows what else.
I've read in a few spots that engineering continues on the product past when the RTM is signed off on, right up until GA. I'm just assuming this is one of those cases - It makes ZERO sense for a product (let alone a flagship one) ship with any kind of flaw, especially when it's this publicised and regardless of how much it'll impact the common end-user. I mean, I saw "TWITTER HACKED" all over the ing CBC because some nimrod tried to bring it down in a DDOS attack.. I doubt the Windows 7 Development Team wants any kind of negative press for when this launches on the 22nd October - Just a thought:
| quote: | Originally broadcast by CNN
FLAGSHIP MICROSOFT RELEASE MARRED BY LAUNCH WOES
Less than hours after the General Public Availability of Microsoft's Windows 7 Operating system, users are being asked to install hotfixes that address a "showstopper" error that could grind the user's system to a halt - Hardly the security powerhouse that Microsoft developers have boasted about in the nearly 2 years of engineering to ready it for release.
etc etc etc..
|
PS why all the ing animosity? Jesus lol |
|
|
| patpicos |
| quote: | Originally posted by Jer
I've read in a few spots that engineering continues on the product past when the RTM is signed off on, right up until GA. I'm just assuming this is one of those cases - It makes ZERO sense for a product (let alone a flagship one) ship with any kind of flaw, especially when it's this publicised and regardless of how much it'll impact the common end-user. I mean, I saw "TWITTER HACKED" all over the ing CBC because some nimrod tried to bring it down in a DDOS attack.. I doubt the Windows 7 Development Team wants any kind of negative press for when this launches on the 22nd October - Just a thought:
PS why all the ing animosity? Jesus lol |
Because its considered good journalism lol, hey that's headline worthy, lets distort the facts and make it event stronger |
|
|
| Jer |
| quote: | Originally posted by devnull
Because its considered good journalism lol, hey that's headline worthy, lets distort the facts and make it event stronger |
That's exactly my point - Hence why a ty DDOS attack was on the ing news. If someone successfully DDOS'ed, say, canada.gc.ca or whitehouse.gov - then yeah, newsworthy. The fact that people couldn't read Paula ing Abdul's "idol farewell" tweets is *not* headline-newsworthy to me. |
|
|
| rabbitjoker |
| quote: | Originally posted by Jer
I've read in a few spots that engineering continues on the product past when the RTM is signed off on, right up until GA. |
Engineering continues even after GA - what do you think SPs and updates are?
The first thing a new install does is try connect and update itself, whether it is XP, Vista or 7.
RTM is a great step forward that will allow it to get on to devices, get broad scale and tighten up the last few minor issues so that the GA is in peak form and RTM updatable to such a state.
RTM is a big friggin' deal (way bigger than GA). |
|
|
|
|
