fbl impressive code 10049 windows update

f14tomcat said:

I just want to add my 2 cents.... this is not the final release. This is not even close to RTM.. It is, at best, a senior alpha or junior beta.

What do you think the gurus in Redmond are doing? They're tweaking the guts out of this! Just like they should be. So are we. It's part of the testing and feedback. Some of the feedback resulting from insider tweaks has made it to the next build.

If MS was set against Tech Preview mods by Insiders, they would have deprecated Regedit! They expect us to look under the hood and experiment. They also expect some common sense from Insiders, as well as their own people.

I, for one, am having fun using what MS has provided and tinkering around.

All IMHO....

Hear, Hear !!

Roger said:

Another speed factor that's seldom considered is burn speed of your ISOs?
As burn speeds have increased I wonder how many ISOs have been burned at 52x and the user spent the weekend trying to install the new update and couldn't?

There's no such thing as a 52x DVD burner. 24x is pretty much the max. 52x is only for CD-R's. Any computer should be able handle 24x.

Mystere said:

There's no such thing as a 52x DVD burner. 24x is pretty much the max. 52x is only for CD-R's. Any computer should be able handle 24x.

We call them coasters

dencal said:

Thank you for explaining so that others can fully understand my original post that playing around with the registry will have no input in the development of this Preview O/S.

Your point isn't completely lost, it was more of the way it was made, than the content.

I install a TP rls two ways, Windows Update and Clean ISO install. Then I run a set of consistent tests on each rls, adding new tests for new features.

When that is all said and done - I personalize the machine to my liking. Some of that requires registry mods because MS does not provide a UI to make the change. This doesn't mean that it is an unofficial modification, the registry keys and values are there to be set if you understand what they are. There are and will be MS sanctioned registry mods as part of a solution.

Will some mod break the system? Probably, but MS should know about that too.

Plain vanilla testing is the domain of MS, we're given the opportunity to the drive the OS. How I drive or how you drive is up to each individual. All feedback is useful to MS, there's no possible way for them to do what 2 million individuals might change or install. That's the real point of the TP - not just geeks, but how will regular users 'break' the system.

The real feedback is the telemetry they pull from your system - if they see a registry mod in the data, they know they either need to fix the code that caused the app or system crash or ignore the key/value.

Bill
.

Roger said:

"Upgrade speed has a lot of factors..."

Another speed factor that's seldom considered is burn speed of your ISOs?
As burn speeds have increased I wonder how many ISOs have been burned at 52x and the user spent the weekend trying to install the new update and couldn't?

It's great to brag to the forum that you burned the new 2.5GB file to DVD in four minutes but it's not so great to spend a weekend to discover it's a bad burn.

I don't know what the max speeds are on any of my burners, and I've got a dozen or so kicking around, but I burn everything at 4x. Burning an ISO to disk is no time to rush.

The main problem with burning disc at higher speeds is finding quality media. With the reasonable prices of flash drives and HDD I very rarely burn anything to disc.

badrobot said:

That's the exact opposite for downloading the ISO.
You have to have a good and steady speed to download a clean ISO. If you have a wonky connection (specially wifi connection), it's prone to having a corrupted download.

I still remember the days trying to download newer versions of Mandrake Linux when I only had a dial up connection. It didn't take hours, it took days. I could never go back to dial up.

Slartybart said:

Your point isn't completely lost, it was more of the way it was made, than the content.
Bill.

Please reread my original post, it was not a point, it was a QUESTION. see post #28.
Is it not somewhat counterproductive to tweak unofficial mods and the registry.?

badrobot said:

It seems that MS is making registry tweaking easier for everyone probably through feedbacks MS is getting from Windows Insider hub.
They may be monitoring the Registry Editors too more that they read our feedbacks. :)
http://www.neowin.net/news/windows-1...-between-hives

The operative word being MAY!!!
Purely a subjunctive opinion M$ would find it extremely difficult to keep tabs on the registry modifications made on millions of computers on an experimental O/S especially if one takes into account some of the mooted points pointed out by ROGER in post #96 and these are just some of the problems encountered in installing this latest preview.