I updated the tutorial - in Win7 (and probably 8, 10 and 11) instead of using a full Administrator account, can be used account with administrator's permissions but you need to disable UAC and restart the system.
I fix sysprep.inf because the USB keyboard and mouse not yet operate at stage Welcome & License: Code: [Unattended] OemSkipEula=Yes ... [GuiUnattended] OemSkipWelcome=1 USB devices (e.g. keyboard & mouse) only work after this step - when the progress bar exceeds half: Also replaced MS Paint to IrfanView 64-bit (iv.exe) in boot.wim & install.wim files.7z and sysprep.7z updated
Nope, the modified MUI is based on the build 3790.0, much like 32-bit Server 2003 MUI's do. A proper 64-bit MUI should be based instead on 3790.1830. Using a registry script which forces system to use the provided files, and patching it up with MCE 2005 MUI files is not a correct way to fix all the flaws that are in it.
F..k! Why MUI? Even the Polish version of WinXP 32-bit is not perfectly translated e.g.: Code: The time sample was rejected because: The peer's stratum is less than the host's stratum. Polish version: Code: Przykład godziny został odrzucony, ponieważ: Warstwa końcówki jest mniejsza od warstwy hosta. This was translated by an idiot I don't understand people who install some s**t MUI after which the system looks worse than the original English version
Of course. It was just my first thought, that newer MUI for XP will fix lack of translation. Later I tried it without copying these files and worked as before, so I assume that any of XP MCE's files aren't touched at all. When I mentioned wrong values, it is about known bug with Windows XP - msfn.org/ board/ topic/ 177950-change-language-of-an-updated-xp/ (still I can't link because of 5 posts rule) I know some English, you know English, but (for example) my parents not really -- they had contact with English language only with DivX movies with subtitles Windows XP's translation wasn't bad, I think is quite good compared to older OSes. My personal "best" Polish translation was from Windows 95 setup - "Udoskonalone wideo przyspiesza akcję gier". Even if I'm native speaker, I don't know what they had in mind... Nie no, wiem, ale się śmieję xD
Forgive, but people who use the system only to watch DivX movies, social media, etc. and so they do not understand what there are advanced OS options even in the native language, so it is no difference in what language the system is in. P.S. I used to configure the system for a lady and asked what a web browser wants to have - Chrome, Firefox? - she replied that she wanted to have onet.pl In addition, you can always use the application in the native language regardless of the language of the operating system:
files.7z updated added new tool to detect boot mode UEFI or Legacy - thanks to this, in Legacy mode, I skipped selected parts of the code required only in UEFI mode cosmetic changes in main script new screenshots in first post
Came back to revisit the project and its working so well now thanks for everything! I am running into an issue though during the install. For some reason I have to re-enter the windows xp key, language etc until it logs me in for the first time.
I have changed it a long time ago - now the xp key, organization and regional options are introduced during installation (mini-setup) - see Spoiler Screenshots mini-setup at the end of the first post in this topic. Do you use updated files.7z and sysprep.7z files? Do not use a sealed system again! This is why there is a step in the tutorial to create a copy of sysprep.vmdk to the vanilla_sfc.vmdk file after installation and SFC replacement to start tutorial from that moment. If you have not made a copy of the sysprep.vmdk file, you need to install the system from the beginning. If in the tutorial I share a new version of sysprep.7z, you always have to do it: delete current sysprep.vmdk copy a previously made backup vanilla_sfc.vmdk as sysprep.vmdk boot VM WinXP then use sysprep.iso from sysprep.7z
One disadvantage is that Windows XP 64-bit is not technically Windows XP at all, it’s a desktop version of Windows Server 2003 64-bit. But the main disadvantage is that 16-bit programs and 32-bit drivers no longer work. So, if you have relatively exotic devices or programs they won’t run anymore. There are only three main issues with XP x64: 1) Driver Support - A lot of lowly manufacturers do not have XP x64 drivers. 2) Application Support - XP x64 has zero support for 16-bit applications. If you have any old 16-bit games or programs, they will no longer function. 3) Installer Blacklisting - Some idiot installation developers have added operating system checks to the installers which blacklist any operating system not explicitly defined in the installer. Basically, that means the installer will refuse to install the software on XP x64 even though it works fine on XP x64. You can work around this one by installing the application on a operating system that isn't black listed and then copy the files over to your XP x64 computer. copied.
Small edit for future users if you'd like to update the original post, tell folks where disable the page file, system restore, automatic updates set Never search Windows Update for drivers set Ignore - Install the software anyway and don't ask for my approval is within xp. Also for testing on a VM, what should people set the OS type to? Windows 7 x64? 10 x64? etc
@stan456 All these settings are under the System Properties - right click on My computer > Properties Testing in a virtual machine is really just for me to check if the startnet.cmd script works well and whether USB3 and SATA drivers work. In a virtual machine, you can always install the original WinXP. I did the guide to install the system on a real (modern) computer