On the other hand the opposite is true, SKUwitching a client to server removes the lock (unfortunately in W10 it's limited to 4GB even using the highest server SKUs) Obviously it is. It wasn't there in XP SP0 (and SP1 IIRC)
You can’t compare XP SP1 vs XP SP3, they are like two different systems. Really a huge changes accross whole system. XP SP3 doesn’t contain needed code for PAE itself. Thats why we need to use @daniel_k PAE patch instead. On 2003 - 10 use PAE patch by evgen-b.
Yeah, they were likely closer to win2k than XP Sp3 I lost track of what patch I use, when I used it first I spent a day to get the damn thing working reliably, so I kept copying the hal and kernel across new builds, and they never failed since.
Thanks to BF10's ISO Compare program, I am now able to adjust components based on the target edition. Spoiler: Windows XP Home x64 Edition From now Home Edition on x64 will lack components from Professional edition. Just like original Windows XP Home Edition ISOs for x86. @ohault, @acer-5100, @MilkChan, @George King, @Andalu
@example12345678912345678 Looking forward for your progress. Will be really interesting to use your tool to prepare non-existant ISO. Seems like I need then expand some handling for these ISOs in XP2ESD
Code: [For Windows XP/2003/Longhorn 4093:] 1. Open Command Prompt window as Administrator. 2. cd C:\Windows\system32 Make sure the current directory is in fact system32. 3. C:\WherePatchPaeIs\PatchPAE3.exe -type kernel -o ntxpnew.exe ntkrnlpa.exe This will patch the kernel to enable a maximum of 128GB of RAM. [For Windows XP Only, no need for 2003/2000/Longhorn 4093:] 4. C:\WherePatchPaeIs\PatchPAE3.exe -type hal -o halnew.dll hal.dll This will patch the hardware abstraction layer to enable a maximum of 128GB of RAM. 5. attrib -R -A -S -H c:\boot.ini You must change attributes for c:\boot.ini to modify it. Then open c:\boot.ini in text editor: notepad c:\boot.ini [For Windows XP only:] 6. Add the line like this to section [operating systems] in c:\boot.ini: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP (PAE Patched)" /kernel=ntkrnlpa.exe /hal=halnew.dll /fastdetect /pae /noexecute=optin. where "multi(_)disk(_)rdisk(_)partition(_)\WINDOWS" you will copy from existing item in c:\boot.ini [For Windows 2003/Longhorn 4093 only:] 6. Add the line like this to section [operating systems] in c:\boot.ini: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Server 2003 (PAE Patched)" /kernel=ntkrnlpa.exe /fastdetect /pae /noexecute=optin. where "multi(_)disk(_)rdisk(_)partition(_)\WINDOWS" you will copy from existing item in c:\boot.ini 7. Then save changes in c:\boot.ini. You no need to patch the HAL in Server 2003/2000/Longhorn 4093. You no need to patch the loader in XP/2003/2000/Longhorn 4093. 8. attrib +R +A +S +H c:\boot.ini Set attributes for c:\boot.ini to system/hidden. 9. Restart the computer and enjoy. Some stupid 32-bit XP drivers cannot work with more then 4 GB. You may replace it from Server 2003. [For Windows 2000/2003SP0:] PatchPAE cannot run in Windows 2000/2003SP0 now, but you may copy ntkrnlpa.exe from Win2k/Win2k3 to newer version of Windows like XP or 7 and patch it here. All actions for 2000 kernel are exactly same as for 2003 (step 3). Finally, copy patched kernel into Windows 2000 back and add new item in Win2k boot.ini like 2003 (step 5-8). To remove the patch from XP/2003/2000/Longhorn 4093: * Delete line with "Windows XP (PAE Patched)" in section [operating systems] in c:\boot.ini * Delete the files ntxpnew.exe and halnew.dll from C:\Windows\system32.
@George King Thanks The system now recognizes all the installed RAM, but the boot.ini file must be modified by replacing "/kernel=ntkrnlpa.exe" with "/kernel=ntxpnew.exe"
Now same thing applies for the Professional Edition. Professional SKUs will lack Server stuff. I've decided to use an ISO that is only available in Server SKU to prove that. Spoiler: Windows XP 64-Bit Edition v1137 After some tries, I got it. But obviously @George King's syssetup.dll patch wouldn't work there. So I had to replace the syssetup.dll file with pre-patched DLL files. Some people may think it is IA-64 due to 64-Bit Edition branding but it is not. Early versions of Windows XP Professional x64 Edition had the brandings of the Itanium version.
Yes. This is RC1 I think, back on the day I used a slightly older version (Beta1 probably) and it had the Itanium branding, but lacked themes and a bunch of other graphical things. Perhaps such old versions ran only on AMD64, Intel already started to copy the AMD architecture, but Windows was still unaware of that, and BSOD on early Intel 64 bit CPUs
Finally I got both Compute Server and Storage Server SKUs working. First of all most of the brandings were set by ProductSuite registry value. Strings such as DataCenter or Blade were set by a file setupdd.sys. Those were not defined on setupdd.sys, I've decided to replace one of the strings with Compute Server and Storage Server. Both were 15-characters long and I had to find a string with the same length and found Small Business. I replaced it with Storage Server string and got all brandings changed except msgina.dll. Compute Server gave me the same result. Spoiler: Windows Server 2003, Storage Server Turkish x86 Spoiler: Windows Server 2003, Compute Server Turkish x86 Edit: Windows Unified Data Storage Server 2003 SKU added too. Spoiler: Windows Unified Data Storage Server 2003 Turkish x86 To convert to this edition, use SETUPDD.SYS from Storage Server, SETUPREG.HIV file I've provided and add this to AddReg section of HIVESFT.INF. Code: HKLM,"SOFTWARE\Microsoft\ServerAppliance","Edition",0x10001,3 HKLM,"SOFTWARE\Microsoft\ServerAppliance","FSMRefresh",0x10001,1 HKLM,"SOFTWARE\Microsoft\ServerAppliance","OOBEStart",0x10001,0 HKLM,"SOFTWARE\Microsoft\ServerAppliance","R2Refresh",0x10001,1
I added support to create custom editions. Now a SKU can include components from both Professional and Server. Here is the example: Spoiler: Windows Server 2003, Datacenter Edition My next goal will be to create Lite editions.
Thanks to the patch I found for setupapi.dll, now it is possible to convert skus in betas without triggering signature error. But the thing is you still have to set BIOS dates in order to install. Spoiler: Windows Longhorn Standard Server build 3718
I implemented codes for Storage, Computer and Unified Data Storage Server SKUs for x64. Some places say Standard x64 Edition due to ProductSuite value. Some places do not say anything at all as you can see in the screenshot. It bears Standard x64 Edition brandings on msgina.dll only and boot screen is the only place that mentions the respective SKU. Spoiler: Storage Server x64 Edition
I finally figured out to make the Server Manager work on Longhorn Server conversions. The main file was named mys.dll, I found a .hta file and it could be opened via notepad. After that I found out that this program was written by jscript and it obviously wouldn't work on any system with its absence. So I implemented some code that installs the file and registers it. After some trials and errors, I did it. Spoiler: Windows Longhorn Server OMEGA-13 build 5000 P.S: This build is only available in Professional SKU, so the OS in the image is created by the tool. NT 5.1 uses a different executable named cys.exe, so I have to figure the executable out before being able to do the same on NT 5.1.
I'm getting closer to the perfect in ConvertNT5SKUs v3.0.0 confidential releases exclusive to Discord Server members (DM me to join.) Spoiler: Windows .NET Enterprise Server build 2600.1078 I also found a way to get rid of driver warnings for x86-based conversions. Unfortunately I have to use a WINNT.SIF file to skip driver warnings. Note: The Driver warnings are gone only for clean-installs. Upgrades still show the driver warnings. Found out that not-all Longhorn builds were compatible with ConvertNT5SKUs mainly 4066 Server. Now I'm gonna work on that.
I've implemented the Media Center Edition and Tablet PC Editions for Windows XP/2003 versions without Service Pack. Next will be Longhorn, after that I might consider publicly releasing the next version of ConvertNT5SKUs as well as the ConvertNT6SKUs Prototype. I'm terribly sorry for making you wait for months. But it will be worth it I promise. Spoiler: Windows XP Freestyle 3790.srv03rtm Spoiler: Windows LH Freestyle 3683
I made some more improvements regarding Server editions. Spoiler: Windows Neptune Server Windows Neptune Server is not that interesting as you expected. It's just Windows 2000 Server with no "Neptune Server" brandings. Server Manager is not available, because I was unable to find a patch for GUI-mode setup for build 5111. Spoiler: Windows XP Server NT 5.1 It is possible to backport Server Manager from Windows Server 2003 to NT 5.1. All you need to do was having jscript.dll and mys.dll installed via regsvr32. Spoiler: Windows Server 2003 x64 (from Pro x64) I also added support for Professional to Server conversions on x64. However there're some non-severe bugs. I'm in process on having wow64 components copied for 64-Bit conversions.