Jump to content

windows 7 sp1 beta released!


gosh

Recommended Posts


Like I've explained,....

To be fair :) you didn't explain anything before, you may have "announced it" or "stated it", NOW you explained *somehow* *something* :whistle:

But still it is not an explanation, it's a simple report about why it was disabled, and doesn't really explain why "SP (levl N) can ONLY be integrated in a fully configured DVD with N-1 level".

A possible :unsure: explanation goes something like :ph34r: :

Since the good guys at MS didn't find an easy (for them) way to integrate SP's, they removed an easy (for all their customers) feature.

Additionally the problem is not with slipstreaming the "current" SP1 but will come out when SP2 will be out.

In their wisdom, to make life easy (to them) and avoiding a lot of protests that will come when the slipstreaming of SP2 will fail, they removed this possibility also for SP1 which may have made life easy (for all their customers), at least temporarily.

:lol:

;)

jaclaz

Edited by jaclaz
Link to comment
Share on other sites

It's not a flat-file-based system, and even slipstreaming updates doesn't actually "slipstream" them - CBS installs them during WinPE after the base WIM has been placed down on the system. Unfortunately, one of the drawbacks of having the current servicing stack and image-based installer means slipstreaming a whole service pack (versus perhaps a few packages) got a LOT harder. However, given that we have good tools now to build Windows 7 images, I'm not sure this is really a sticking point like it was when Vista SP1 came out.

Link to comment
Share on other sites

the point is, why does the ST thinks updates into an offline image can be pending? This is the cause of the Sp slipstream issue. An update can be only pending, when hardlinks can be updates when they are in use. The Slipstreaming works fine, when you have an fully configured image from MS.

Link to comment
Share on other sites

The Slipstreaming works fine, when you have an fully configured image from MS.

Well, but *somehow* the MS guys must create this "fully configured image" :unsure:, even if they do it by typing each single byte :w00t:, there must be *some* way they create it, so the question is:

How can one convert a normally slipstreamed SP1 image into a "fully configured" SP1 image?

I presume it is just a question of time before someone finds a way...

jaclaz

Link to comment
Share on other sites

The fully configured image can be created by your own. Simply follow the reverse guide for Vista Sp1/Sp2. This creates fully configured images. MS has an automated way to do this.

Yep. :)

That's what I was talking about AFAIK "we" don't have such an automated method/app , but before or later someone may come up with one. :thumbup

jaclaz

Link to comment
Share on other sites

Technically, all Windows Vista / Windows 7 images are just that - images. Microsoft can make them from their build labs, but it's not wholly different than reverse-integration, really. You'll find a system installed from an MSDN SP1 source to be just about identical to one from a reverse-integration image.

Link to comment
Share on other sites

Because you're not just copying files, you're staging them as well. There *are* updates pending (technically binary staging) in an offline image, even an RTM image - this is one of the reasons the only really reliable way to do this is to use reverse-integration. We don't have access to source and thus cannot just *build* an SP<insert version here>-level build of Windows like Microsoft can, but we can do what is arguably the same exact thing by installing and cleaning, then running sysprep.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...