similar to: Syslinux 3.70 - BSS DOS boot says: "Could not find kernel Image: linux".

Hello everyone, I have just released SYSLINUX 3.70, which is the first version which includes gPXE for support of non-TFTP network scripts, as well as a large number of other enhancments. gPXE support is still somewhat experimental - in particular it still doesn't support chaining other NBPs. Very special thanks to: - rPath, Inc, my employer, for the uncountable hours I've spent

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

I am trying to PXE boot an ISO image using ISOLINUX. I am starting small just trying to get anything working but seem to be having problems. I followed the instructions on the isolinux page (http://syslinux.zytor.com/iso.php) but still cannot get it to work. I can get the ISO image to try to load but then it stops at the booting message. Any help would be greatly appreciated. Here is

Allow the grub loader to (optionally) support using a GRUB menu file. For example chain fs grub=stage2,grub.conf will load GRUB's stage2 and pass the (absolute) path to the file "grub.conf" in the Syslinux filesystem to GRUB's stage2. The path is passed to stage2 in GRUB's device/partition syntax (eg, "(hd0,1)/foo"). Note that we don't check whether the

This patch introduces extra functionality to chain.c, mainly with reference to BPB adjustments, but not only that. It expects 3 small patches I sent earlier (they are included for easy reference, patches 1-3/4). The changes introduced are: 1) file and boot sector use separate options to control load address and jump address (if applicable). Options are as described below: *

Hello, Thanks for all the information, I think my last remaining question is why the image created with virt-install shows the full apparent size and the image from virt-sparsify does not? (The image testimage1.qcow2 created with default options). As they are both qcow2 I would expect them both to have the same behavior as far as apparent size goes. Or is there an option I am missing in

> Delete what you've done and start from the beginning. Describe > exactly how you created the guest. Use 'qemu-img info' to show the > format of the input file. Show precisely the virt-sparsify command > you are running. And use 'qemu-img info' on the output file too. Okay, here goes. Start off with an install root@testingbox:~ # virt-install --name

On Wed, Jun 22, 2016 at 05:56:09PM -0500, libvirt_users@skagitattic.com wrote: > > Delete what you've done and start from the beginning. Describe > > exactly how you created the guest. Use 'qemu-img info' to show the > > format of the input file. Show precisely the virt-sparsify command > > you are running. And use 'qemu-img info' on the output file

While playing with some less than usual configurations, I've got bitten few times by geometry settings in case of, usually, microsoft[ish] systems. First two examples, then the improvement idea. Example #1 My usb stick has zip-compatible geometry, which should work fine both in hdd and zip modes. It usually does, at least as far as syslinux and normal software is considered - excluding

I am working on dumping raster data from R into PNG files using rasterImage(). I am working with a test matrix from the rasterImage() example and using it to produce a PNG image with the following code: # From the example for rasterImage(). A 3 pixel by 5 pixel b/w checkerboard. testImage <- as.raster(0:1, nrow=3, ncol=5) testImage [,1] [,2] [,3] [,4] [,5] [1,]

I am working on dumping raster data from R into PNG files using rasterImage(). I am working with a test matrix from the rasterImage() example and using it to produce a PNG image with the following code: # From the example for rasterImage(). A 3 pixel by 5 pixel b/w checkerboard. testImage <- as.raster(0:1, nrow=3, ncol=5) testImage [,1] [,2] [,3] [,4] [,5] [1,]

Just tried the latest release and found a minor bug. Have a UFD w/ SYSLINUX, which boots a simple .BSS image no problem. Launching exactly the same image on a ISOLINUX disc fails w/ the following error msg: Invalid image type for this media That's it for this msg. Later....Jet -- Powered by Outblaze

The following patch for chain.c32 adds support to boot the Recovery Console of Windows NT/2K/XP. Normally when you want to boot the recovery console, you need to patch "cmdcons\0" into the bootsectorof the partition (8 bytes starting at 0x3 (4th byte)). We can do this patching in memory: strcpy((char *) 0x7c03, "cmdcons"); To boot the recovery console with chain.c32:

filename to GRUB Legacy GRUB Legacy reserves 89 bytes for storing the filename of the configfile from memory address 0x8217 to 0x826f. We allow overwriting the default value (/boot/grub/menu.lst) when grubcfg=<filename> is used together with grub=<loader>. Examples: chain.c32 fs grub=/boot/grub/stage2 grubcfg=/boot/grub/grub.lst chain.c32 hd1,10 grub=/boot/grub/stage2

Version 1.34.6 (on Debian Stretch) Using virt-builder I tried to create a user and inject my ssh key: virt-builder -v -x centos-7.4 --output testimage --format qcow2 --selinux-relabel --hostname testimage --firstboot-command 'useradd -m -p "" dummy' --firstboot-command 'chage -d 0 dummy' --ssh-inject dummy ... [ 16.1] Installing firstboot command: useradd -m -p

Here is a patch that makes it possible to chainload GRUB2 core.img form chain.c32. It reuses the grub= parameter (used for chainloading GRUB Legacy stage2): - both loaded at 0x8000 - start execution at offset 0x200 (0x8200 in memory) GRUB2 allows to specify another "GRUB home dir" than the standard /boot/grub GRUB2 doesn't allow to change the configfile 'grub.cfg' name

I have been having an irritating problem with my home network. My network consists of 1 PC running Mandrake 8.0 as the file server with Samba 2.0.7, three PCs running Win98SE and one PC running Win XP. I have had the network running for almost two years in various OS configurations and for the most part have had smooth operations. However, my problem comes when I try and copy, move, or save any

This adds (basic) support for GRUB stage2 image files. Loading a stage2 image will probably give you a GRUB prompt, with GRUB's "root" set at "(hd0)" (ie, entire first disk). Maybe the "root" will differ in less common setups. (One can of course select another disk and/or partition with GRUB's "root" command.) This has only been tested with version

Thanks for the answers so far but I haven't been able to come up with an solution yet :( Some new info (see bottom of email for history): 1. I upgraded to 2.0.10 on my Mandrake 8.0, no change to the transfer problem. 2. I attempted to ftp a file from the Win 98SE PC to my Samba Server, didn't work. So I can assume that it is not specifically Samba problem. 3. I have changed the NIC cards

I was encouraged [1] to use the storage encryption mechanism of libvirt [2]. However, it is not clear to me how to generate a corresponding encrypted volume. Preferably, I would like to use virt-install to arrive at such an encrypted volume, similar to e.g. virt-install --connect qemu:///system -n testImage -r 2048 --os-type=linux --disk