similar to: PXELinux and Mess-DOS

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?

I have an application/program which shows 'bios EDD error' when using Isolinux (with either loading an image directly through MEMDISK, or booting to A:), and not when using a bootdisk directly or booting a bootdisk directly which has SYSLINUX on it. configuration: bootable cdrom with Isolinux 2.11/2.12pre9 as bootloader. 1.44MB bootdisk with MSDOS.SYS/IO.SYS and the UDMA2 dos driver,

Memdisk 2.08 cannot boot an XP boot floppy image (XP appears to use WinME boot files for its bootable floppy). For example: http://members.iinet.net.au/~bdriver/bootdisk/download.htm This disk will not boot with Memdisk (Memdisk starts to load the image and then hangs). I'm using Bart's tools to build a boot CD: http://www.nu2.nu/corpmodboot/ Which uses Isolinux and Memdisk.

Memdisk 2.08 does not appear to be able to boot an XP DOS image (it starts to boot and then hangs). XP DOS appears to be borrowed from WinME (v4.90.3000). I was trying to make a multiple boot CD with Bart's method: http://www.nu2.nu/bootcd/#multimemdisk but substituting Brads TCP boot disk instead of Barts: http://members.iinet.net.au/~bdriver/bootdisk/index.htm Brad uses XPs DOS as it

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.

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

Hi, Currently I am building a new PXE boot environment and during that I noticed something odd while attempting to boot using one of those universal netbootdisks based on the '3Com Universal NDIS driver v1.00' (aka undis3c) driver. Using pxelinux.0 this works like a charm, but when I switch to gpxelinux.0 the 3Com driver bails out on me... all other configuration is the same. Have

I am using the following simple menu and have noticed that items at the bottom are dropping off. I seem to be limited to 12 items. Is there a limit to how many items can be on the simple menu? default pxelinux.cfg/menu.c32 prompt 0 MENU TITLE UWSP PXE Boot Menu # TIMEOUT 200 LABEL bartpe MENU LABEL Build 12 KERNEL /STARTROM.0 APPEND keeppxe LABEL 11dnet MENU LABEL Build 11DNET beta

Dear Sir, I am trying to create a multiboot cd that will supposr the following: 1. Linux RedHat 7.2 2. Windows 2000 Professional 3. Windows 2000 Server 4. Windows 2000 Advanced Server I get it right, but to have the Linux image on the same cd and to boot from it is a problem. Here's what I did: First I created a bootable cd with the windows images and used the El-Torito standard based

Running Redhat 2.4.21 with Samba 3.0.9. My share is readable ok but while write access will work when i've booted from a dos environment (Bart's boot Disk http://www.nu2.nu/bootdisk/ which is a marvelous free product that i'm happy to plug) When i authenticate from a windows XP or 2000 desktop i can read but have no write access with the same account. The folder permissions all

Have a look at the 911cd forums. I wrote the initial thread on RAM booting WinPE. To answer to question... memdisk won't work with Windows. Windows uses 32bit access (direct HW access) and memdisk relies on the BIOS. Any programs that don't use the BIOS disk interfaces will not work. The other problem is the allocation of memory. Windows doesn't respect the memdisk allocation.

Hey all, I'am able to use pxelinux to successfully boot a particular kernel and image on various IBM PC's ex. 6287-41U and 6591-34U. However, using the same setup (ie. dhcp, tftp, pxelinux.0, pxelinux.cfg, networkcard, bootrom, ram memory) on an IBM 6282-73U my kernel and image decompress fine but I'am getting a... Kernel Panic: VFS: Unable to mount root fs on 01:01 I realize

Hello all, I plan to make an (emergency) multi OS bootable CD which contain: - Win98 boot floppy (create from Win 98 control panel, add remove program) - WinME boot floppy (create from Win 98 control panel, add remove program) - Linux boot disk - Win NT boot disk - Win 2000 recovery console - Win XP recovery console - Winternal Administrative Pak (ERD Commander etc) I am new to Linux and feel

Hello ! Maybe passing argument root=/dev/ram0 or root=/dev/rd/0 would help ? I use isolinux and it works in the isolinux.cfg sylvain > Message: 3 > Date: Fri, 13 Sep 2002 14:11:38 -0300 (ADT) > From: Geddes <jgeddes at unb.ca> > To: syslinux at zytor.com > Subject: [syslinux] Unable to mount root fs > > > Hey all, > > I'am able to use pxelinux to

Hello! I'm having trouble to access a Samba share trough ms-dos. I'm using NU2 network boot disk, wich loads ndis drivers ms-dos prompt. So that after that I can do a net use to a share and load an disk image with Ghost. The problem is that i passed from a windows to unix - samba share and i'm not capable of connecting to it. Mapping the share trough Windows XP is no problem. Can

forgive me.. i have no idea what im asking or if its possible... i have 2 partitions as follows and am using the std windows xp bootloader to boot xp - ntfs (windows xp) - fat16 stupid question is... can i use syslinux, isolinux, memdisk or some combo there of to place a bootable cdrom iso image on the fat16 partition and then have a boot menu with something to the effect of : 1) winxp as

OOPS. Hit the wrong key. Hope you didn't get the previous message! I've been using Barts Boot CD method at: http://www.nu2.nu/bootcd/#multimemdisk It works great...trouble is, it creates a ramdisk of it's own. I end up with the following drive assignments when I boot DOS/Winxx: a: - memdisk image of boot floppy c: - hda1 d: - hda2 (etc) q: - ramdisk created by barts

Hi All, I had some issues with keeppxe and also found a solution after much trial and error. I would have not mind trying out ?experimental? binaries but it was not clear where to find them. I use a stock a stock install of slackware64 current for my tftp server. I use pfsense to point to the tftp server under the dhcp boot options. I upgraded from Syslinux 6.03 to 6.04 pre1 and was still

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

Has anyone been able to boot a bartpe image successfully using pxelinux or does anyone know if this is impossible? For those who don't know, bartpe is a legitimate way to make a trimmed down installation of Windows XP or Server 2003 using your installation media. For more information on bartpe see: http://www.nu2.nu/pebuilder Basically the pebuilder gathers the minimum files needed to