in all this cases you shoudlnt give a s**t.. i woukd say: 1. wait for intergrated isos 2. wait some more 3. and some more.... 4. burn dvd or make usb bootable key 5. backup what you need 6. install from integrated isso dvd/usb key. 7. oh ye and wait some more....
It really is starting to get ridiculous with all the waiting they're making us do. They just want the attention at this point
i quit waiting, not playing their games. Its all fine with SP1 here, will do a clean install when MSDN ISOs are officially out. i would be happy nevertheless if another group release it before
They did say first quarter, and we're getting antsy halfway into January? FWIW, Paul T mentioned "within weeks" last weekend.
MS said first quarter, WZ said yesterday and then today too. Paul T shouldn't be trusted with this stuff
I have to agree with SoLoR here, it is getting a bit ridiculous. You either have the ISO's or you don't. And if you don't just say so, this way people aren't waiting for something that's not going to come any time soon.
Wave 1 SP1 RTM x64 downloaded from link in Post#1 didn't work on a clean install of Windows 7 Ultimate x64 Clean install from USB stick made from TechNet ISO using Microsoft DVD/USB Tool. Asus P5Q-E Intel Q9550 CPU 8800 GTX 4 x1gb 1066 DDR2 OCZ Vertex 2 120gb SSD Wave 0 SP1 RTM x64 from wzor torrent worked perfectly Go figure?
If you have integrated SP1 with RT7 Lite, but want to clean the SP backup files before installing the image, I've prepared this guide for the DISMally challenged: This works whether you have only integrated SP1 with RT7 lite and exited the program before customizing, or after you've integrated and fully customized your image. This assumes that your freshly integrated image already resides in a folder. If you have already modified the new SP1 image with RT7 lite, deleted the folder, and made an .ISO, you can extract the .ISO into a folder. For the sake of simplicity, I suggest you rename that folder to what I've used in the DISM command lines later on in this tutorial; Rename your RT7 image folder "W7SP1." Let's make another folder called "W7temp." Reboot, and after your BIOS posts, hit the F8 key and choose "Repair Your Computer." You'll have to be quick on the draw here; your window of opportunity is pretty slim to hit F8. Once the the recovery console has loaded, select the command prompt option from the list of recovery tools. Now let's mount the image. If you've used RT7 Lite to integrate, no matter what version of Windows you chose, (Home, Ultimate, etc.) the index number will be 1, as shown below. It's hard telling what drive letter you'll need to use in the command lines...my image files resided in my "D" drive, but in the recovery console, it became the "F" drive. I just hunted around by guessing the drive letter and typing E:\DIR and F:\DIR, etc., until I found the correct drive. Type the following, assuming that your RT7 image resides in E:\W7SP1. DISM /Mount-Wim /WimFile:E:\W7SP1\sources\install.wim /index:1 /MountDir:E:\W7temp Once the image has successfully mounted, we'll clean up the SP1 backup files: DISM /image:E:\W7temp /cleanup-Image /spsuperseded DISM may report that there might not be enough disk space for the "scratch file" to perform the operation, but I found it safe to ignore this. After DISM reports that the backup files have been successfully cleaned up, you can unmount and commit the changes to your original RT7 Lite image: DISM/Unmount-Wim /MountDir:E:\W7temp /commit After the operation is complete, you may reboot. Voila! Now when you want to install the image, fire up RT7 Lite and point it to the newly cleaned folder and select no options except for the "ISO Bootable." Once the image is loaded, make a bootable image as per usual and burn to your medium of choice. May I suggest that you print these instructions before rebooting, so that once you're in the recovery console, you can refer to the command lines. Good Luck!
I'm a little confused over who the anger should be directed at regarding the integrated ISOs... yes, we know that Microsoft's build machines automatically generated integrated ISOs on the build date (and almost certainly before the SP1 install EXEs or the KB976932 CABs) and that they do exist somewhere. But is the problem that Microsoft is playing this close to their chest and has not made this ISO available to the leakers (e.g., WZT), or is the problem that the leakers like WZT already have the ISO, but are toying with us by withholding it?
I don't believe WZT is toying us. They just did not put their hands on the ISO yet. Maybe their supplier get caught and fired... Who knows.
St. Cow says: MICROSOFT.WINDOWS.7.AUTOMATED.INSTALLATION.KIT.RTM.WITH.SP1.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.7.AUTOMATED.INSTALLATION.KIT.RTM.WITH.SP1.RUSSIAN.DVD-WZT MICROSOFT.WINDOWS.7.OEM.PREINSTALLATION.KIT.RTM.WITH.SP1.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.7.OEM.PREINSTALLATION.KIT.RTM.WITH.SP1.RUSSIAN.DVD-WZT MICROSOFT.WINDOWS.7.HOME.BASIC.RTM.WITH.SP1.X86.OEM.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.7.HOME.PREMIUM.RTM.WITH.SP1.X86.OEM.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.7.ULTIMATE.RTM.WITH.SP1.X86.RETAIL.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.7.ULTIMATE.RTM.WITH.SP1.X64.RETAIL.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.7.ULTIMATE.RTM.WITH.SP1.X86.OEM.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.7.ULTIMATE.RTM.WITH.SP1.X64.OEM.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.7.ENTERPRISE.RTM.WITH.SP1.X86.VOLUME.OEM.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.7.ENTERPRISE.RTM.WITH.SP1.X64.VOLUME.OEM.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.SERVER.2008.R2.RTM.WITH.SP1.X64.VOLUME.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.SERVER.2008.R2.ENTERPRISE.RTM.WITH.SP1.X64.VOLUME.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.SERVER.2008.R2.FOUNDATION.RTM.WITH.SP1.X64.OEM.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.SERVER.2008.R2.HPC.RTM.WITH.SP1.X64.VOLUME.ENGLISH.DVD-WZT MICROSOFT.WINDOWS.SERVER.2008.R2.HYPERCORE.RTM.WITH.SP1.X64.RETAIL.ENG.DVD-WZT MICROSOFT.WINDOWS.7.LANGUAGE.PACK-1.WITH.SP1.35.LANGUAGES.RTM.X86.DVD-WZT MICROSOFT.WINDOWS.7.LANGUAGE.PACK-2.WITH.SP1.CHINESE-TAIWAN.RTM.X86.DVD-WZT MICROSOFT.WINDOWS.7.LANGUAGE.PACK-1.WITH.SP1.35.LANGUAGES.RTM.X64.DVD-WZT MICROSOFT.WINDOWS.7.LANGUAGE.PACK-2.WITH.SP1.CHINESE-TAIWAN.RTM.X64.DVD-WZT MICROSOFT.WINDOWS.SERVER.2008.R2.LANGUAGE.PACK-1.WITH.SP1.ALL.LANGUAGES.RTM.X64.DVD-WZT MICROSOFT.WINDOWS.SERVER.2008.R2.LANGUAGE.PACK-2.WITH.SP1.CHINESE-TAIWAN.RTM.X64.DVD-WZT MICROSOFT.WINDOWS.7.LANGUAGE.PACK.RUSSIAN.WITH.SP1.RTM.X86.RIP-WZT MICROSOFT.WINDOWS.7.LANGUAGE.PACK.RUSSIAN.WITH.SP1.RTM.X64.RIP-WZT MICROSOFT.WINDOWS.7.LOCALPACK.RUSSIAN.WITH.SP1.RTM.X86.RIP-WZT MICROSOFT.WINDOWS.7.LOCALPACK.RUSSIAN.WITH.SP1.RTM.X64.RIP-WZT MICROSOFT.WINDOWS.SERVER.2008.R2.LANGUAGE.PACK.RUSSIAN.WITH.SP1.RTM.X64.RIP-WZT MICROSOFT.WINDOWS.7.LOCALPACK.WITH.SP1.20.LANGUAGES.RTM.X86.DVD-WZT MICROSOFT.WINDOWS.7.LOCALPACK.WITH.SP1.20.LANGUAGES.RTM.X64.DVD-WZT
Just remember that WZOR and Zukona also have to be carefull about their sources. They probably have the ISOs but leaking them now could be bad for their sources (they could be burned). Waiting for another day would do no harm. Except for the patience levels that are critical Cheers