similar to: Booting firmware harddisk image with memdisk fails

Hi All, I am still having troubling with PXE. Thanks for replying Shao.I did follow ur suggestions and my results have improved a bit.From Ethereal and TCPdump, I can see that the client sucessfully dowloads the file pxelinux.0 from the server but stops at this point. here is the output of tcpdump tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 11:05:41.966864 IP

The RHEL 5 release notes for their desktop version claim "Improved ACPI support with features such as suspend to disk" but this isn't working with CentOS 5. I've installed all the packages and updates for CentOS 5 i386 on a ThinkPad T43 but when selecting suspend, Gnome pops up a URL to a site that didn't seem to give a solution. Gnome makes an entry in /var/log/messages

Hallo, I'm just trying to boot a Clonezilla *.iso (live-20100521-lucid) via PXE; Label clonezilla kernel memdisk append iso raw initrd iso/clonezilla.iso The first step is ok - I see the boot menu of the *.iso. When I choose "Clonezilla live" the system fails with Isolinux: Disk error 02, AX = 4224, drive E0 when I choose "freedos" it fails with

I have a USB flash drive that I'd like to image, and then load that image via pxelinux and memdisk. The flash drive was formatted under Windows 98 SE as FAT, and boots just fine on its own. The PXE boot process gets as far as loading the image via memdisk, but then when the boot process switches over to the RAM disk, it fails: [...PXE diagnostic information...] Loading boot

Cross-posting to the Syslinux mailing-list. Joakim Schicht wrote: > But part of the question is also about "memdisk raw" vs "memdisk iso". "raw" and "iso" are not mutually exclusive. I think that perhaps you meant "HDD versus El Torito emulation." One can do: LABEL ramwin KERNEL memdisk APPEND raw iso INITRD ramwin.iso > Lets say

Hi When purchasing a new UPS, one of the major functionalities I would assess, is the support is has by NUT. We have the http://www.networkupstools.org/stable-hcl.html page, where we can see if a UPS is supported, and what the level is. But I would really like to have more knowledge. I would like to know how the output from the "upsc" looks, so I know what values I will get from the

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

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

Good day to all, Gert Hulselmans requested a feature for MDISKCHK.COM that would function roughly like GETARGS.COM[1] by Murali Krishnan Ganapathy: DOS SET command output for MEMDISK kernel arguments passed by previous boot-loaders. He also needed to support the case for MEMDISK-in-a-MEMDISK type situations, where all MEMDISK kernel arguments could be gathered together and output as a list

This is a minor tweak on 3.11-pre2. If nothing new comes up, I will release this as 3.11 probably early next week. -hpa

It appears that the 3.74 completely broke the "keeppxe" directive -- not due to the command-line parser, but due to mishandling of the flag later. I consider this to be severe enough to do a short-cycle 3.75. As a result, I would like help with: a) are there any other bugs that snuck through? b) once I have a 3.75-pre1, I would really appreciate help testing it. The goal is to have

Good day Gert Hulselmans, You had reported to me at one point that MEMDISK -> .ISO -> ISOLINUX had failed under certain circumstances. I just noticed with a MEMDISK 3.86 that specifying the "iso" option on the command-line actually resulted in the .ISO getting BIOS drive number 0xFF. I had to specify "iso harddisk=224 pause" to confirm that it resulted in 0xE0 (hd96).

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

Is it possible to configure syslinux.cfg on a floppy to start Win98 on a secondary hard drive? If so, how is this done? Currently I have Linux and Win98 on the primary hard drive, and when I attempt to use the floppy to start Win98 on the second hard drive, I simply start Win98 on the first drive. I have tried many different approaches, all to no avail, and I would really appreciate some

Hi, I was wondering what's the best standard file extension for zipped DOS disk images and ramdisks. I've been using the following standard: .zi kernels, memtest86, memdisk .igz .img.gz zipped floppy images and ramdisks I'd rather have a different extension for ramdisks, maybe .zim zipped floppy images .zrd zipped ramdisks Any ideas ? It would also be nice if syslinux

I've recently returned to working on FreeDOS again after quite some time, and read about an unmerged MEMDISK branch that allows to boot DOS-based ISOs. This seemed quite usefull to me as it allows for faster modifications to my code/scripts/disklayout. The general idea was to install Syslinux 3.83 to harddisk, then add the modified Memdisk from that boot-land forum, as well as my ISO. In

The docs in http://mirror.centos.org/centos/4/docs/ do not reflect yum of today ie the yum plugins. Where can updated yum docs be found? By browsing lists such as fedora-devel, centos one can see how the plugins have "stumbled in" but newbies/anyone wanting to pickup on the new features has nothing to read. Note there are yumex docs at the above location but my query relates to yum $

Hi, I'm trying to create a hd image to use with memdisk: dd if=/dev/zero of=doshd.img bs=1024 count=16384 and, via qemu, I installed freedos: qemu -cdrom fdfullcd.iso -hda doshd.img -boot d Everything gone ok and qemu boots freedos normally. But, when I try to use the same image on memdisk the following message appears: Invalid Operation System! I used the same process on USB key, with

Hello Peter. Thank you for writing memdisk and isolinux. I've created a bootdisk with it, and it works gread with floppy images and noemulation (WinXP). I've created also a harddisk image with "nero Burning-Software". It works with the createted CD. But when I use the created harddisk image with memdisk. I'l receive error Message as follows. <<screen.jpg>>

Hi all, I am at the end of my wits, after a day and a half of mucking around with this :) My intention was to take a multi-boot DVD - of the style you get with an MSDN subscription - and burn an individual installer to disc. How to do this? My theory was to take the files for the installation CD, add isolinux, add a bootsector, and away I go. Unfortunately it doesn't seem this easy. So I