similar to: UNDI - Rom-O-Matic -- A bit off topic..

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

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

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

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

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:

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

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

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

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,

The following changes since commit 6438fbcb6cb7e0cd40e4bb3681ada047fe77ffdd: Gene Cumm (1): Allow for UNDIIF_ID_DEBUG in 1 mk line are available in the git repository at: git://github.com/geneC/syslinux.git elflink-undi-thread-for-mfleming Gene Cumm (3): core/lwip/undi: Improve UNDIIF_ID_DEBUG messages core: mbox/semaphore NULL checks core: make

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

I have spent a couple of days and quite some time during the nights googling and experimenting in pursuing subject objective and I feel like failing, if I cannot get competent help: My objective: boot a FreeBSD-package over the network by Systems lacking HW-Support for PXE My Testconfiguration: Server IBM-PC300 Client Siemes Fujitsu ErgoPro with freeBSD6.0 installed Network card in

Hi Hpa and all I am confused about some function of pxelinux and gpxelinux/gpxe. 1, after I read the document (http://edgyu.excess.org/ols/2008/H%20Peter%20Anvin%20-%20x86%20network%20bo oting%3a%20integrating%20gPXE%20and%20PXELINUX.pdf), I knew there are two major module in standard gPXE, PXE BC and UNDI. And I can understand why I need to produce different boot file for different NIC from

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

Sorry for the cross-post, but this could be either lists problem. I have 2 boxes running 7-STABLE as of 20081130, both i386 SMP. One is running ISC DHCPD 3.0.x from recent ports, and the other dhclient from make world. The server is refusing to answer the DISCOVER request, as it thinks the IP checksum is wrong, which tcpdump also confirms. Other DHCP clients are working fine on this network,

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

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

O.K Here we go: 8-) Pxelinux 4.10 4.10-pre22 Copyright ..... !PXE entry point found (we hope) at 9073:00F6 via plan A UNDI code segment at 9073 len 216A UNDI data segment at 9059 len 01A0 UNDI: baseio ec00 int 11 MTU 1500 type 1 "DIX+802.3" flags 0x81b Getting cached Packet 01 02 03 MY IP addr seems to be 172.31.126.10 UNDI : IRQ11(0x73):0a63:4f9b -> 0000:8de2 Mac: Addr: 80 ee 73