It works fine on my side. I didn't understand why it didn't work on your side. Please send me your kernel32.dll here. Spoiler: Setup Spoiler: Desktop @MolianFrank
The Target and Goal ISO Both are "Windows XP Version 2003 (Simplified Chinese).iso" I made this ISO by infs from leaked source("srv03rtm\mergedcomponents\setupinfs") and chs version of XPSP1 and chs version of 2003RTM
If you actually meant the file "Windows XP Version 2003 (Simplified Chinese).iso" for both ISOs, you're doing wrong. You should never use the same ISO or ISOs with matching Product IDs on ConvertNT5SKUs. Not only that, your ISO filename has spaces. Sadly batch language has limitations on that. It cannot allow filenames with spaces to be used. You should rename your ISO like this: Windows_XP_Version_2003_(Simplified_Chinese).iso Another point is, I don't recommend to use any ISO files other than official MSDN ISOs. They're more likely to include differing bytes to patch which I'm not going to support. Download and use the following, then try again: Code: For Base: cn_win_srv_2003_r2_standard_with_sp2_cd1_x13-13927.iso For Goal: zh-hans_windows_xp_professional_with_service_pack_3_x86_cd_x14-80404.iso Finally, I see that you used VL ISOs. Avoid VL ISOs unless strictly required. Because they're stricter than OEM and Retail ISOs on activation checks. It'll likely to block you from logging in after setup.
First, install any hex editor (I recommend HxD which is free). Then, depending on your version, find the following bytes and replace with their respective bytes. Code: Windows 2000 (5.00.2195): FC 01 00 00 C0 -> FC 00 00 00 00 Windows XP RTM/SP1 (5.1.2600): 10 01 00 00 C0 -> 10 00 00 00 00 Windows XP SP2/SP3 (5.1.2600): 01 00 00 C0 E9 9A -> 00 00 00 00 E9 9A Windows Server 2003 RTM (5.2.3790.0): BD 01 00 00 C0 -> BD 00 00 00 00 Windows Server 2003 SP1+ (5.2.3790.xxxx): 01 00 00 C0 33 FF -> 00 00 00 00 33 FF Windows XP/2003 x64 (5.2.3790.3959): 75 3F BB 01 00 00 C0 -> 75 3F BB 00 00 00 00 After that, you have to re-calculate the hash of the edited DLL file, otherwise text-mode setup will refuse to copy that file. You can either use PEChecksum.exe or CFF Explorer (as GUI) to do that. Next, run the following command to compress to kernel32.dl_. Code: makecab <path to your kernel32.dll>\kernel32.dll Finally replace the file to your ISO. Here is the tricky part for Windows 2000: Kernel32.dll exists in driver.cab/spx.cab, that's why you have to extract both of your cab files to separate folders, replace the file and re-generate full CAB file.
Due a technical problem, I re-uploaded the Milestone 3. Also, I'm trying to backport support for Whistler, .NET Server and Longhorn builds. Here's the list of issues I met so far: Early-22xx builds such as 2202 Server doesn't show up the dialogue for network components. It doesn't set the domain as WORKGROUP, making it impossible to login after setup. Some builds such as 2498 refused to load the second stage setup and ended up with c000021a on VirtualBox and VMware. So, I had to set up on QEMU which took so long to just to complete the GUI-stage setup. Longhorn builds converted to Server doesn't support themes, even if the service is running; you're stuck with Windows Classic. And I'm not planning to support: I386 re-pack builds: Most of them has weird compressed/uncompressed file lists. It usually ends up with winlogon-dependencies with conflicting versions leading up to c000021a. Builds 4031, 4038 and 4066. On those builds, text-mode setup completes. However the GUI-mode setup just doesn't launch or take too long. If you know an expert about builds like these, it'd be better to contact them. Neptune, it breaks at the "Saving Settings" part and it doesn't have anything interesting like "Neptune Server" brandings. Here're some screenshots throughout this journey. Spoiler: Screenshots Lastly, setting a timebomb for Windows 2000 conversions was a problem as setupreg.hiv file had different positions after setupdd part. Now it's fixed.
Supporting major beta/preview builds would already be fantastic because in the development cycle these builds are like milestones with a lot more testing and last minute fixes for better stability. Targeting all leaked builds would be an order of magnitude more complex and time consuming.
Yeah, I already won't focus on fixing bugs that already exist in the leaked build. I'm gonna only focus on the precisely close edition conversion. Beta builds are expected to have more bugs than final releases. If it can't be installed, well you can expect that. QEMU would be the best VM program to use for betas. Spoiler: Windows Server build 2223 with VGA driver installed
I finally released a new build. I called it Beta 1 instead of Milestone 4 since I felt like it became stable enough to upgrade from Milestone to Beta. Here are new screenshots meanwhile developing this build. Spoiler: New Set