boot iso XP legacy
Hi all !
I have a problem to boot Windows XP isos on computers in legacy mode with ipxe. I have an error message: memdisk bootstrap too large to load.
No problem with other installations with wim files.
Can you help me?
I found a solution. I am using WinNTsetup4 which I run from winPE and it works. I don’t know what else he does but it works so I won’t look. Thank you for helping me !
@george1421 same probleme whether on physical machines or hyper-v virtual machines. And I am in IDE and not in AHCI in both cases
I did a little google-fu and found these two article that may help you get started.
The first one uses a bartpe environment. The instructions are for syslinux pxe booting but they can be converted to ipxe pretty easily.
This one is a bit more detailed, but it looks interesting and most likely will work without a bartpe image. The bootfloppy files from the sourceforge site looks interesting too.
@bluedark Well its now getting stopped at preparing for the installation. I would think at this point it should try to partition and format the disk. This might be a hardware issue in that XP may not understand the disk controller installed. I remember issues between <something> and ahci mode. If you didn’t have the drivers for ahci mode the system would fail to install.
So are you trying to install under a hypervisor or a physical machine? Right now we don’t know if the fault is in the winpe image or the XP installer.
@george1421 I have something new.
I recreated a winpe image with adk under windows 8.
This time when I run winnt32 I can start the installation, as the screenshot shows :
BUT after 2 or 3 minutes I automatically come back on the winpe command prompt …
@bluedark See this is where I was saying about WFWG and lanmanager protocol. You have to realize this is a 20 year old OS so my mind is a bit fuzzy, but you need to boot DOS mode where WinPE is probably running in 32 bit mode. I know I did it back in the day… or we just booted off a USB stick with all of the installer files on it.
See if you were using FOG and captured the XP image fully installed, sysprep it and then you could deploy it to other like hardware.
edit: Hmm this looks interesting https://www.netbootdisk.com/
@george1421 in fact, I have the impression that when I want to start the installation of XP with the iso from a minimum vista machine, it does not work. From a machine already in XP, ok, the line is not grayed out. How then to start installations of XP from winPE?
@george1421 I test on several different machines (HP, dell, …) and also on virtual machines on hyper-v. Always the same problem
@bluedark What hardware are you trying to install XP on? Manufacturer and model?
@Tom-Elliott yes I can install XP with this iso
@bluedark And you’re 100% certain this ISO is capable of installing XP?
@Tom-Elliott the iso is 600MB and the machines are 4GB
Exactly how large is the ISO, how much memory is available to the machines you’re trying to load the ISO from?
If the ISO is 2GB for example, then you need at least 2GB of RAM for the ISO to load to the machine.
@george1421 no need for the -n switch, the winpe boot in legacy as well as uefi.
I can see the disk and partitions from winPE (verified with diskpart).
I do a clean on the disk.
I try to install XP in pxe from several different workstations and I also test on hyper-v virtual machines.
Always the same problem…
@bluedark OK I see the issue I was having. You said a few things that didn’t link with the way FOG works. I was under the impression you were using FOG as a netboot server as outlined in this tutorial: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images
FOG is a disk imaging tool, where you create a golden/master/mother image on a computer, then capture that image with FOG and deploy that image to many computers. FOG is built on top of other open source projects like iPXE, ISC-DHCP, rEFInd, etc. Within FOG’s web ui there is a utility that FOG Admins can create custom iPXE menus to do other things (like netbooting) that is not related to FOG imaging. I had the impression you where reusing FOG for netbooting and not for imaging as it was designed.
I can offer you a few tips with your ipxe menu. From what I can see of the screen shot of the ipxe menu your winpe entries will (should) only boot under bios, for uefi booting you need to use the -n command switch as in this post: https://forums.fogproject.org/post/103331
Remember you can use different protocols for netbooting beyond nfs. You can use http which is very scalable and fast protocol.
You are running winsetup on your winpe instance. Can winPE see the target disk?
Can you run diskpart from winpe and remove all partitions on the target computer?
What target hardware are you trying to install XP on?
@george1421 thank you very much for your reply.
In fact, I don’t see concretely what is FOG used for compared to ipxe?
Currently I have my ipxe which is on my dhcp server and which will look for the installations which are on my nfs server.
I don’t have a web user interface.
Here my ipxe config (sorry in french) :
UI on boot pxe :
And my problem setup XP on winPE :
Thinking back here. We are talking about XP, so that means no nvme, uefi, sata raid, (I’d question ahci disk mode too). I also seem to recall if the target disk had files on it it wouldn’t go through the install XP path, but you had to upgrade path. So assuming the hardware can meet the other requirements of XP make sure there are no partitions on the target hard drive. You still might need the F6 disk drivers so XP can see the disk adapter.
I’m just thinking of reasons why it won’t work. (the remote xp setup mode that is)
@george1421 What does you iPXE menu look like. Can you show me a screen shot of the web ui configuration page?
Also what version of FOG are you using? I understand you are not using fog for imaging but that may also give us a clue. I have had someone post FOG is not working and they were using 0.30 version of fog (hint 10 years old version).
@bluedark WFWG is Windows for workgroups. It predates windows 95.
Well if its less than 2GB we need to rethink this error.