similar to: Creating HD Boot Images

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

I read the following about memdisk : .... For any other size, the image is assumed to be a hard disk image, and should typically have an MBR and a partition table. The disk C/H/S geometry is determined by examining the partition table, so the entire image should be partitioned for proper operation. .... I'd like to create a bootable cd, wich boots a linux and some other tools. While

Hello all, I've been following this project with interest, and have had great fun implementing Isolinux within the FreeDOS cdrom distribution. Since I'm not that an expert at Linux, I would like to know how I can *succesfully* generate a bootable image from a partition. Situation is like this: (640MB RAM on system) 60GB IDE harddisk, primary partition 1 win98 500MB extended partition

forgive me.. i have no idea what im asking or if its possible... i have 2 partitions as follows and am using the std windows xp bootloader to boot xp - ntfs (windows xp) - fat16 stupid question is... can i use syslinux, isolinux, memdisk or some combo there of to place a bootable cdrom iso image on the fat16 partition and then have a boot menu with something to the effect of : 1) winxp as

Thanks for Remko for his help to solve the fractional cylinder problem. But there is the second problem, the boot disk failure (see below << [B]) ... command line: initrd=disk.img harddisk c=2 h=256 s=63 BOOT_IMAGE=memdisk Disk is hard disk, 16128K CHS=2/256/63 <<<< [A] ... Loading boot sector... booting... SYSLINUX 2.04 welcome! boot: 1 [single dot]

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 Steve, thanks for jumping in, I've answered your questions below. ---------- Forwarded message ---------- From: steve <steve at steve-ss.com> To: samba at lists.samba.org Cc: Date: Thu, 12 Dec 2013 10:46:15 +0100 Subject: Re: [Samba] [Sambal can't "see" files on NFS mounts using 3.6.15, after upgrading from 2.2.8a On Thu, 2013-12-12 at 01:24 -0800, Linda W wrote:

Hello list, My set up is almost complete in booting DOS through PXELinux, but I need to create a DOS boot image from (2 )DOS floppies. I've search the archives and google but didn't find any relavant info... My current set up now works with the standard setup (with one DOS floppy): kernel: memdisk append: initrd=floppy.img ramdisk=10000 My goal to is create a floppy.img from 2 DOS

Hello, I am trying to boot the extracted contents of an iso, on a usb stick, using the bootsect.bin included in the iso. Yet it will not work. the bootsect.bin file is in the root of the usb drive, as well as syslinux's cfg file. Here is what the cfg looks like PROMPT 1 TIMEOUT 100 DEFAULT main LABEL main BOOT /bootsect.bin -- Karch aka Dimeneira aka Dime

Hi, I use the latest Codeweavers WINE and several DOS programs wouldn't run correctly. Where can I find the best DOS emulator for Linux? Thanks!

(Tested using a Linux bzImage, with and without an initrd.) Per shuffle_and_boot documentation, %ecx must contain the descriptor list byte length, but it's set with such list end address instead. Fix. Signed-off-by: Ahmed S. Darwish <darwish.07 at gmail.com> -- core/bcopy32.inc | 2 ++ core/bcopyxx.inc | 2 ++ core/bootsect.inc | 8 +++++--- core/runkernel.inc |

Hello, I am managing 15 separate boot disks with various network disk images. These disk images are used for network installs of Windows OS's. Basically the network boot disk contains dos, the network drive in question and the connection information to the shared server for doing a ghost install. The problem is the 1.44 disk doesn't hold enough space to accomplish the job. What I

In other words: I'm suggesting to use WinImage as it also allows easy injection of new files *and* updating of already existing files. May I ask which vendor is distributing a DOS FW update that is 20MB? I'd like to see the files. Sometimes you just need the .bin/.rom and the actual FW update EXE and it would fit a 5MB FDD image. On Mon, Jun 18, 2018 at 2:03 PM, R S <rene.shuster at

Create a virtual FAT-formatted floppy disk from a directory of files. For example: nbdkit floppy /path/to/directory The implementation of this is quite different from nbdkit-iso-plugin since we cannot use an external program. Instead this plugin synthesizes the MBR partition and FAT32 structures that are required. To do: Implement bootable virtual floppy using syslinux. This is not

Haven't yet had a need for 10MB FDD images. The biggest I had to create was 5MB (5760kb). At that time I had to use WinImage to create the FDD image and it took me a while to figure out the correct settings. My notes state: "I'm getting 'missing FAT' errors in WinImage, and 7-zip complains about 'unexpected end'. The fix is to increasing the FDD Heads from 2 to 4 and

Hi, on Windows 7 (tested on NTFS file system) and R-devel: 1. file.info("C:/") gives NAs whilst file.exists("C:/") gives TRUE. Instead you have to do file.info("C:/."). 2. Any number of dots will do, e.g. identical(file.info("C:/........."), file.info("C:/.")) == TRUE DETAILS: # C:/ => DISCREPANCY file.exists() and file.info() >

[Redirecting to the syslinux mailing list.] anutma at cmsd.bc.ca wrote: > First of all THANKYOU! > I am a tech at Coast Mountains School District, we have 6 techs and close to > 3000 computers. We have need using Neboot, and have recently switched to grub > using nbgrub. With Memdisk, life has been great (well easier) > What I am trying to do is create a small windows 9x

On 2019-4-12 2:48, Ady Ady via Syslinux wrote: > > I was tempted to reply to several side-topics you have mentioned. I'll skip > them, except for one: the PATH directive is for c32 files only. I am mentioning > this because some readers might interpret the phrase "memdisk do not honor path > command" as if it was some kind of bug; it is not. Thanks for the

The following patch allows memdisk to support compressed floppy images created by WinImage. WinImage creates a PKZIP-style archive with a single member, the .img (or .ima) file containing the floppy image. WinImage names such archives with a .imz extension. This patch lifts the header/trailer checking code from gunzip() to a new function, check_zip(), which both checks for a valid ZIP image and

I am using PXELINUX, ISOLINUX, and memdisk in my project (http://unattended.sourceforge.net/). When memdisk gained support for compressed images, I started using it because it is cool. I used gzip to compress floppy.img to create floppy.imz, and all was good. But now my users are complaining that they cannot use WinImage (a Windows floppy image editing tool) to edit my floppy.imz files. I have