similar to: Boot DOS through Pxelinux

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]

I am trying to build a distribution without having to be root. The SYSLINUX installer typically needs root to do loopback mounting, but if you have MTOOLS, you can use that instead. This seems to work so far: #!/bin/sh # A minimal replacement for /usr/bin/syslinux; assumes that ldlinux.sys # and ldlinux.bss are available in the current directory. You must # specify locations of mkdosfs and

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

Yes, really. I've got hundreds of the damn things here at home, and I want to go through them and get rid of them all. But... to do that I want to read them. I have both a 5.25" and a 3.5" drive, both are plugged in, but in the BIOS, all I see is the 3.5". Fine, I figure I'll take care of those. Nope. I see /dev/fd0 once I've booted up, but neither konqueror nor

Hi all, I have just released syslinux-3.70-pre25. Unless someone has something big and scary that either I have managed to miss or was just stumbled over, I'm going to release 3.70 final some time between tomorrow and Monday. Thus, *please holler now* if there are any stop-ship problems still known... -hpa

On 01/21/2014 11:13 AM, Thomas Schmitt wrote: > > My current theory is that vendors prefer to record > a cylinder aligned end CHS address over recording > an end CHS address which exploits the whole capacity. > This is used as an (inofficial ?) protocol to publish > the CHS factors H' and S'. > Indeed it is -- at least some BIOSes "deduce" the H/S to use

Hi, I saw a post you made on a forum quite some time ago about booting linux off a USB drive with compatible bios via ISOlinux. I'm currently trying to do the same thing and keep running into problems with my initrd. This is probably caused by the fact that I don't really know what I'm doing! I was wondering if you found any useful info on the net you could point me in the

If there a way to may samba "handle" files like ftp does during ascii transfers. Changing the ^m to unix end of line markers

--- utils/mkdiskimage.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/utils/mkdiskimage.in b/utils/mkdiskimage.in index 533193a..a95a077 100644 --- a/utils/mkdiskimage.in +++ b/utils/mkdiskimage.in @@ -218,7 +218,7 @@ $totalsize = $c*$h*$s; $tracks = $c*$h; # If -s is given, try to simply use truncate... -unless ($opt{'s'} && truncate(OUTPUT,

utils/mkdiskimage.in: With option -s: Avoid zeroizing the partition even if truncate() failed. --- utils/mkdiskimage_patched_01.in 2014-01-30 20:43:02.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:45:09.000000000 +0100 @@ -217,8 +217,11 @@ print OUTPUT "\x55\xaa"; $totalsize = $c*$h*$s; $tracks = $c*$h; -# If -s is given, try to simply use truncate... -unless

Hello All: I've recently had to provision some RHEL and CentOS VMWare instances. There was no network connectivity so I had to use a kickstart floppy and DVD iso rather than installing from our repository. To create the floppy I used the following: As root: dd if=/dev/zero of=floppy.flp bs=1k count=360 mkfs.vfat floppy.flp mount -o loop floppy.flp /mnt/floppy cp base_kickstart.ks

Hi, I am trying to create an image that is larger than 1.44MB to be used with PXE boot (Ghost 8 requires 2 floppys). My current attempts result in the boot hanging at : Loading boot sector... booting... Starting... My config just says the following: default memdisk append initrd=smalldos.img I created the image following http://syslinux.zytor.com/archives/2005-August/005573.html (I am unsure

This isn't strictly speaking a SYSLINUX release, it's a change to MEMDISK and mkdiskimage to allow the creation of hard disk images with DOSEMU headers. This should make it easier to create bootable DOS hard disk images under DOSEMU. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

I have just received some audit info on the SYSLINUX 2.01 installer running setuid. There seems to be some issues, and although I can fix them easily enough I'm somewhat questioning the whole approach. The other alternative would be to make the syslinux installer a wrapper around mtools, and use mtools for the filesystem access. Since this would be done entirely in userspace, as a normal

Using memlinux I have been able to PXE boot an image I created from one of our DOS boot floppies. It works quite well. I am unable to figure out how to build a larger disk image however. It appears you can use a 2880k floppy without having to pass special options. My attempts so far have failed. Has anyone done this before? I would like to convert the working disk image I have (1.4 meg) to a

@Carl, I'll repeat what I said in my prior email: you don't have to keep looking, we already achieved what you want (considering that you are willing to "disregard" the screen problems and similar issues, at least for now, according to your own emails). In short: 1_ Re-read my email from 2018Dec05: www.syslinux.org/archives/2018-December/026247.html where I posted

Can't hold it off any longer... here it is :) Changes in 2.00: * ALL: Add support for "COM32" (32-bit COMBOOT) images. * ALL: Add an API for COMBOOT/COM32 images. See comboot.doc for details. There is a C development environment for COM32 being created; it should be ready at some point in the future. * Fix mbr.asm so that it

Here's an interesting problem, and the first partial failure I've seen when booting USB keys. I've installed a bootable Knoppix "CD" image to my USB key, and posted a writeup of my installation method here: http://knoppix.net/forum/viewtopic.php?t=25402 Up until now, I've always had one of: 100% success (it fully boots) 100% failure (BIOS fails to recognize the USB

I have put a compile hack in for older distros and pushed it out as syslinux-3.62-pre16; for those who have reported compilation problem on older distros I would greatly appreciate if you could confirm if it works now (it worked for me on a CentOS 3.9 VM.) -hpa

Hello list, any try the new memtest86 v3.2 with isolinux 3.11 cd and pxeboot? How is the proper way to chainload memtest86 I was tried: label memtest kernel memtest.bin but, nothing happens just a weird hang (my older versions of memtest hangs too). Anyway chainloading in a floppy image with memdisk on CD or pxeboot was fine but if I use memory to emulate a floppy I was not using this memory