similar to: pxegrub + memdisk + dos + undi

sorry - i must have overlooked the part where you mentioned that.. my fault. What software are you looking at ? Altiris maybe ? I am, ofcourse interested in the option you are looking for. Please keep this list updated. Best regards, Rijk -----Original Message----- From: Aaron McSorley [mailto:aaron.mcsorley at amd.com] Sent: Thursday, January 15, 2004 4:56 PM To: rbitter at cntnl.jnj.com Cc:

Hi Aaron, i know it is not an interactive menu - but in my 'config' file i call for a textfile to be displayed : DISPLAY menu.txt that contains all my labels. See the first part of my 'config' : label 0 LOCALBOOT 0 label 1 KERNEL memdisk/memdisk APPEND initrd=images/w2k/unatt.ima label 2 KERNEL memdisk/memdisk APPEND

In our testing, pxelinux and Dos UNDI is much more stable than pxegrub with ten different nic drivers compiled in. The only thing holding us back on using pxelinux for all of our tftp images is the lack of a menu system. We are very close to buying a proprietary software but, I would much rather use an open source type solution. It should be possible to write some comboot code

....."We are looking at Argon, they seem to have the best menu system. The sad thing is, they dont support alot of our image types, we will use their menu system to select pxelinux which will do all the real work. So, they get the money just because they have a menu system, and pxelinux does most of the work. Another negative is the configuration is all done through a bad windows GUI."

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

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

On Tue, 2002-04-30 at 15:12, Yoshinori K. Okuji wrote: > > Jean-Jacques pointed out a bug in GRUB and I've fixed it right now. So > the current CVS version should work with memdisk. Could you try? > > Thanks, > Okuji hi, okuji. that works great! thanks very much for your help. it might be worth mentioning memdisk in the documentation because i'm sure others would find

Pedro, Thanks for the feedback. HPA and all, Since we have confirmation that this patch fixes keeppxe (for the memdisk use case) for at least one other person, could we get it into the next syslinux release? http://www.syslinux.org/archives/2016-June/025216.html -- Adam On Sat, Dec 24, 2016 at 02:09:14PM +0100, Pedro Koschi wrote: > Hello Adam , thanx . I was successful to compile

Hello i'm working on a netboot environement with a highly configurable menu system. for some parts i like to use pxelinux for others pxegrub. I can load both seperatly. Now what i want is to have the possibility to switch from une to another. I tried: to load pxelinux from pxegrub: menu.lst: title pxelinux root (nd) kernel (nd)/pxelinux.0 title pxelinux2 root (nd) kernel

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

The git version of syslinux won't solve your problem. It doesn't have the keeppxe patch at this time. I can't help you to get pxelinux to load ldlinux.c32. I didn't write syslinux. I've Cc'd the mailing list. Maybe someone there can help you. -- Adam On Sun, Nov 27, 2016 at 07:38:53PM +0100, Pedro Koschi wrote: > Hello Adam, > I was able to compile syslinux in

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

Greetings: [ First, apologies if this has been discussed before. I looked through about the last year's worth of archives, but couldn't find a "Search feature", so I used the visual grep method, which is not foolproof. I also tried to download the full text of the archives to use the real grep, but I got an error loading it... ] I'm working on setting up the Xen virtual

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?

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'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.

> Marcel Ritter wrote: > > > > The good thing about it: The PXE code removal seems to work now ... > > > > But I'm not quite sure about the syntax - is the following right? > > > > label undi > > kernel memdisk keeppxe > > append initrd=UNDITest/dosundi.1 > > > > The documentation only says: > > > > ... option

Hello, I'm still trying to setup RIS (Remote Installation Service -w2k) with PXE Linux, but before that I must say that the mail list archive is a _good_ idea. Back to RIS. When I start from pxelinux memdisk initrd=risbootdisk.img I get an error: No UNDI Driver found. The risbootdisk.img is a bootdisk from Microsoft, which starts a RIS installation. When I boot from floppy it works fine,

I have already a running automated Deployment system using pxelinux and tftd and a 1,44 floppy image (memdisk) with ms-dos and 3-com undi drivers. The whole thing is working good, and i am not unhappy about it. But, the dos image solution has a few disadvanatages, because i cannot find a mtftp client for ms-dos to deploy a lot of system at the same time. Under linux such client exists, but i

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