PXE boot?

  • Release Candidate 6
    Guest:
    We are at a “proposed final” true release candidate with nothing known remaining to be changed or fixed. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in:

    This forum does not automatically send notices of new content. So if, for example, you would like to be notified by mail when Steve posts an update to his blog (or of any other specific activity anywhere else), you need to tell the system what to “Watch” for you. Please checkout the “Tips & Tricks” page for details about that... and other tips!

    /Steve.

drwtsn32

Active member
Sep 19, 2020
43
14
Anyone get this to work with PXE boot? (I have PXE set up on my network to boot to dozen+ utilities.)

I tried booting the IMG file but it didn't work for me.
 
Does PXE booting automatically imply non-EFI booting? I've never played with it, so I don't know if there are any ties to legacy booting.
 
No it doesn't.

PXE booting exists in all three UEFI, EFI and legacy modes. Depends on what architectures your PXE server offers.
The booting firmware, (U)EFI or UNDI, will send out a different DHCP architecture option for themselves.
 
Yeah I'm doing legacy boot for sure.

Is there a way to write the IMG to a standard 1.44MB floppy disk image? That's how I boot many utilities with PXE. Alternatively an ISO would also work.
 
Yeah I'm doing legacy boot for sure.

Is there a way to write the IMG to a standard 1.44MB floppy disk image? That's how I boot many utilities with PXE. Alternatively an ISO would also work.
1.44 MB Floppy disk image
It currently places rs.exe in a small 128 kb RAMdrive but it can be disabled in autoexec.bat ( if you prefer to stay on A: )
 
Thanks @millQ, will check it out...
I started AIOBoot-v0.9.9.19 and then PXE booted for the first time :)
(I first made an .ISO from the .img file) and it did not like the splash screen(hangs after enter is pressed :( (no hang when booting from USB)).

So if you have the same problem, then use this Autoexec.bat file instead
(and if you don't need a RAMdrive...then just remove the RAM.BAT line)

Code:
@echo off
SET PATH=\;\FREEDOS
SET DIRCMD=/OGN /Y
SET COPYCMD=/-Y

CALL FIXPATH.BAT
CALL RAM.BAT

fdapm apmdos
alias reboot=fdapm warmboot
alias shutdown=fdapm poweroff
alias edc=edit \config.sys
alias eda=edit \autoexec.sys
menu
 
I started AIOBoot-v0.9.9.19 and then PXE booted for the first time

I'm not really following this part. AIOBoot looks like a USB boot creation utility, maybe similar to YUMI (which I use quite a bit). I'm not sure how a USB boot utility relates to PXE booting.

By the way, I tried your image file and it wouldn't PXE boot for me. I didn't have time yet to try and troubleshoot why. Strange....
 
I'm not really following this part. AIOBoot looks like a USB boot creation utility, maybe similar to YUMI (which I use quite a bit). I'm not sure how a USB boot utility relates to PXE booting.

By the way, I tried your image file and it wouldn't PXE boot for me. I didn't have time yet to try and troubleshoot why. Strange....

It looks like that, but instead it fixes the menu for the pxe boot => Tiny PXE server 1.0.0.23

I decided to download the Tiny PXE server(for windows portable version) separately
and then by hand editing the files to boot a floppy image file instead
..and this time it had no problem with the splash screen :)

Code:
C:\pxesrv\files\menu.ipxe


item --gap -- ------------------------------ Advanced ---------------------------------
item readspeed  ReadSpeed (using Memdisk)
item spinrite60 Spinrite6.0 (using Memdisk)
item spinrite61 Spinrite6.1 (using Memdisk)


Code:
C:\pxesrv\files\menu.ipxe


######################## other items

:readspeed
kernel ${boot-url}/memdisk
initrd ${boot-url}/images/readspeed.img
boot

:spinrite60
kernel ${boot-url}/memdisk
initrd ${boot-url}/images/spinrite60.img
boot

:spinrite61
kernel ${boot-url}/memdisk
initrd ${boot-url}/images/spinrite61.img
boot

tinyPXE.PNG
 
Last edited:
I'm also using iPXE and memdisk to boot floppy disk images and ISOs. But it didn't work for me with ReadSpeed.img, presumably because of what has previously been discussed - it's not a floppy image. It also didn't work with the custom img file you provided in the mega.nz link. Your custom img file worked for you with iPXE?
 
I'm also using iPXE and memdisk to boot floppy disk images and ISOs. But it didn't work for me with ReadSpeed.img, presumably because of what has previously been discussed - it's not a floppy image. It also didn't work with the custom img file you provided in the mega.nz link. Your custom img file worked for you with iPXE?
I used my floppy image RSRAM02.img
and renamed it to readspeed.img
and yes it works everytime.

The file you download is 1.4 MB (1 474 560 bytes)?
 
The file you download is 1.4 MB (1 474 560 bytes)?

Yep, it's exactly the same size as my other floppy images.

I figured out the issue - I was PXE booting a DOS virtual machine that only had 4MB RAM assigned to it. I used a different DOS VM that had 16MB RAM and it worked fine. So...... user error!
 
it did not like the splash screen(hangs after enter is pressed

I have tested PXE boot on a few machines and all hang at the splash screen as well, so I commented it out of autoexec.bat.

I also PXE boot SpinRite and have no issues with its splash screen, interestingly enough.

Thanks again for making the PXE boot version!
 
Trying to get SpinRite 6.1 SRPR-053 to work PXE using iPXE memdrive and it hangs with just cursor _ with both DOS 6.22 and FreeDos 1.3 But 6.0 works fine
I created a SpinRite.img with spinrite.exe in Windows and then edited it and saved it as SpinRite61.img while adding srpr.exe and modifying config.sys to be the following

config.sys
=-=-=-=-=-=-=-=
DEVICE=SRSPLASH.SYS
SHELL=srpr.exe
=-=-=-=-=-=-=-=

/pxeboot/config/boot.ipxe
=-=-=-=-=-=-=-=
set os_root os-images/spinrite61
kernel http://${server_ip}/${os_root}/memdisk
initrd http://${server_ip}/${os_root}/SpinRite61.img
boot
=-=-=-=-=-=-=-=

I have booted the SpinRite61.img in VirtualBox and it runs fine but when I boot via iPXE with memdisk I see the 6.0 splash screen and then just a blinking _ cursor. Also, same results with DOS 6.22 and FreeDOS 1.3 img's.

Any Suggestions?

Thanks
 
I decided to download the Tiny PXE server(for windows portable version) separately
http://erwan.labalec.fr/tinypxeserver/pxesrv.zip
Ummm I hope you used the necessary precautions, because my PC blocked that download and said it had a virus... so I went to virus total (see attached.) I also looked at the Windows Defender report, and I find the reference to Android strange, and it says "unwanted behaviour" so I don't know... but I'm unwilling to install or investigate further because I don't want to risk it.
 

Attachments

  • PHolder_2023Oct25_PXEServerVirusTotal.png
    PHolder_2023Oct25_PXEServerVirusTotal.png
    295.6 KB · Views: 81
  • PHolder_2023Oct25_PXEServerWindows.png
    PHolder_2023Oct25_PXEServerWindows.png
    12.7 KB · Views: 73
Last edited:
Trying to get SpinRite 6.1 SRPR-053 to work PXE using iPXE ...

I tried the same procedure as you. Edited the SR 6.0 disk image and replaced `sr.exe` with the new executable. I also removed the DEVICE line from config.sys.

In VMware workstation, I do a PXE boot and get as far as the main screen for SR 6.1 where it shows my name and serial number. But it hangs at that point.

On a physical machine (early gen ThinkPad X1), it doesn't even get that far and just hangs after 'InitDisk'.
 
Trying to get SpinRite 6.1 SRPR-053 to work PXE using iPXE memdrive and it hangs with just cursor _ with both DOS 6.22 and FreeDos 1.3 But 6.0 works fine
Hah, I just posted about this on the newsgroup over the weekend :p

Unfortunately I have had the same experience; 6.0 runs fine booted PXE with memdisk (been using it that way for several years) but 6.1 currently does not. I've been messing with it a bit on and off for a few days but haven't made any useful discoveries.
 
Ummm I hope you used the necessary precautions, because my PC blocked that download and said it had a virus... so I went to virus total (see attached.) I also looked at the Windows Defender report, and I find the reference to Android strange, and it says "unwanted behaviour" so I don't know... but I'm unwilling to install or investigate further because I don't want to risk it.
I used it a couple of years ago...2021, so I don't know if they changed anything in the code 2023.
I used a VM so I am not too worried :)