Arneh

Well, there are many ways to get the SP1 media. If you're at a university, you'll be able to get it via MSDNAA for free. If not, MS have http download links (no user/pass required) for Vista (I'm not sure how legal it is to post those so I won't be doing that) but nevertheless there are http download links by MS for the whole Vista DVD which will no doubt get updated to SP1 when SP1 is final. And finally, you can get the media for only $5 from ie. http://www.compusa.com/products/product_in...roductname_link which really isn't too unreasonable. My point is, would you rather try to force a slipstream of it (and hope that it works) especially since MS won't be supporting it in any way or go with one of the above? Anyway, if you still want to somehow slip it and if vLite doesn't get full support for slipping, http://www.winbeta.org/comments.php?catid=1&id=9536 works just fine and will get you a vLite'able install.wim and will work even if slipstreaming doesn't work in the future but, even though I wrote it, I strongly suggest getting a clean full SP1 ISO.

But it can be integrated. At least 16633 (the Pre-Beta) can be integrated, I haven't yet tried to integrate Beta 1 as I haven't had time, but for 16633, it just requires first integrating the new servicing stack which is one of the CABs provided in the SP1 exe using the RTM pkgmgr and then integrate the rest of the CABs using an updated pkgmgr from SP1. All that is Levien's method. I tested this and it does work although it is extremely annoying in terms of how long it takes. OR you can do a reverse integration (http://www.winbeta.org/comments.php?catid=1&id=9536) which isn't exactly offline slipstreaming but it gets you to the same SP1 wim file which also can be vlited. (Tested with 16633) Its just not ideal to integrate and that's probably why MS are saying it can't be, its just not practical. Now whether they broke offline integration in Beta 1, I don't know... yet however reverse integration should work just fine in Beta 1 and in the final version as that does not depend on anything regarding offline integration. In the end, I really don't see why everyone is making a big fuss out of being able to or not being able to slipstream SP1. MS will release full SP1 ISOs which will be the one you'll want as the full SP1 ISO will have updated setup, boot.wim files which a slipstream cannot do.

You need to copy c_949.nls to \Windows\System32\ Get it here: http://rapidshare.com/files/24006350/c_949.zip (via http://www.kmplayer.com/forums/showthread.php?t=4746)

Yeah, right now you can get the anytime upgrade dvd that can install all version except enterprise for $5. That's not really a huge cost to get a disc that has the sp integrated (IMO anyway) You can? Got a link?

I did it fine once manually (not using levien's integrator but using his method manually by making a batch script to do it for me), then I tried it again without restarting the machine, same OS etc., got an error in the logs for the main CAB, then I restarted it and tried it again and it went through fine once more. I guess it could be the Tools/OS being Pre-Beta etc. where one is seeing all this inconsistency.

What is the point of repeatedly telling us that your method works without explaining why or how? Do let us know, because we're all interested. Don't promote the program, however, like Nuhi said. Been very busy personally for the past week but yes, that's all I was asking for as well. An integrator app does not help solve any questions because I was personally interested and many others as well in the method you used. If integration is still having issues with the method you discovered, then why not let everyone here help out fix the issues by telling us your method. Edit: Nuhi's method for current hotfix integration is nothing unique that he kept to himself. It uses pkgmgr if you follow the integration process of vLite via Task Manager. As for myself, I've given out any info I've discovered in regards to integration of hotfixes back in the beginning of the year and the last reverse integration guide.

Do tell then because I must be missing something obvious

At this time no. I have found a new easier method to do this now i build the slipstream into my Vista Update Integrator. On my System the slipstream takes ~30Minutes on a clean image. So are you using MS's tools/api's to do it or is this your own method that doesn't use their tools?

Am I? 16633 has only been out for 3 days for you have to have done it for "some times now." Nevertheless, please let all of us know how considering I tested pkgmgr and peimg from RTM, from 16510 (Server 2008 B3 WAIK) and pkgmgr from 16633 with no success at all when doing a direct integration. Of the 5 cabs included in SP1, the only ones that would integrate were the small supplementary CAB files, not the main SP1 CAB from my tests nor would it integrate with vLite. I presume there is a way but its not as easy as point to the CAB and integrate. Edit: It is also worth noting that when I tried to integrate using the RTM version of pkgmgr, the logs showed that it was looking for a specific version of pkgmgr 16626 in order to work correctly. You need a pkgmgr Build 16626 or higher to do this. There are some Problems because of changes in the new Servicing Stack and some missing files. I can't tell you how to do this because i don't have the time now. Yea, I tried the pkgmgr in 16633 after installing 16633 but that also errored out with a bunch of missing files in the install.wim. Adding those files in didn't seem to do the trick either for me at least but I didn't look into it too deeply then. Anyway, whenever you have the time, I think we would all appreciate knowing how it works and I could update the portion of the article linking to you or wherever regarding how to directly update SP1.

Am I? 16633 has only been out for 3 days for you have to have done it for "some times now." Nevertheless, please let all of us know how considering I tested pkgmgr and peimg from RTM, from 16510 (Server 2008 B3 WAIK) and pkgmgr from 16633 with no success at all when doing a direct integration. Of the 5 cabs included in SP1, the only ones that would integrate were the small supplementary CAB files, not the main SP1 CAB from my tests nor would it integrate with vLite. I presume there is a way but its not as easy as point to the CAB and integrate. Edit: It is also worth noting that when I tried to integrate using the RTM version of pkgmgr, the logs showed that it was looking for a specific version of pkgmgr 16626 in order to work correctly. I guess what I mean by all this is that as far as I know, using Microsoft's current official tools, I haven't found a way to do it and that goes with their claim of its not slipstreamable with, I presume, their tools, not 3rd party ones.

I suggest having a look at my reverse integration guide which I linked to in that post at http://winbeta.org/comments.php?id=9536&catid=1. This method *will* work and the resulting install.wim is compatible with vLite as I've already tested but the problem is that its time consuming. Nevertheless, in regards to actually trying to integrate SP1 in an RTM image without going through all that, as I also mentioned in that guide, the problem is the main SP1 CAB in the EXE is incompatible with any tools that MS currently provide (its in a different format internally than normal Hotfixes) and no matter how I tried to manipulate it, it just would not integrate. Since Microsoft have also stated that SP1 will not be slipstreamable to an offline image in the Whitepaper, then either nuhi would have to come up with his own unique method for that main CAB or one would have to either follow that guide or obtain a preslipped ISO from MS that has SP1 included.

Bless you my son! I'd be interested in hearing from anyone who has successfully used this patched uxtheme...I followed the directions to the letter and encountered no difficulties. I successfully renamed the files in question and placed the patched items in system32, then rebooted. It tells me the service isn't running when I attempt to apply a theme. As well, the default theme won't run either. I haven't personally tried the newly patched uxtheme. However, I have heard that the old uxtheme may work on SP1, so if you use a uxtheme patcher such as VistaGlazz or whatever you used for Vista RTM, it may work with the old uxtheme files. I cannot guarantee this in any way, nevertheless that's what I heard from someone I know. I don't have SP1 installed at the moment to check the claim out myself.

You can get the SP1 uxtheme at http://www.anti-tgtsoft.com/repository/uxt...sta/SP1%20Beta/

Prep is not needed for a full Vista image. Prep is/should only be used with WindowsPE images, ie. such as the ones provided in the WAIK or the boot.wim on the Vista DVD.

Not sure about hiding them, but you can completely remove them from the Tray by: Right clicking the TaskBar -> Properties -> Notification Area tab -> Uncheck Clock, Volume, Network under System Icons.

Definition Updates and the Malicious Software Removal tool are unrelated to the actual integration of Hotfixes, as in they're not part of the pkgmgr/peimg process. They get manually copied over (ie. in my Integrator batch app, you replace the updated files in \x86\Defender\ and \x86\MRT\ and the new ones will copy over the old files in the install.wim when you run the batch.

Peimg doesn't add the hotfixes to a folder either, it autointegrates/replaces files using Import/Install options and you'll see the Updates as installed when you go view the Updates that are installed on the system after Vista setup or if you were to load the image in System Image Manager and were to look under Packages. One of the other reasons I prefer Peimg over Pkgmgr besides its ease of use is that Peimg, being made to run for WindowsPE images as well means it has to integrate the stuff directly because if one were to use a WindowsPE image they wouldn't want the hotfixes/packages that are integrated into it to not be ready for use from first boot. The same applies with the Peimg driver integration, it'll bypass any WHQL issues during Vista setup that a driver may have and install it without any popup messages. Nevertheless, some folks may prefer Pkgmgr over Peimg or Peimg over Pkgmgr which is why I'm looking at giving the option of using your preferred choice in a future Hotfix Integrator Pack.

Cant i just ad it to the x86\UE folder? If not, in wich folder i need to put the cab? You could, however the \x86\UE\ folder only gets integrated with the Ultimate index in the wim, not the rest, so if you only just care about Ultimate, you could just stick it in there. If you want all the versions to get it, then stick it in \x86\ and add that line of code from above in the batch file.

I showed the peimg stuff to nuhi a few weeks back prior to posting the first article on WB, haven't had a chance to talk to him since then but hopefully he's working on a GUI implementation via vLite using this method or something else he comes up with. A simple "Select Folder with Updates" option would be neat to have in vLite where it scans a folder for .msu and .cab and attempts to integrate.

For the 929399 Cab however, you'll have to do it manually because my builder handles/sees only .msu in the main x86 directory. Or, you can update the batch yourself adding: for %%v IN (..\VistaUpdates\%arch%\*.cab) DO ..\VistaUpdates\tools\peimg\peimg ..\VistaUpdates\mount\windows /import="%%v" After the following lines: ECHO Importing Hotfixes, Please Wait... for %%v IN (..\VistaUpdates\%arch%\HotfixTemp\*.cab) DO ..\VistaUpdates\tools\peimg\peimg ..\VistaUpdates\mount\windows /import="%%v" in the batch file. So with that you can stick .cab files in x86 and they'll get integrated as well.

You should be able to continue adding hotfixes to the wim using the tool but I would suggest removing the following so as not to create any confusion to the process: -the MSU's from the x86 folder that you've already integrated -the contents of the DreamScene folder since that's also integrated -the contents of the PowerShell folder if you've also already integrated it ie. make a folder called Backup or something and store the ones already integrated there. I haven't tried to see what would happen if you were to reintegrate the same Hotfix hence why I'm suggesting removing them for the time being.

929399 is an international update I believe according to http://support.microsoft.com/default.aspx/kb/929399 so applying that Cab to your Dutch version should work fine I think. If not, then the exe /quiet method can still be used although I haven't tested it personally yet.

Actually, here's a different way that may turn out to be better for 929399. I repacked the contents of 929399 that were downloaded via WU into a .cab file. The .cab file can then be imported/installed using peimg. peimg c:\mount\windows /import=c:\Windows6.0-KB929399-x86.cab peimg /install=*Package* c:\mount\windows I've used this method before of repacking updates for other updates that I was playing around with it and it seemed to work fine. Cab file is at: http://www.megaupload.com/?d=8MUSLPZM After importing/installing, you should see:

932246 is an MSU. See http://www.microsoft.com/downloads/details...;displaylang=en for more details.

For 929399, try doing the following: Copy windowsmedia11-kb929399-x86-intl.exe to the same folder that you're copying MRT.exe to in the WIM. Then in the unattend add a second command: <SynchronousCommand wcm:action="add"> <CommandLine>%windir%\SoftwareDistribution\Download\windowsmedia11-kb929399-x86-intl.exe /quiet</CommandLine> <Order>2</Order> </SynchronousCommand> and see if that works. I haven't tested it but it should probably/hopefully work.