I want to DIY an XP64 ISO from "2003 Enterprise x64 SP2" as base and "XP Pro x64 SP2" as target. Questions below: 1. How can I edit CNT5SKU script to create an XP64 with both full XP comps and as more 03 comps (including those belong to R2) as possible? Additionally, how to fix bthprops.cpl and irprops.cpl missing prob? 2. I used cn_win_srv_2003_r2_enterprise_x64_with_sp2_vl_cd1_X13-47314.iso but it recognized as SP0. Why this and will it bring any possible faults? 3. When I target "XP SP3 x86" with the same base ISO, almost all XP comps were missing including user profile pic. Why? 4. Base zhs, target enu, so XP comps on the converted "XP64 zhs" was in enu. Given there were MUI on enu XP64 for zhs-ers to change the disp lang of those comps in zhs, I attempted to apply MUI (including 03 MUI and XP MUI) on "XP64 zhs" to change the lang displayed, it refused popping "The Windows Multilingual User Interface Pack can only be installed on versions of Windows with a matching (or later) build version number" though both base and target were 3790. I tried regedit "InstallLanguage" into "0409", failed. How can I unify disp lang further? PS:My Computer is Clevo P870DM1, with E-2278GEL CPU, mGTX 980 GPU, 4*32GB SO-DIMM DDR4-2666, 2*2TB HDD (MBR, sys partition). So, I have to use EE to make full use of all 128GB DRAM but there're only VL edition for EE zhs and no DC zhs at all.
1. You can't have R2 components for Professional x64 Edition, because it is not an update to be slipstreamed. 2. cn_win_srv_2003_r2_enterprise_x64_with_sp2_vl_cd1_X13-47314.iso is recognized as SP0, because Server 2003 x64 international releases don't have a file named SP2.CAB in AMD64 folder. Service packs are determined by those files. 3. This is weird. Normally the script is supposed to skip directly to Step 6 for such conversions (like Pro -> Pro). I didn't have problems related to it so far. 4. This is expected because the binaries on XP x64 ISO were compiled for English. If you really want fully Chinese XP x64, you can try Server 2003 x64 CN as Base; Professional x86 CN as Target. This should work.
1. Can I decompress R2 inst ISO and extract the components manually to integrate using modified ConvertNT5SKUs? 3. My meaning is that "03 EE x64" as base and "XP Pro x86" as target leads to component missing.
cn_win_srv_2003_r2_enterprise_x64_with_sp2_vl_cd1_X13-47314.iso and zh-hans_windows_xp_professional_with_service_pack_3_x86_cd_vl_x14-74070.iso
I understand now. I got the same error, related to Enterprise Server base ISOs. I have to remove some entries related to tshootas.inf in .txt files. If an inf entry specified in syssetup.inf cannot be found, Start Menu entries part is skipped entirely. Try with this base ISO for now: cn_win_srv_2003_r2_standard_x64_with_sp2_cd1_x13-28810.iso. I reuploaded b2 release. It should be fine now.
While target="zh-hans_windows_xp_professional_with_service_pack_3_x86_cd_vl_x14-74070.iso", no matter whether base="cn_win_srv_2003_r2_standard_x64_with_sp2_cd1_X13-28810.iso" or "cn_win_srv_2003_r2_enterprise_x64_with_sp2_vl_cd1_X13-47314.iso", the output system has no games like minesweeper. Though user profile appears these two times, component "User Account" can NOT be opened.
Released Beta 2.1, thanks for detecting issues related to AMD64. This release should fix these errors now.
When I test with 03EEx64 base and XPx86Pro target, user account still can't be opened which means clicking the profile picture in Start menu results in nothing. taskmgr shows rundll32(both x64 and x86) starts and stops after a very short time. Additionally, in Programs folder in Start menu, for sub-folders "附件" and “启动”,there're two namesakes for both, while the contents inside are different.
I guess I have to integrate more stuff to AMD64 Server -> x86 Pro from AMD64 Server -> x86 Home conveersions. As for the second, I don't know why does it happen though. At least games should have been fixed.