Before i edited the post my question was if i really had to localize winre.wim and also boot.wim #1.. But after localizing Boot.wim #2 I can choose language for windows and setup (obviously) Strangely i didnt have to with SP0 wellwell, im not sure why but still, i shoudnt have to localize boot.wim #2 right?
I never tried, so I don't know. My goal has always been to try localize 100% of the DVD , so I always localized all indexes.
Where to download Windows 7 Pro 32bit with SP1 integrated Upgrade iso. It is version which comes for time period in 2009 year as free upgrade offer from July to October.
I've installed WZOR's leaked W7 SP1 (wave 0/RTM) with no ill effects. It did not seem to install KB971033.. it's still sitting unchecked in my hidden update location. Made a disk image beforehand just in case but all looks ok... still running fine with DAZ' loader.
I heard that MS AIO images have been released too.By AIO i mean x86-64 and all editions for both archidectures in a single image.
Quickpar Patch for WZOR Language Packs Made Quickpar patches for the x86 / x64 TW language packs, this can change the TW language pack from WZOR to the Official Microsoft MSDN image. (You'll need to download + install quickpar to use these patches) Download PAR2 for x64: mediafire.com/?cc9x45ovo5rczsd (835kb) Download PAR2 for x86: mediafire.com/?rcbztcddc4ejruu (824kb) How to Use the patches: 1. Open Quickpar and click open on the lower left, and open the PAR2 file. 2. Click 'Add' and add either the wzor ISO or the 'cab' file. (you'll need to use the LP.cab from the 'langpacks.back' folder for x86) 3. Wait for the scan to finish then click repair. 4. You will get a new ISO which will match the MSDN image. x64 Pic: img193.imageshack.us/img193/7606/twx64.png x86 Pic: img251.imageshack.us/img251/7572/twx86.png SFV Checksums: Code: tw_windows_7_sp1_language_pack_x64_dvd_646888.iso 0E88D997 tw_windows_7_sp1_language_pack_x86_dvd_619609.iso 5C2A11CF
Compared the zh-tw lp.cab: x86 MSDN File: lp.cab CRC-32: 74e5c74c MD4: 89b598a00306b7c484917fc9111521c9 MD5: bf592c73b6091fafee1fd4dc201ab471 SHA-1: 7cf4fa6fb6fe9a674bc793c841643de3ee0c89de Timestamp: Saturday, November 20, 2010, 18:12:07 (PST) x86 wzor leak (\langpacks\zh-tw) File: lp.cab CRC-32: b980bb9a MD4: 03215c35a0a2d3b0b00a85d71a3b8255 MD5: b9735380ea2f86177be50f49d487ffb3 SHA-1: 5f1f20164b4624a0a550c84ecb2099bc8a10c7d6 Timestamp: Friday, January 14, 2011, 14:28:09 (PST) x86 wzor leak (\langpacks.back\zh-tw) File: langpacks.back\zh-tw\lp.cab CRC-32: 74e5c74c MD4: 89b598a00306b7c484917fc9111521c9 MD5: bf592c73b6091fafee1fd4dc201ab471 SHA-1: 7cf4fa6fb6fe9a674bc793c841643de3ee0c89de MATCH Timestamp: Friday, January 14, 2011, 14:28:09 (PST) so the mysterious backup folder in the wzor leak IS the same as the MSDN one!!! WTF? now as for the x64 version: x64 MSDN File: lp.cab CRC-32: eff17c54 MD4: 89486e7783379de96a16b5f7f30d86b3 MD5: 382553933b739d3b5da9cda5af202c38 SHA-1: 516d209d16b0b78c3f7f54df28b1018481912e2a Timestamp: Monday, February 14, 2011, 16:25:38 (PST) x64 wzor leak File: lp.cab CRC-32: eff17c54 MD4: 89486e7783379de96a16b5f7f30d86b3 MD5: 382553933b739d3b5da9cda5af202c38 SHA-1: 516d209d16b0b78c3f7f54df28b1018481912e2a MATCH Timestamp: Saturday, November 20, 2010, 20:27:51 (PST) x64 version is OK, only differences are in the time. If you already integrated a x64 disc using the wzor leak, you are fine! If you have x86 and mistakenly didn't use the lp.cab in the langpacks.back folder, you'll have to do it again!
What the f...? Weird but OK Thanks to 69218 I have uploaded the real zh-tw language packs to my mediafire!
indeed in any case, I have rebuilt my x86 AIO ISO and will be leaving the x64 one alone, since it has been proven that they all match now it's finally time to burn this off!!!
When is it safe to remove the sp backup files? Should I wait a few days? What are the most common problems people have been running into, if any?
I removed them yesterday, even on freshly installed sp1 via windows update on my other 2 machines I've been running sp1 on both a 64bit and 32bit system for a month.... nothing went wrong and I'm going to assume nothing will go wrong with the other 2 also... and if things do go wrong, I now have a working integrated install disc I can use to "repair install"