I have a question if i convert XP profesional sp3 to datacenter it's going to recognize My 8 Pentium 3 xeon cpus? Right or it's only the sku?
Maybe. I don't have any real hardware to test ISOs created by ConvertNT5SKUs. XP SP3 Server is not stable on latest public release but it's fine on private releases which I am planning to release but with date being unknown.
I've finally managed to get rid of the driver warnings on x86-based conversions. Patch these bytes in syssetup.dll: Code: Before: DB 39 5D 08 89 45 FC 0F After: DB 85 DB 90 89 45 FC 0F I gave it like that, because offsets vary file to file. Tested on 2600.5512 and 3790.0. Will likely to work well on Betas and Longhorn builds too. @MilkChan, @asdddsa101, @ohault WINNT.SIF is not required anymore. Meaning the driver warnings won't show on upgrades either.
Quick question, will converting Windows 2000 Server Dutch to Windows 2000 Datacenter Server Dutch contain components from Datacenter Server?
Not in current public release, but yes in private releases. Releases up to RC1 only focused on basic things, but now it focuses on components aswell. Converting Server to Server editions did not make much of difference, but there will be differences from now. I really would like to make the private releases public, but some nonsensical bugs prevent me from doing so. I don't have a proper deadline to make latest private releases public. Even though I get really good (even though not perfect) results, beta testers usually don't get good results. This is another thing prevents me from making releases public.
Succeeded for a (Simp.)Chinese version of XP x64 Though some remnant from Server persists and it shows lack of file during text mode setup,it was somewhat useable.
Cool. I removed the Server remnants and made all files copy well (probably you are referring to sounds) on text mode setup. That was because sounds were copied as Chinese strings and Chinese characters were not recognized by default encoding. However I fixed that long before.
Yes, mainly sound scheme files (also someabout XP tour). Server remnant i currently found was SCW and IE enhanced Security (the former one can be removed using nlite though)
Chinese version of Server 2003 x64 actually only had SP2 though. (SP0/1 did not have Chinese version) , so maybe for some reason the codebase change did not influence it (same like how XP SP3 still use old Whistler brand when becomes server , also early XP x64 did refer itself as 64-Bit Edition). Windows XP x64 was initally called "Windows XP 64-Bit Edition for 64-Bit Extended Systems " at early development stage
Released RC2 version after a long time. If you find any bugs that I don't know, you can report them. I'll make patches based on the RC2 version. The release won't be pulled, you can apply bugfixes over the release by overwriting files. Also this release is likely to be the latest feature-based release. Further versions will be focused on bugfixes.
Converting Windows Server 2003 (Base) to Windows XP Home (Target) results in internet not working. It also seems as a result that the oobe after install takes a long time to load.
You need to tell me what ISOs did you use. I need to know about the base edition, architecture, language and service pack level. I am aware of slow oobe loading on 3790. However I don't think there's something I can do about that. About the internet is it about the driver? If it's about driver I'll check, but if it's about the Internet Explorer it's normal for 17 year old browser to not work today. Spoiler: Off topic I also forgot to tell that I reuploaded the rc2 release due to a severe bug on x64 conversions. But I won't do that again unless another severe bug was discovered.
Base ISO is Windows Server 2003 SP2 Dutch, Target Edition is Windows XP Home SP3 Dutch. Both x86. I don't think it's related to drivers or Internet Explorer, as any other browser does not work either.
I converted Windows Server 2003 x86 SP2 to XP, but during GUI installation, Setup prompts the file taskman.exe and updshell.htm are required. Strangely the two files are correctly located in the i386 folder. And, some Chinese characters in the billboards can't be displayed. For example, one of the billboards likes this: "计算机运行更 、更可靠", which should be "计算机运行更快、更可靠" And, device drivers are not digitally signed after Setup. When installing OS built-in drivers, I get driver signing warnings such as Audio Codecs and Media Control Device.