similar to: Fetching TFTP server from dos/memlinux via pxelinux?

Good day, I have the problem to pass the ?loaded? undi driver to the next bootloader. In current pxelinux ?lernel memdisk keeppxe harddisk raw initrd::parh_to_img? always unloads undi before memdisk (or other kernel) takes control. After many tries I found that the keeppxe feature is broken starting from version 6.03 pre 9. I tried to find the reason by comparing sources 6.03 pre 8 / 6.03

First off I love syslinux and it has worked flawless for us on the unix side of the realm. We're trying to use our ghost images within a dos netboot using syslinux. Unfortunatly we can only pass DHCP ip's to hosts that exhibit a vendor code 'like windows/pxe/and other os's do". Unfortunatly DOS does not, so we cannot request a second IP after the pxe process to map samba

Summary ======= I have a recommendation for a minor documentation change regarding 'keeppxe'. I lost some time on this and think that a clarification could save other people time in the future. pxelinux.doc should be tweaked to explicitly say that the "keeppxe" option should be given on the kernel command line through the APPEND statemen Detail ====== pxelinux.doc line 356

Hi, I'm trying to get the above working, without success so far: UNDIS.DOS refuses to load with an invalid NDIS stack message (from memory). keeppxe has some effect: it reduces the available conventional memory by 140 kbytes or so... still, the packet driver doesn't seem to find the interface. Does anybody have a working setup I could look at? -- Thanks, Feri.

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

Hi, I want to use PXELINUX to load a DOS disk image which I currently use for Win2K/XP unattended installs. I want to move away from reliance on specific NDIS2 drivers and use the 3Com UNDIS3C driver instead. I have used this successfully to start the MSClient, but the problem is that the UNDI and PXE layer take about 90K of base memory, which means that WINNT.EXE has insufficent memory to run

I have an image of a dos floppy that loads the undi driver from 3com and mounts an smb share. This works great with pxelinux(from syslinux) and memdisk I need to make it work with pxegrub so we can use menus. (or figure out a menu system for pxelinux) With pxegrub I use memdisk as the kernel and load the dos image as a ramdisk. The undi driver loads and doesn't complain but, the network is

I have got pxelinux booting a DOS ramdisk via the memdisk program from the command line. However I am having a problem getting it to use the configuration file. pxelinux find the configuration directory, pxelinux.cfg and then finds the file, C0A801, and reads the file, but no matter what I put on my "kernel" line, it looks for a kernel named "linux". When I create a sofft

I am using memdisk to remotely flash the BIOS and other firmware. It works well for most flash programs. After the flash I need to initialize the NIC to send a signal to my management server that the flash is complete. I am curious as to how others have solved this problem. Thanks.

Hi I am using PXELinux to boot BartPE and some other application and it works fine. There are some other Boot application which I am using 3COM MBAUTIL PXE.mnu and floppy images. I have problem chaining from pxelinux.0 to 3com pxe.0 (pxe.mnu). Consider: BIOS->(DHCP-TFTP)->pxelinux.0 works fine. BIOS->(DHCP-TFTP)->3COM pxe.mnu works fine, the menu appears and I can choose a floppy

Hello, I'm trying to create and boot a Win98SE-DOS OS through Hard Disk emulation. My src files are from a Win98SE 1440K floppy image file, with a x86 boot sector (dl'd from the net - I have no floppy drive and a slow net link 3.2KB). I don't know what to put into the partition boot record of my image and how to load dos.bss properly (the docs explain for floppy images not for HD

I found the 3Com one, but I'm looking for the intel one. The PXE PDK doesn't have it anymore, and the intel site points me to the proboot.exe archive, which has no *.dos files in it. Does anyone know of other generic drivers for dos that work with memdisk's keeppxe option?

I'm trying to use this universal DOS TCP/IP boot disk available here: http://members.iinet.net.au/~bdriver/bootdisk/ It requires an MS-DOS formatted disk created by Windows XP. It works great as a floppy but doesn't boot at all with memdisk. The problem can be simplified down to just the XP boot disk. If you make an MS-DOS startup disk with XP on a floppy, dd the floppy to an image

Hello, We use undi_drv.exe that is provided with Symantec Ghost Enterprise. This driver loads a UNDI PXE stack into memory. It, along with a UNDI packet driver are bundled into a 1.44MB disk image that we use for netbooting computer lab machines into the ghost client. This is done with pxelinux. This driver has been working fine for a couple years now. Recently, I upgraded the pxelinux.0 to

Hi I use this setup with PXELINUX. label Ghost1 menu label Ghost v11 (uni net 192.168.150.10) kernel memdisk append keeppxe initrd=img/gh1.zip floppy vga=1 The sw keeppxe I use to prevent destroy the pxe UNDI net driver. The problem is similar when using ISOLINUX with the same UNDI net driver, the driver fail to load!!! The same will happened if I don't use the sw

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

I am using the following simple menu and have noticed that items at the bottom are dropping off. I seem to be limited to 12 items. Is there a limit to how many items can be on the simple menu? default pxelinux.cfg/menu.c32 prompt 0 MENU TITLE UWSP PXE Boot Menu # TIMEOUT 200 LABEL bartpe MENU LABEL Build 12 KERNEL /STARTROM.0 APPEND keeppxe LABEL 11dnet MENU LABEL Build 11DNET beta

I'm using PxeLinux to bot DOS images for an automated test application. After Running the DOS application program, I want to use the UNDI stack to send a completion status message to the server. I boot the DOS image with keeppxe, so that the UNDI stack will continue to be in memory. I am not clear as to what state the stack is left in after PxeLinux has loaded and transferred control to the

Hello all, I ran across a couple bugs in memdisk concerning hd images the other day. With the attached patch I've been able to successfully boot a 32MB gzipped hd image. (I'll put the image up for a short while at ftp://ftp.io.com/pub/usr/duanev/fdoshd.img.gz) The pxelinux.cfg entry I'm using is: label fdos kernel memdisk append keeppxe initrd=fdoshd.img.gz

Hello, I am a *nix newbie I am trying to boot a DOS boot disk using PXE (to Ghost on windows images). We have an existing PXE server which successfully serves out PXElinux and Fedora builds based on that but my floppy disk image with memdisk isn't working I have tried a few different floppy images which people have posted as ones that work for them but I doubt the disk is the problem