similar to: Large Floppy Images

On Thu, Feb 17, 2005 at 16:09:50 -0800, Mikey Sklar wrote > > I use 8MB DOS images with pxelinux to load firmware. Which platform > would you like them for (I have many). I just saw your post and I would definitely be interested in an 8 MB DOS images to work with pxelinux. I have tried the method described in http://people.cs.uchicago.edu/~gmurali/gui/downloads.html but I keep getting

To: Syslinux From: John Plunkett When Syslinux is used with floppy disks with a 1.44 MB format the boot proceeds at a good speed with no problems. When a format over 1.44 MB is used, the boot takes up to ten minutes. Is there a special setting for booting from floppy disks over 1.44 MB's? Is there documentation on how to configure with floppy disks with a format over 1.44 MB's? Thanks,

Hello, i was getting into problems when booting a GRUB bootdisk with memdisk. I get the menu of GRUB, but when i change something to boot (e.g. Redhat installation tool) System freezes after uncompressing kernel. I used either syslinux version of Boot Scriptor and latest standalone version from kernel.org. I hope you are able to give me a clue what is wrong. Thanks in advance. Christian

How does one make a HD image? Floppy images are easy enough, but to have to create a hdimage, you need MBR and partitions, etc... I want to create a 10MB DOS HD and boot it, how would I do this with Linux? Thanks.

Hi Maybe HPA or Murali could help me with this one, or anyone who got the following working. I spend numerous hours reading the list and googling without success. I'd like to create a bootable USB stick and CDROM that will do the following. I will have a menu, from which I could pick a specific dos image (not partition). The dos images could have up to 20Megs in size. The goal is to have

Hi, I'm sorry to bring this up again but I can't quit get this too work. I'm trying to build a 2.88 floppy image so that I can use PXE to load Ghost. I'm useing the following to get a copy of the bootsector: dd if=/dev/fd0 of=bootblock bs=512 count=1 Then I build the image file with: mformat -C -t 160 -s 18 -h 2 -B bootblock x: Then use mcopy to put the required

Hi, I'm the maintainer ROCK Linux (www.rocklinux.org). We are using isolinux on our Install-CDs for x86 systems. We - as most other distributions too - are running in the problem that even minimalistc kernels are slowly growing and sometimes don't fit on 1.44 MB floppies anymore. 2.5.x kernels with initramfs are even bigger than 2.88 MB in some cases... Until now it always has been

It is now possible to build a bootable floppy image which contains HDT, with my patch applied to Erwans HDT branch: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=16b37fe2266c920087f88cdec94243b71218d871 Unpack the Syslinux archive and build whole Syslinux first, then cd to ./com32/hdt/ and make hdt.img $ make $ cd ./com32/hdt/ $ make hdt.img Now you have a 2.88 MB floppy image which

I am using memdisk to remotely flash the BIOS and other firmware. It works well for most flash programs. After the flash I need to initialize the NIC to send a signal to my management server that the flash is complete. I am curious as to how others have solved this problem. Thanks.

It seems that quite a bit of stuff built up very quickly after the 2.07 release: Changes from 2.07 to 2.08-pre6: * Add new configuration command "ontimeout" to allow timeout to have a different action than just pressing Enter. * Add new configuration command "onerror" to allow a custom command to be executed in case the kernel image is

Can anyone please tell me how to create a bootable 10MB hard disk image for use with memdisk? I'd like to use FreeDOS. And I know little of DOS. Thanks.

Hi, I'm working on a Red Hat 7.3 based bootable cd. I have included a number of firmware update floppy images to it succesfully. However, I run into problems trying to build a floppy image for IBM ServerRAID firmware update. The firmware update disk set contains three disks. So their content does not fit into 1.44 nor 2.88 floppy images. To my understanding it possible to build a hard disk

Hi, I did found the problem, a combination of 2 factor. 1- I taught that I did install the latest syslinux, but in fact it was the 3.36 version. 2- Thank to kevin Connelly, he point me to a problem he got with mkdosfs command. The default FAT16 do not work, but the FAT12 do. By adding -F12 to the mkdosfs command fix the problem. The default F16 do seem to work for <8M floppy image. Thank you

Hi. We've been using PXELINUX for years, to kick off OS installations (floppy images) and booting assorted tools. The addition of ISO support in memdisk opened up some new alternatives that we also use, e.g. booting WinPE ISO images over PXE. Today I downloaded a BIOS for a HP EliteBook 8440p and discovered that the BIOS file is 3 MB. I could probably squeeze it onto a 2.88 MB floppy image

Hi all, We are hoping to update our BIOSes remotely with pxelinux and memdisk (it is for a 600 node Beowulf cluster with no floppy access). The DOS floppy loads and starts, however somehow the flash utility 'phlash.exe' or 'phlash16.exe' are both unable to load the provided rom image and just stop doing nothing. It looks like it can't access the rom image somehow, which is

I often boot DOS using MEMDISK and 33MB HD images for remote flashing. After my flash I need to activate the NIC and send a signal. Currently I use different packet drivers for different NICs, but this link below looks like a universal solution: http://www.emboot.com/products_UniversalPacketDriver.htm Does any thing else like this exist that is open source or freely available and freely

Like a lot of people, I am using SYSLINUX + MEMDISK to make a technician universal boot disk on a USB key (I have done the same with ISOLINUX and MEMDISK for a CD using Bart's method for bootable CDs) I *LOVE* Syslinux and MEMDISK, and what I can do with floppy images! I have a few problems that have cropped up, most notably the DOCMEMORY program (www.simmstester.com) boots fing, but the

I have periodically been trying to get memdisk to boot images larger than your average 1.44Mb floppy and have always been unsuccessful. I cannot boot anything greater than 1.44Mb. The systems I'm attempting to do this with are not too old but they are not recent either. One is a Asus P5A and the other is a Intel SE440BX both with the most recent bios firmware patches available applied. If

All: I have recently discovered pxeLinux/memdisk and have been using them without alot of pain in a somewhat unconventional setup.. Win2k DHCP server and tftpd32 on WinXP. Don't throw rocks at me - you use what you've got. Anyways, thanks to HPA for a great tool. I am running into an odd little problem now for which I was wondering if there might be some remedy. On a particular

Hello, I'm investigating ways to boot a DOS floppy image stored on the FAT32 EFI System Partition using Syslinux and Memdisk. The system will be running Win8 using UEFI mode (GPT disks) and secure boot off. Change the Windows efi boot loader is the easy part... With the current syslinux's alpha version (6.0), is it possible to boot the syslinux's efi module from the FAT32 EFI