I have XP2ESD on a Precision M20 with a mSATA-IDE converted SSD but I haven't checked if TRIM is working and/or if it correctly aligned.
I'm working on TimeZone fix right now. These steps are needed to be done. 1) Install Windows 10 21H1 into VirtualBox 2) Export TimeZone keys in "XP" format and place resource string ID into key value 3) Convert REG to INF 4) Import TimeZone UpdatePacks INF lines into Excel table and use text to column by , 5) Import converted registry to INF to Excel table and use text to column by , and remove all " and spaces 6) Concat and lookup first three columns 7) Now every UpdatePack String ID have it's own TZRES string ID from Windows 10 8) Lookup these string for all 24 languages from related TZRES.dll.mui These steps are needed to be able to fix current TimeZones strings. But there are a lot of new TimeZones in Wndows 10. I think I can add these new too and update TZI value on old mapped ones. Bad is that every TmeZone settings needs to have MapID value - I will add simply 1,1 to fake position on map Hopefuly I can manage all of these steps in next few days. I decided to completely update TimeZone settings with these ones from Windows 10 21H1 EDIT: I prepared three scripts to make this easy again in future. Now I need to install and update latest Windows 10 and install 24 language pack. Progress seems now without problem
This seems like TimeZone addon is not installed as after my Addon are not time strings in GMT, but in UTC. When you boot into desktop and manually install TimeZone.inf do you see fixed TimeZones when you try to adjust clock time? I have not tried it on Russian Windows yes and I'm not tried to see it in OOBE, only directly in registry - English and Czech works. I will try Russian build tomorrow. Currently I'm testing full process on English images. Code: en_win_srv_2003_r2_datacenter_with_sp2_vl.iso en_win_srv_2003_r2_enterprise_kn_with_sp2.iso en_win_srv_2003_r2_enterprise_kn_with_sp2_vl.iso en_win_srv_2003_r2_enterprise_with_sp2.iso en_win_srv_2003_r2_enterprise_with_sp2_vl.iso en_win_srv_2003_r2_standard_kn_with_sp2.iso en_win_srv_2003_r2_standard_kn_with_sp2_vl.iso en_win_srv_2003_r2_standard_with_sp2.iso en_win_srv_2003_r2_standard_with_sp2_vl.iso en_win_srv_2003_r2_sbs_with_sp2.iso en_win_srv_2003_web_with_sp2.iso en_win_srv_2003_web_with_sp2_vl.iso en_win_srv_2003_whs_with_sp2.iso en_windows_xp_home_k_with_service_pack_3_x86_cd_x14-92386.iso en_windows_xp_home_kn_with_service_pack_3_x86_cd_x14-92388.iso en_windows_xp_home_n_with_service_pack_3_x86_cd_x14-92393.iso en_windows_xp_home_with_service_pack_3_x86_cd_x14-92413.iso en_windows_xp_mediacenter_with_service_pack_3_x86.iso en_windows_xp_professional_k_with_service_pack_3_x86_cd_x14-92430.iso en_windows_xp_professional_kn_with_service_pack_3_x86_cd_x14-92432.iso en_windows_xp_professional_n_with_service_pack_3_x86_cd_vl_x14-78118.iso en_windows_xp_professional_n_with_service_pack_3_x86_cd_x14-92445.iso en_windows_xp_professional_with_service_pack_3_x86_cd_vl_x14-73974.iso en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso en_windows_xp_tabletpc_with_service_pack_3_x86.iso en_windows_xp_tabletpc_with_service_pack_3_x86_vl.iso If everything goes well, I will finish 2003 Update Packs run XP2ESD v1.6 on all XP and 2003 ISO - this will be like 4 days Auto-Sysprep process.. EDIT: Test relaunched due small bugs in my input ISOs
Hello Mr. George King Thank you for your work but why do you do on Windows XP it's no longer supported by Microsoft and update are completed? stop post ready 2019 More security for this bone What interest if you could tell me because it was a fan of Windows XP
Another issue with timezones Why Russian version don't choosing GMT+3 (Moscow, St. Peterburg) timezone automatically?
@sleonov97 Yes, v1.5.6 have broken default TimeZone setting during Auto-Sysprep. It's fixed in upcoming v1.6 (Hopefully should be released in few days) This is where is broken settings in public version. Code: REM Set LanguageGroup and TimeZone if !Language! == "0419" set LanguageGroup=5 && set TimeZone=145 In words it means Cyrillic + Russian Standard Time (GMT+03:00) Moscow, St. Petersburg, Volgograd as default. In v1.6 it works correctly
Server 2003 SP1 ISO needs to have manually integrated SP2 before using XP2ESD. Windows XP with SP2 needs integrated SP3. All mentioned editions and license types are supported. I want only update CaptureVHD.cmd before releasing v1.6 for public. And I need to spend some hours to rewrite first post with all needed informations