Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Would like to make a "massive" DOS floppy disk image, say 10MegaBytes or more containing all the firmware updates i need for any system, harddrive, BIOS. i do not need the DOS image to be networkable as everything will be on the PXE booted image, but networking would be nice. Since ZipDisks were attached to the floppy disk controller and were over 100MegaBytes, this should be possible. i tried a long time ago to do this and spent too much time on it only to have it fail to boot. So if someone has reliable instructions on how to create such a nightmarish beast and edit it, please let me know. One image that can used for PXE and copied to a USB stick would be a plus.

Too bad manufacturers don't supply a single bootable Linux ISO containing all their firmware updates, that would be easy to boot over-the-lan and have networking. HP servers do this and it is awesome.

share|improve this question
I don't know the answer but you should check Hiren's Boot CD (or USB stick) and check the different images and boot options that they have there – golimar Jun 29 '12 at 9:12
I couldn't agree more. It's just ridiculous! – Matt H Oct 3 '13 at 2:47

This cannot be easily done but it’s not impossible;

You can craft a bootable FreeDOS ISO containing all your firmware upgrades Then PXE boot that ISO with PXELINUX and memdisk

 KERNEL memdisk
 APPEND iso initrd=FreDosBiosUpg.iso
share|improve this answer
That would get too difficult to maintain. Need to have FreeDOS have networking built-in so it can map a networked drive letter containing all the BIOS images. – rjt Nov 11 '12 at 18:38
Why too difficult to maintain? You do not need networking built-in; the bios images are contained within the ISO. Just boot FreeDOS some bat with a menu and fire the right bios update; perfectly doable and not really hard to maintain. – Pat Nov 11 '12 at 19:27
Rebuilding an ISO to maintain 50 or so BIOS images is nuts. Having one PXE boot of FreeDOS that reaches across the network to a share of downloaded updates would be much much easier. – rjt Nov 24 '12 at 19:14
nuts?? you can build an ISO with a single line command and you call that nuts?? and 10 megs sounds too much for plain TFTP? you know what WDS/MDT/SCCM transfer ~200MB on PE boot.wim images w/o a hitch. Its seems to me you have no idea what you're talking about besides being pretty rude to the one that is giving you an answer. – Pat Nov 24 '12 at 22:51
Pat, i did not mean to be rude and really do appreciate your time. Seems were having some miscommunication. The management of all the images is already out-of-hand and has become much much worse with SolidStateDrives that there is even less time than when i asked this 5 months ago. I have run mkisofs many times, but do not have the time to run fire that up, wait for it to finish, test the PXE boot and rerun it to test different BIOS images. i never said 10MB is too much for tftp, but 10MB can be too much for DOS unless it is handled just right. – rjt Nov 27 '12 at 0:45

memdisk kernel won't be able to load bigger images,

you need to try vmlinuz kernal to load the bigger images, you can find it in the linux mirrors online.. I used one from centos to load some bigger images.

share|improve this answer
Most BIOS update software works with MS-DOS compatible operating systems, not Linux. vmlinuz is Linux, so it would not work. – rjt Nov 11 '12 at 18:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.