![]() I had to install xterm and run an installation script that downloaded a bunch of stuff. Personally, I find Multisystem's specific solution to creating a USB XP installer undesirable. It does work, however, it uses the method of loading the whole iso into memory in conjunction with Firadisk, as the above link discusses. If you really want to do that method, see this: Įdit: Just tried Multisystem (a Linux app) for making a USB drive bootable into the XP installer. The method of loading the whole iso into memory and booting it usually results in a blue screen at some point. Just note that you will need to make a second hardware profile, because Windows configures itself to a specific hardware configuration during the first part of the installation, and the hardware platform conjured by the hypervisor is not the same as your real hardware platform. Yes, a "real fake" as opposed to a "fake fake".). You could also try to use QEMU or VirtualBox where you actually make one of the VM's hard drives be your real target hard dirve, and simply have the hypervisor boot the iso like a CD (actual hardware emulation, not BIOS disk emulation that Grub4DOS does. Make a bootable USB to install Windows XP from Linux However, it is a Windows-only utility (that is unsupported by Wine), so follow the tutorial here (the big post): WinUSB does not do this, UNetBootin does not do this, the diskpart tutorial does not do this, WinToFlash does not do this, and bit-banging the iso onto the device with dd does not do this. Modified copy of txtsetup.sif copied to the root level ![]() Special stuff in the bootsector of the partition (use ms-sys). Unless you have a modified SETUPLDR.BIN, it won't work from USB directly. I haven't tried it yet, but can be doable - build script, that run OOBE instead running OOBE directly.Ģ) Remove all others user accounts - there should exist only glitch on Home edition as original unusable Administrator is renamed to AdministratorN and new Administrator account is created.OP asked how to make a USB windows XP intaller: Idea to investigate is - switch into OOBE after all these steps are finished - can be done in RunOnceEx as last step. all applications are automatically installed using RunOnceEx all drivers are automatically installed using SDI What is done by default on 1.4 - we can call it audit mode What can be done in currect OOBE on ProfessionalĢ) Insert product key - can be skipped using oobeinfo.ini instead of sysprep.infģ) Change Computer name - "WXPSysprep" is set as default I know what you are looking for - full OOBE same as you can see only in standard setup. but otherwise it has only disadvantages compared to a clean installation The only advantage is the hyperfast installation. ![]() Now I begin to understand why SysPrep started spreading from Windows Vista (and especially Windows 7) Then the computer name is not reset as well as other things. among other things, I noticed a new bug, after the creation of the SysPrep (even the simple one) when I open an account on the control panel it exits an error. It starts as administrator, at each installation I should create a new account from the control panel. The problem is that this project, based on the Russian SysPrep, modifies a lot of registry strings. OK you can delete it while creating the SysPrep by going to safe mode. In Windows XP this is not possible, the account remains. from Windows Vista to create a SysPrep you go to Audit mode, so you don't create any accounts and everything remains clean. The idea was nice but unfortunately looking at the whole SysPrep on Windows XP (or earlier) is not as clean as from Windows Vista onwards.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |