similar to: Problem or error in syslinux used with UNDI net driver...

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

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

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

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

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

Hello I wonder, if you know any more about the possibilities of having a standard Network driver for most cards. Is there any such thing for linux? Where do I get it? Is there possibly something for DOS? A UNDI Packetdriver would be cool, because then I could use DosSCP on every Network card I would ever be using with MemDisk (which in turn is very cool.) bye Christian (thinking about writing

Hi all, I'm still trying to figure out a good way of booting a DOS disk image via PXE and accessing files over a network share. Having some success with the Microsoft network DOS client, it seems that many programs have issues with its IPX support - so, now I'm trying to use Novell's IPX driver instead. Unfortunately it seems I need an ODI driver to do this, and there are no

Hello, Has anyone thought about how one could use the "keeppxe" option with a vmlinuz/initrd? It would allow one to boot this combination, and if possible the linux kernel/initrd (assuming we have busybox in there) would not have to run udhcp and instead leverage what pxe stack information is loaded. The problem is I don't know of any PXE/UNDI linux utilities to look at the pxe

> 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

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

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?

Hi, I work in Dell Support and I have a customer with a PowerEdge 1650 Server with Intel? PRO/1000 XT (82544GC Gigabit Ethernet Controllers). The nic is integrated on the motherboard. The customer is using a Linux system with DHCP+tftp to PXE boot and load an MS-Dos 6.22 image, with an UNDI driver, over to the PowerEdge 1650 and then map a Samba share to install Windows 2000. The customer get

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

HPA et al.: Are there any plans for pxelinux to support UNDI-3.1, as defined in UEFI-2.1, appendix E? I ask because I was dismayed to see EFI systems successfully download pxelinux, only to have pxelinux exit. This was a major downer after implementing an debugging an entire EFI "UNDI" driver. Scanning pxelinux.asm, I conclude that pxelinux supports only UNDI-2.1 at the moment.

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:

First let me say I'm really excited about the possibility of dynamic menu creation over http using php. When this is stable it will make maintinging some of our pxelinux infrastructure much easier. Id like to thank all involved; I'm really looking forward to the gpxe intigration. After hpa's announment for 3.70pre7 I begain testing. I dropped the new gpxelinux.0 and new c32 modules

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.

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,