similar to: KEEPPXE/DOS

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

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

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

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.

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

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

but it works well with pxelinux.0 in 3.75

Hello, I saw your post on booting a Norton Ghost image via pxe, syslinux, memdisk. I would like to how if you were able to do it? And also how you did it? I tried converting to .img to no use Thank?s Marcus Nascimento Ger?nte de TI Mikropar Ind. e Com. Ltda (11) 4662-9100

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 Peter. I have some question: on my nt4 dhcp server i have added the option (067 Bootfile Name - ......\boot.ovl) the boot.ovl is needed for automatic installation and configuration with on command ccm (www.ontechnology.de) the clients boot with pxe this boot.ovl. now my question: I want to to boot in a menue with two options. first and default boot, is to boot the boot.ovl and second is

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

Hi! I've spent the last days trying to get PXE working (with all the nice stuff that's in the specification - doesn't work :-( ) So I tried the new 1.75 with the Intel DOSUndi Bootdisk (which should verify that everything works correctly) but it does no longer work with syslinux-1.75! 1.74 is fine - so I guess something is broken here ... Please have a look at it - and let me know