similar to: mkisofs help?

I'm having trouble getting memdisk 6.03pre18 to boot large floppies and wondering whether I'm doing something incorrectly. 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz 2) gunzip FDOEM.144.gz 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img 5) Use following pxelinux.cfg: LABEL works LINUX syslinux/memdisk INITRD

I need to make a iso image with the filesystem like nero does and i need it for the windows platform not for linux... I need something that does not restrict filenames, it doesn't boder me that are shortnames as long as it let's me access the directory or filename. This is the commandline I use to compile my iso file: %BASEDIR%\isolinux\buildcd\win32\mkisofs -r -log-file log.txt -J -l

On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao Miller, Kenneth Davis, wrote: > [...] Thank you all for your responses. You helped me solve my problem. For anyone else that runs into similar trouble and finds this thread, here follow summaries of what I've learned. To recap, our PXE server holds Dell BIOS updates in FreeDOS floppy images booted via MEMDISK.

> I'm having trouble getting memdisk 6.03pre18 to boot large floppies and > wondering whether I'm doing something incorrectly. > > 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz > 2) gunzip FDOEM.144.gz > 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img > 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img > 5) Use following pxelinux.cfg: > >

tom & peter Hi Guys, I have a little problem I'm hoping you can help me with. When I try to boot toms image, memdisk states a "fractional end sector" while loading the image. It continues with the process until I get a "Booting..." prompt and then freezes. Here's the whole story: A while back I acquired version tomsrtbt 2.0.103, to make a multi-image boot cd as

I need to make a iso image with the filesystem like nero does and i need it for the windows platform not for linux... I need something that does not restrict filenames, it doesn't boder me that are shortnames as long as it let's me access the directory or filename. This is the commandline I use to compile my iso file: %BASEDIR%\isolinux\buildcd\win32\mkisofs -r -log-file log.txt -J -l

> On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao > Miller, Kenneth Davis, wrote: > > [...] > > Thank you all for your responses. You helped me solve my problem. For > anyone else that runs into similar trouble and finds this thread, here > follow summaries of what I've learned. > > To recap, our PXE server holds Dell BIOS updates in

Hello again ! I have another problem and now is with mkisofs... I understand that i cannot use nero to make isolinux bootable cd's but can you help me with mkisofs because i don't understand what all his params do ! I need a iso filesystem like nero does ...relaxed restrictions 31 characters in filename and most important nero doesn't convert "-" to underscores this is

Have been trying some things, but something isn't working at least with using Virtual Box with EFI option. With it off, the cd boots as normal, and works, but with EFI on, it has an error that flashes on screen, and then it drops to a shell prompt. I'm hoping it is just a dumb mistake I am making, and can be resolved. Perhaps I've named the directories incorrectly, or there is a

hi there, hope this is not too much out of topic here... i give it a try anyway :-) when i try to build the iso with: mkisofs i get the following error: [...] Using TTYX2000.;1 for ./dev/ttyX2 (ttyx2) Using TTYS0000.;1 for ./dev/ttys0 (ttyS0) Using TTYY3000.;1 for ./dev/ttyY3 (ttyy3) Using FD0H360000.;1 for ./dev/fd0H360 (fd0h360) Using TTYX1000.;1 for ./dev/ttyx1 (ttyX1) Size of boot

Hello! I have a problem with a bootable cd that i'm trying to make .. The problem is that i don't know what all the mkisofs parameters do and because that weird things happen, if the filenames or directorynames contain spaces they do not open and if i'm in windows's safe mode it gives me an error message stating that the file or folder does not exist! Can anyone help with that?

Hello, I'm Jacques living in France. I have a problem when I use isolinux. I'm working on a multiboot cdrom so I make many "mkisofs" for testing. The problem is that when I modify the "isolinux.cfg" file and then build my image with mkisofs it's the previous configuration of my "isolinux.cfg" which appears on my screen (I run the .iso file with qemu...)

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

Due to limitations of equipment, I have need of using the isolinux boot loader with .iso files generated by roxio. After trying (and of course failing) with an off the shelf version of isolinux, I grabbed the source for isolinux (syslinux 2.11 package) and started looking. It took a few hours to orient myself, but I ended up doing the modification below to isolinux.asm. I then had to write

Please forgive me if this is a known issue or "feature". I didn't notice anything in the list archives or the docs, so I'm assuming this is a bug. I was attempting to create a bootable LFS cd using the instructions found at http://hints.linuxfromscratch.org/hints/boot-cd_easy.txt. I wasn't following the steps exactly as I had some personal changes I wanted to make. One

Hello, I am having a problem with the second-generation of a custom isolinux boot CD for one of the PCs here in the lab. We have three types of PC here - two Dells and one from SGI (a SGI 230). The previous version of the custom bootcd still works on all three platforms. The new version only works on the Dells. It fails on only the SGIs with:

> Hi, > > Pascal wrote: > > mkisofs -o core.iso -b boot/core.img -c boot/boot.cat -hard-disk-boot core/ > > my iso image is ok with qemu on bios and uefi, > > Astounding. As CD-ROM this is not supposed to work with UEFI unless the > firmware emulates BIOS. What particular UEFI firmware did you use ? > > > and with qemu as hard disk on uefi but not on

Hello! I'm trying to boot with a remastered Knoppix 3.4 CD. I burned it with debugging and I get the following output: isolinux: Starting up, DL = 9F isolinux: Loaded spec packet OK, drive = 9F isolinux: Loading main image from LBA = DEADBEF0 isolinux: Sectors to load = D5B7 isolinux: Disk error BE, AX = 42F0, drive 9F A don't understand everything in it and I can't find enough

hello every body, I'm trying to build an isohybrid image based on syslinux able to boot on bios and uefi with optical disk or usb key. I've build a 16Mb hard disk image (core.img) with necessary parts for bios (legacy bootable partition, protective mbr, gptmbr.bin & syslinux installation) and for uefi (gpt, esp, /efi/boot/bootx64.efi & syslinux files). my hard disk image is ok -

when you say """ Unfortunately, syslinux.efi v.6.03 is not capable of booting optical """, you talk about isolinux.bin ? because my iso image with a "good" alternate eltorito boot image (eg. "uefi ready") is booting with qemu (qemu -cdrom core.iso -bios uefi.fd) and is also booting in hard disk mode (qemu -hda core.iso -bios uefi.fd). Le mercredi