similar to: PXE Menu Not Working

Hi, I'm trying to convert my PXE enviroment from the 3com to PXELinux but I've got a problem when loading a image created by 3com's utility. At first when I tried to launch the bootimages with memdisk but I had no luck Then I added a MBR to the images and now Norton Ghost can launch but it first gives me a Windows 98 bootscreen and my customized Universal Network Bootdisk can't

My ?default? was just a sample to prevent further tl;dr :) Right, by 2014 I meant 6.03. I didn?t notice in the docs this was a known issue. If keeppxe is a bug with 6.03, that?s likely my issue. Do I drop back to 6.02 or X? Which version? Thanks, David Sent from my iPhone > On Feb 1, 2018, at 6:53 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > >> Hardware

Hardware with issue is a Lenovo T410 (circa 2007?): SysLinux PXE boot (pxelinux.0) version 2009 - PXE boot works, select Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is working for Ghostcast/peer to peer. SysLinux PXE boot (pxelinux.0) version 2014 - PXE boot works, select Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is NOT working for Ghostcast/peer to

Thanks Ady. I have to stick with stable vs. experimental but I appreciate the Debian suggestion. I don't mean to troll anyone, but... how is 6.03 considered stable if it does not correctly support keeppxe? I have to go all the way back to 4.xx for this to be supported? Wow. I still couldn't find it in the docs online where it states keeppxe doesn't work. I have some "detail

> Hardware with issue is a Lenovo T410 (circa 2007?): > > SysLinux PXE boot (pxelinux.0) version 2009 - PXE boot works, select > Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is > working for Ghostcast/peer to peer. > > SysLinux PXE boot (pxelinux.0) version 2014 - PXE boot works, select > Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking

> Right, by 2014 I meant 6.03. I didn?t notice in the docs this was a known issue. If keeppxe is a bug with 6.03, that?s likely my issue. Do I drop back to 6.02 or X? Which version? I would suggest trying Debian's "experimental" binaries (which include potentially-relevant patches for keeppxe), including all its "bios" lib*.c32 files (beware not to mix with the efi

apologies, I take that back... I was in the TESTING path under downloads. Looks like 4.07 was latest stable 4.xx release? thanks. On Fri, Feb 2, 2018 at 10:26 AM, David McDowell <turnpike420 at gmail.com> wrote: > Thanks Ady. I have to stick with stable vs. experimental but I > appreciate the Debian suggestion. > > I don't mean to troll anyone, but... how is 6.03

Hello list, I'm trying to reuse a fairly old PC based embedded system. It has no video output at all, no VGA, nothing older, and no keyboard / mouse connectors. The console is on a standard RS232 interface, including BIOS output and the minimal BIOS loader. The BIOS emulates / redirects text output to and keyboard input from the console RS232 interface, but unfortunately, this emulation

Hello Xen users, I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this mission failed.. Hope you can help me by finding the reason for my problem. I downloaded the xen sources from http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz and compiled them by running "make" and "./install.sh". This seemed to work. After setting up grub like

Hi Peter, I'm using isolinux and memdisk to create a multiboot rescue cd for personal use as described on Bart's page (www.nu2.nu). One boot item is to boot DOS 7.1 from Win98SE with a lot of other staff for emergencies. This DOS bootimage puts all necessary stuff into it's own ramdisk (XMSDSK). Some progs on the ramdisk needs access to floppy drive A: and unfortunately I've no

Hi: recently i am doing fast boot from linux kernel to Xen hypervisor,and vice-versa. it means when linux is running on the real machine, i just want to switch to Xen hypervisor without going through bootloader. both linux and dom0 of Xen using the same filesystem. we boot Xen and the Linux with the following command in grub: title Ubuntu 8.04.2, kernel 2.6.29 root (hd0,7)

Hello, I''ve got a problem to get a serial output on grub, xen, linux-xen0 and getty. The serial works fine with grub, xen and linux-xen0, but I''m unable to start a console, where I''m able to login. I dont''t get any output. If I change only the getty from ttyS0 to ttyS1 than I''m able to login.. At the attachment you can see what I see through a serial,

let''s try this with a shorter subject, which was originally this, which probably tripped the list-admin-approval triggers.... Xen 3.2 Debian 2.6.18 on Dual Xeon with Remote Serial access - grub.conf config advice needed the subject says it all - anyone who knows the answer can stop reading and hit "send" with a few lines of grub.conf - however, for those people who are bored,

Hi, I am trying to boot syslinux with an SD-Card on COMe-mBTi10 board, it works perfect with syslinux 4-06(as BIOS supports booting from SD-CARD), but hangs with syslinux-6.03 during 'Loading vmlinuz ... '. I tried various ways in which I could debug but no hints, just one time I got the error below the loading screen. 'Loading vmlinuz0 ... CHS: Error 8001 reading sector 34(0/3/3)

Hi. We've been using PXELINUX for years, to kick off OS installations (floppy images) and booting assorted tools. The addition of ISO support in memdisk opened up some new alternatives that we also use, e.g. booting WinPE ISO images over PXE. Today I downloaded a BIOS for a HP EliteBook 8440p and discovered that the BIOS file is 3 MB. I could probably squeeze it onto a 2.88 MB floppy image

Erwan, I'm using syslinux v3.85 Gene, the kernel was built using buildroot (and I checked that Xen support was enabled). Didn't try without the menu, will see that now. Also, I saw a short note on syslinux mboot wiki page: "A really good use case for this (using mboot.c32) is booting Xen <http://xensource.com>, or any other hypervisor-based virtualization pieces that also

Hi, I've got the same Problem. Not with WinMe but Win 98SE. But what I figured out is, that it doesn't realy apply to the Command.com rather to the Way the BootImage was created. It took me a long time to get my Hands on a Image with 2.8MB that's working. Since creating one my self, was allways failling. I downloaded the Bootutils 4.3 from 3com and used the Imageedit tools. With these

Hello Peter, is it possible to boot a CD-Image of a bootable CD (no disk emu) via pxe. I've build up the infrastructure to boot normal floppy images via PXE (under W2K and/or Netware). I have a ISO image of the bootable CD (1 tack TAO eltorinto with an a single boot sect -> bootimage is 2kB, ISO image about 600 MB) I suspect that a combination of MEMDISK and PXELINUX with activated UNDI

Hi SysLinux, i'm using pxelinux.0 and memdisk to successfully boot dos on my PXE capable workstation. But aber the DOS boot I need to get access to Drive A: again. My DOS bootimage is putting all necessary stuff into it's own RAMdisk. How can I disable memdisk, so that it releases drive A: (does not necessarily free the allocated memory for it's RAMdisk ..) with kind regards / mit

Does SYSLINUX have any idea which DOS driveletter would be assigned to the disk it is booting from? At www.veder.com someone is trying to build a USB flash drive. However, FreeDOS does not seem to boot correctly from it (bootsector trouble maybe, or kernel itself is confusing drives), thus we're thinking of using Syslinux + Memdisk + bootimage, but somehow we want to be able to also access the