similar to: Problem with Symantec's UNDI driver and 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

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

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

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

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

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

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

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

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

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

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

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

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.