ok, those 2 .mum files where really easy to miss while scrolling, found them now... now, my 2 cents: - you SHOULD overwrite older files, that is, start expanding from smallest numbered kb to largest, and NestedMPPContent.cab should be the last (as you can see from new cabs ini file, order of lang cabs is irrelavent but they should go right before it, they contain different languages with the same english one in each) - in setup.ses you should change "absent" to "installed" in offline installation phase (i think its self explanatory why) will try now that way and report later...
I'm now integrating with overwritten files. But rt7 didn't overwrite and also didn't eddit update.ses (although I indeed expected update.ses o be modded also). But doing it the way I discribed in my previous post you'll have the same directory as rt7 created right before executing 'some dism command'. Tomorrow I'm going to run rt7lite again and look at the dism logs. And about overwriting older files: this isn't always true. For example the update.mum in kb976902 contains info about that update, the update.mum from the main cab contains info about that cab. The 2 cabs inside the main cab don't contain an update.mum. But the update.mum of the big cab may be missing info about 976902 and visa versa. Also it seems all dll and exe files etc of 976902 are also inside the main cab, so I wonder what the exact purpose of this update is, also because it let the integration with my method fail when already applied before. With normal updates it doesn't matter if some update is already installed or nog (at least during dism integration). Maybe it works using a custom update.mum with info mixed from the 2 real ones? I really don't know.
Hellyeah! And perhaps post a improved guide beacuse now i dont understand a thing I get expans sp1rc.exe by writing sp1.exe -x (Will -x extract it to current folder?). And then C:\sp1\windows6.1-KB976932-X86.cab the same way or use expand command? And then C:\sp1\windows6.1-KB976902-X86.cab same way as above? And then Im lost
You can extract the cabs with winrar, 7zip, whatever. Extract windows6.1-KB976902-X86.cab first, then extract windows6.1-KB976932-X86.cab to the same directory. Then inside the extracted directory extract NestedMPPContent.cab and KB976933-LangsCab0.cab also to tha very same directory. All without overwriting with overwriting, I don't know yet. Then set allowedoffline=false to true in both update.mum and Windows7SP1-KB976933~31bf3856ad364e35~x86~~6.1.0.17105.mum in that same directory But it doesn't work at the moment. dism /image:X:\whatever\mountedwimimage /add-package /packagepath:X:\whatever\extractedcabdir this command integrates fine, and the wim image grew quiet a bit, but when installing it just installs rtm (and yes I installed the right version, mounted the right index, unmounted with /commit switch etc) But when I succeed I'll write a propper guide
ok, a couple of things i noticed: you HAVE to edit update.ses, otherwise offline install will just do the same as online/offline uninstall - remove KB976933 if its already injected even !!! my update.mum contained all 3 KBs, it came from NestedMPPContent.cab which containes same files as KB976902 (just newer i suspect, but didnt check), so not overwriting IS where you went wrong Stannieman the version of the image stayed 7600, BUT file versions inside it are a newer 7601 now - maybe image version just depends on dism version? anyone got a new one? i had 7 lang cabs, extracted them all and they ALL got injected, so just extract en-us files from all of them - or the lang you use from the cab which contains it (i suspect en-us files are just fallback languages for incomplete ones, so i'll try without them too) all credits go to Stannieman for making it even possible, but just follow my instruction and thats it...
One question... why are you bothering with intergrating SP1 update in to original MS iso if MS does that for you? You do know they are offical MS isos avilable with SP1 RC integrated? and ofc when SP1 will go final again new isos will be avilable? I mean i undestand if you do is for fun, but at the end of the day its still better to use MS offical isos, because you can at least be safe that its done properly
update.mum actualy came from KB976932, and NestedMPPContent does have all the same files as KB976902 (except for update.mum and update.cat) but has two extra packages whish i pressume are updates for it @solor: official m$ integrated ?! i'm sorry, but i would have to see some links to actualy belive that, anyway it is fun... (and if they did anything properly, sites like this would be obsolite)
They are posted on wzor 2 days ago, leaked by zukona and yes they are "proper" ones since he also posted screens of connect where he got them on FB... MICROSOFT.WINDOWS.7.ULTIMATE.WITH.SP1.X86.RC-1.RETAIL.ENGLISH.DVD-WZ.ZUKO BUILD: 7601.17105.100929-1730 7601.17105.100929-1730_x86fre_client_en-us_Retail_Ultimate-GRC1CULFRER_EN_DVD.iso SIZE: 2,553,706,496 byte SHA1: 4B7BDED6204E1B8F91C2BA8730C6DD40899B5341 MD5: 6CD0E563FAC746DCD479FB9251F1F4FF CRC: 20E6C38F NOTE: this original M$ image. by WZ/ZUKO MICROSOFT.WINDOWS.7.ULTIMATE.WITH.SP1.X64.RC-1.RETAIL.ENGLISH.DVD-WZ.ZUKO BUILD: 7601.17105.100929-1730 7601.17105.100929-1730_x64fre_client_en-us_Retail_Ultimate-GRC1CULXFRER_EN_DVD.iso SIZE: 3,289,118,720 byte SHA1: F5BC7E73FBC7E4C3F80B980954EA22CAB79916BE MD5: 266B60BB6EB7EFF2DC108F881A975BA9 CRC: B68D4618 NOTE: this original M$ image. by WZ/ZUKO MICROSOFT.WINDOWS.SERVER.2008.R2.WITH.SP1.X64.RC-1.OEM.ENGLISH.DVD-WZ.ZUKO BUILD: 7601.17105.100929-1730 7601.17105.100929-1730_x64fre_server_en-us_OEM-GRC1SXFREO_EN_DVD.iso SIZE: 3,121,965,056 byte SHA1: D43256CAA50FE1463C259AE2BA70A821491E2DDE MD5: 14858F9009816548E9355713D5D8E82A CRC: 48A4EEDA NOTE: this original M$ image. by WZ/ZUKO MICROSOFT.WINDOWS.SERVER.2008.R2.WITH.SP1.X64.RC-1.RETAIL.ENGLISH.DVD-WZ.ZUKO BUILD: 7601.17105.100929-1730 7601.17105.100929-1730_x64fre_server_en-us_Retail-GRC1SXFRER_EN_DVD.iso SIZE: 3,121,965,056 byte SHA1: B932A73A5FB20E2899E497AB2345FF4F0B5FE425 MD5: FC56A794179C7B078756205B0D2651F2 CRC: FBF73F84 NOTE: this original M$ image. by WZ/ZUKO MICROSOFT.WINDOWS.7.LANGUAGE.PACK.35.LANGUAGES.SP1.RC-1.X86.DVD-WZ.ZUKO 7601.17105.100929-1730-3_x86fre_client_langpacks_1-GRC1CLP1_DVD.iso SIZE: 2,212,091,904 byte SHA1: 7FAF75E4E94D3B93FC77A76E4842FBE0D439F92A MD5: C5693638841D4B6D84092232C33A7F52 CRC: C4E3EA0D with CHINESE SIMPLIFIED DVD-2: 7601.17105.100929-1730_x86fre_Client_LangPacks_2-GRC1CLP2_DVD.iso SIZE: 120,690,688 byte SHA1: 367D8B501773CCEDB17E59087B7EEC1A3EA76910 MD5: 10993F338505C4BBCB613D9965337BCA CRC: 2FC08DB3 LANGUAGE PACK - the packages for localizations of the interface of the user Windows 7 with SP1 RC-1. NOTE: this original M$ image. by WZ/ZUKO MICROSOFT.WINDOWS.7.LANGUAGE.PACK.35.LANGUAGES.SP1.RC-1.X64.DVD-WZ.ZUKO 7601.17105.100929-1730-3_x64fre_client_langpacks_1-GRC1CXLP1_DVD.iso SIZE: 2,696,456,192 byte SHA1: 828B54F734602027E92829F170B78CFAC53E465D MD5: 0B7062EFC406CA5E80AAA3B0F5182067 CRC: 188FD955 with CHINESE SIMPLIFIED DVD-2: 7601.17105.100929-1730_x64fre_Client_LangPacks_2-GRC1CXLP2_DVD.iso SIZE: 146,046,976 byte SHA1: A2BEB06D8F010055E493403B54D601F81B3A167F MD5: C3EF3E88850409990BC67389F582DDAD CRC: 8156A4DA LANGUAGE PACK - the packages for localizations of the interface of the user Windows 7 with SP1 RC-1. NOTE: this original M$ image. by WZ/ZUKO MICROSOFT.SERVER.2008.R2.LANGUAGE.PACK.ALL.LANGUAGES.SP1.RC-1.X64.DVD-WZ.ZUKO 7601.17105.100929-1730-3_x64fre_server_langpacks_1-GRC1SXLP1_DVD.iso SIZE: 2,884,667,392 byte SHA1: 91262645627C65AB5D772050EFE9C43875E7C759 MD5: 87365B164F391992CFE668FA3BC7005E CRC: B01EB2F4 with CHINESE/TAIWAN DVD-2: 7601.17105.100929-1730_x64fre_Server_LangPacks_2-GRC1SXLP2_DVD.iso SIZE: 88,520,704 byte SHA1: 6E64E518993C3DD73C238FED8F01C3ADF4123551 MD5: 3801E672E4B3A6FDD0E5C508A1BF2383 CRC: F2FA906E LANGUAGE PACK - the packages for localizations of the interface of the user Windows Server 2008 R2 with SP1 RC-1. NOTE: this original M$ image. by WZ/ZUKO
Wow so unnecessary of MS to release new isos of RC1 .... Well then its time to make a new Windows 7 / Server 2008 R2 AIO.. But why are the language packs also updated?
Considering SP1 have new features like RemoteFX im sure there are new strings to localize... dont know if local branches will localize them, but they have the option with new LPs. Also probably once SP1 will go RTM, LPs will need to be versioned as 7601.xxxxx or you wont be able to install them. I think this is already the case and you need to modify update.mum to get around this... not sure about this part because personaly i hate localized computer... considering im coming from DOS days im used to have everything on computer in english and when i personaly actualy feel lost in localized computer programs and if i need to fix something i actualy ended up translating things back to english in my head....
Hehe i hear ya.. Well ill wait for RTM and MS to release new official ISOs Naah, just integrated every update possible using steven 4554's WUD updatelist Except for Server 2008 R2, no1 helps me with that issue. All editions except enterprise, will all updates & 2 language packs.. total size 6.9 GB or something like that.
ok, i stand corrected, his earlier releases where untouched also, so i will trust him on this one too (others are just reverse integrations) - didnt think m$ would actualy do it, since you cant uninstall an integrated sp, so you would have to do a complete reinstall for the final version... i will download it for updated dism, boot.wim, winre.win and basicly all other files EXCEPT install.wim itself, cause mine is already syspreped, and i would just hate to have to go through all of that again (does that answer your insistent question finaly - plus you would have to dism languages other than en-us anyway, and offline sp1rc does that too) SIMPLIFIED GUIDE: expand anywhere sp1rc with -x switch, then delete it extract larger .cab file with 7-zip to c:\sp1rc (smaller one is for online installation only, and updated one is included in larger too BUT dont integrate it first or slipstreaming will fail), delete everything afterwards in c:\sp1rc extract NestedMPPContent.cab (its that smaller one from above) there too overwrithing anything if prompted, then delete it and 2 already existing .ini files in update.ses under offline installation change "absent" into "installed" in update.mum and windows7sp1-something-.mum change allowoffline from false to true in windows7sp1-something-.mum keep neutral, en-us (as fallback language if yours is not completely translated) and your languge packages, delete all others (they are over 3gb if you want to keep them too) now extract all lang .cabs together to a separate new folder overwrithing anything if prompted, do a search of that folder for anything containing words "en-us" (without quotes) then cut and past it back to c:\sp1rc overwrithing anything if prompted, repeat for your language too, then delete whole that new separate folder, and lang .cabs themselves afterward DISM /Mount-Wim /WimFile:C:\install.wim /Index:1 /MountDir:C:\offline DISM /Image:C:\offline /Add-Package /PackagePath:C:\sp1rc DISM /Unmount-Wim /MountDir:C:\offline /Commit thats it, done (delete sp1rc folder)
Only the lang cab inside the big one, right? Or also the big rtm language packs? And do you need to copy only the files of the languages you want? Cause since they are removed others from update.ses maybe that doesn't matter. And yes of course I knew MS always makes official integrated isos. Also I always preffered MS integrated isos over home made slipstreame ones, even in 2000/xp days where there was a valid slipstream option. But with vista sp1 we wanted a slipstream option => it wasn't there With vista sp2 we were hoping for the return of slipstreaming => it wasn't there With win7 sp1 we were hoping => NOTHING I just want those f*cking sps slipstreamed, and finally it seems we've got it. And I don't know if it's 100% clean and correct, but at least it's possible now without tools like vlite and rt7, from which you never exactly know what they are doing to your wim.
yes, lang cabs inside sp1rc (when all extracted) are about the same size as that separate lang pack download (so you dont need it, no) and yes, i copied only the languages i needed purely as a precaution - with my first slipstream i didnt remove any of them (from folder nor from .mum) and i got about the same size of install.wim EXCEPT that there were folders like c:\windows\en-us for every language - they where quite small, but i wanted to get rid of them too so only the languages already present in your install.wim actualy get fully updated - you can try without removing them from folder (only in .mum file) and see if those small folders get still created, that would be even more simplified procedure then... i didnt know on the other hand that there EVER were official beta/rc slipstreams for the reasons i already stated, and as Stannieman points out correctly, just the simple retarded fact that slipstreaming wasnt given as an option from the very beggining - was all the incentive for it i needed... and this IS a 100% clean and working (not quick and dirty) solution, otherwise m$ themselves would have to reverse integrate
It looks indeed clean, but we don't know how ms make servicepacks these days. I think with xp and earlier they really saw it as a pack of updates which is distributed as an update, and afterwards they made an integrated iso with update eula and setup etc. Correct me if I'm wrong, but I think the sp builds between beta and rc etc were all build in exe installer form. But now I think they look at it as a real new windows build, and they make a new install.wim for each build. Only when it needs to be released to the public (beta, rc, final) they take all the updated files and put the in a cab. That would be the reason that the rc escrow leak was a full iso, just because an exe was never build. So I think MS doesn't make slipstreamed builds, they create the exe sp and the windows update sp based on the new windows build which has the new files.
After slipstreaming, that particular wim index is 1.2 to 1.3GB bigger than the same index of the official sp1 integrated wim. Also 3 SP1 updates and the remotefx client package are listed in the list of installed options, and even the option to remove them is given. 1.2 to 1.3GB is also approx the size of the directory where all the cabs are extracted. This all means that there are backups of rtm files stored inside them wim. So te come closer to the original images and to save space these must be removed, also the registry has to be edited to remove them from the installed updates list. By the way, has anyone already heard of a tool simular to vsp1cln.exe or compcln.exe?
I've tried to use the guide above to slipstream rc1 in windows 7 but it doesn't work for me Everything seems to work perfect but when i install in vmware windows7 doesn't have sp1 installed....:-(