similar to: next: booting dos from syslinux/memdisk

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]

From: Ady, Tue, 8 Jul 2014 > [...] every document related to newmkfloppyimg.sh > specifically recommends adding: > floppy c=$CYLINDERS s=$SECTORS h=$HEADS > to the MEMDISK arguments. Good advice. As it turns out, according to the memdisk output, it is already correctly determining CHS. Explicitly specifying the values doesn't seem to have an effect. > You might also want

I'm running into an issue which I didn't expect to encounter. When specifying the "nopassany" parameter to hide physical drives, I'm getting different output from ELTORITO.SYS (v1.5, syslinux distro) such that it fails. My intent is a LiveCD functionality with a DOS RAMDISK program taking over as drive C:, meaning either no FAT partitions on harddisks and removable disks

> Hi all, > > I have observed a problem where, under legacy BIOS booting mode on the > DL360g9, memdisk fails to execute. The same mechanism works fine on the > DL360g8. The system displays the below on the console and ceases to > respond and must be power cycled. Updating the firmware didn't help. > There didn't appear to be any similar issues on the mailing list

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

Im trying to boot memtest86 via pxelinux, memdisk, I found this advice on http://forum.x86-secret.com/viewtopic.php?t=2906 folks are making the image match a floppy size by one of the following: dd if=memtest86+-1.xx.bin of=memtest.img bs=360k count=1 conv=sync or dd bs=360k count=1 conv=sync if=memtest86+-1.xx.bin|gzip > memtest.gz I did the former, it did suppress the warning/errors I saw

Hi, As the subject suggests, I am trying to remote boot a Mini-ITX system. I am using PXELinux as the bootloader, and Memdisk (2.11) as the 'kernel'. My ramdisk image is a hard drive image based on PC-DOS. Two things go wrong during the boot process. 1. "INT 13 08: Failure, assuming this is the only drive" message 2. "Loading boot sector... booting..." message,

On Thu, Feb 2, 2017 at 1:26 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Hi all, > > > > I have observed a problem where, under legacy BIOS booting mode on the > > DL360g9, memdisk fails to execute. The same mechanism works fine on the > > DL360g8. The system displays the below on the console and ceases to > > respond and must be

Hello list, I sucessfully booted some floppy-images within memdisk-2.0.4, but how can I boot a cd-iso-image (for example a bootable eltorito cd). Or does sb. have a wrapper or a skript which can boot an iso-image ? Thanks for any input in advance. tirili tom. -- Thomas Baumann // Postfach 110115 // D-64216 Darmstadt // <tom at tiri.li> -------------------------------------------------

On 07/08/2014 05:55 PM, H. Peter Anvin wrote: > On 07/08/2014 03:05 PM, Alexander Perlis wrote: >> >> Question: what's special about the transition from 8203KiB to 8204KiB? >> Both have CHS=8/64/32 and both involve a fractional end cylinder. > > Fractional cylinders with floppy disks is almost certainly a very bad thing. > Agreed, but that doesn't appear to

Hi, on Intel VX chipset with Realtek 8139 with pxe flash on nic Dos 6.22 is not booting. Dos from win98 is OK. (compressed or uncompressed) Linux is OK. On Intel 815 with lan on board Dos 6.22 is OK. Dos from win98 uncompressed is OK. Dos from win98 compressed is not booting.(gzip run out of data) Linux is OK. Any hint ? I need to boot dos622 on VX Below is screen for VX mobos: Loading

Hi, I'm doing a small hobby project writing some tools to put DOS boot images and Linux rescue images on a USB stick. For this I have partitioned my USB stick in 2 partitions, one 192MB partition with a VFAT filesystem (for the normal use) and a second partition with an ext3 filesystem. My aim was to provide a graphical menu (grub) to access the different images using memdisk. Since

hpa etal, Im trying to get PIRT running on an SBC which has no CD-ROM drive. (an 8 MB ISO which demo's RTAI - RealTime Application Interface, on linux patched with Adeos) (BTW, PIRT uses isolinux) anyway, Im trying to use pxelinux to chainload / memdisk / mboot it, Im having no success. Ive also tried booting memtest86, which I can boot on my laptop using grub, ie title memtest

Hi all, I try to boot an msdos system using pxelinux and memdisk on my PC engines Wrap-2.c card and I have problems with it This is what I see: PXELINUX 3.11 Debian-2006-03-16 Copyright (C) 1994-2005 H. Peter A boot: msdos Loading memdisk.... Loading images/msdos/msd622bd.dosim......................... Ready. dp83815: Setting full-duplex based on negotiated link capability. MEMDISK 3.11

Hi. I'm working on replacing a PXELINUX/MEMDISK loaded DOS based installation image with a PXELINUX/MEMDISK loaded WinPE ISO image. So far everything seems to work well (appending "bigraw" to memdisk solved booting problems on several machines), but I kind of miss the option of using getargs.com to get/set environment variables from the memdisk command line. Is there any way to

- mkdiskimage -d image.dsk 2 64 32 - load it in dosemu and make it bootable with sys - isolinux: label 999 kernel memdisk append initrd=image.dsk harddisk c=2 h=63 s=32 results: memdisk 2.11 -> boots memdisk > 2.11 (up to 3.07) -> hangs The following message is printed in the boot messages > 2.11: MEMDISK: image has a fractional end sector The complete error message

Hello everybody, I want to boot my HP x86 PCs with a Norton Ghost 12 boot disk image via PXE. I followed all the steps but I have still the same message and the booted computer hangs always. 0- I created the boot image. 1- A folder named tftpboot and tpftpboot\pxelinux.cfg created. 2- The pxelinux.0 copied in tftpboot folder. 3- memdisk copied in tftpboot folder. 4- the image file (norton.iso)

I have the same problem. I can not boot a floppy disk. Once I did it but no longer I can do this. I think there is some problem in the new versions of PXELinux. -----Original Message----- From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On Behalf Of Quinn Plattel Sent: Thursday, September 28, 2006 7:04 PM To: syslinux at zytor.com Subject: Re: [syslinux] problem booting

On 07/15/2014 06:57 PM, Ady wrote: > > Finally, when using MEMDISK to boot floppy images, these images > should not use partial "cylinders". In other words, use exact CHS > values for floppy images, instead of building the images by means of > the desired megabytes size. Then use the selected CHS values as > parameters for MEMDISK. > If you have a proper set

syslinux-3.0.7 Cannot boot memdisk+harddisk image. 1) mkdiskimage -d image.dsk 10 64 32 (I get a 10485888 bytes file) 2) start dosemu+freedos with image.dsk loaded as d: and do sys d: then copy some files to d: 3) reboot dosemu using image.dsk as c: to verify it's bootable, and it is C:\>ver FreeCom version 0.82 pl 3 XMS_Swap [Mar 06 2004 10:49:37] C:\> 4) isolinux.cfg: label 999