search for: emboot

...and get "dos.img.gz". then i rename "dos.img.gz" to "dos.img". 2. memdisk eat 70-100K low memory. i read from archive it's because i got a "broken pxe stack" so memdisk can not release. but i try several pxe bootable desktop & notebook, including emboot pxe boot disk for vmware. none can release the memory. so maybe someone can give a clue what pxe stack is good, then i can give it a try and make sure what's the problem.. 3. a stupid question. can we make floppy image bigger than 2.88M ? it seems not possible, but.. maybe any surprise?...

I often boot DOS using MEMDISK and 33MB HD images for remote flashing. After my flash I need to activate the NIC and send a signal. Currently I use different packet drivers for different NICs, but this link below looks like a universal solution: http://www.emboot.com/products_UniversalPacketDriver.htm Does any thing else like this exist that is open source or freely available and freely redistributable? Thanks.

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

Is it possible to chain isolinux and memdisk over pxelinux? If it's possible, I'd like to boot a CD Image over the network. I've been using pxelinux to boot ltsp for years, and recently upgraded to take advantage of memdisk for booting a DOS hd-image. Ideally I'd be able to boot a CD-Image. Thoughts? -- <:3)~ Michael T. Garrison Stuber

...w what image types you are attempting to support? We have, at times, done some custom work on bootstraps for VenturCom's BXP and also for vendors using WIN CE .net PXE bootstraps. Our interest is in extending as much bootstrap support as is reasonably possible, given the demand. Steve Marfisi emBoot Inc.

Hello all, I ran across a couple bugs in memdisk concerning hd images the other day. With the attached patch I've been able to successfully boot a 32MB gzipped hd image. (I'll put the image up for a short while at ftp://ftp.io.com/pub/usr/duanev/fdoshd.img.gz) The pxelinux.cfg entry I'm using is: label fdos kernel memdisk append keeppxe initrd=fdoshd.img.gz

HI there. Probably my message is a bit off topic but I do not know where else I could be asking. . I'm running a linux terminal server with one client provided with a 3C509B ISA card. I boot the later with a floppy bootable rom image taken from http://www.rom-o-matic.net/ Everything is working just fine. I decided to try to set up a PXE network boot (I'll needed it for installing a

Hello all, First off, thanks for the great work. I have recently added "more submenus" to a functioning advanced menu that only had one "submenu off of the main menu before" The addition of the new submenus has caused the main menu to not function correctly and I have been pouring over the code for several weeks and I just cannot see the error that I have introduced. This

I posted this to the group last year, but the problem was not fixed so I will give it another try. I use 3Com's PXE server to deploy the Fedora Core boot disk to my clients for an ftp install. I also have ghost boot disks, bios update disks, and a video bios repair disk all using the 3Com PXE server. The problem is when I try to boot a Linux kernel. With all versions of syslinux since 1.72