similar to: Integrate 3com boot image files?

On Mon, Dec 8, 2014 at 10:44 AM, Leenders, Peter <Peter.Leenders at computacenter.com> wrote: > This look promising, if I could separate the config files for the different > boot architectures Bios and UEFI. I have 2 different boot files in 2 > different locations, but after startup they both refer to the > tftproot/pxlinux.cfg/default config file. The DHCP Option 209 may solve

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 all, Do any of you have any ideas for getting a DOS floppy to reboot to the hard drive (which may contain Windows 98 or XP or Linux or Novell etc etc)? I want to use syslinux, but it does not support the localboot option like pxelinux and isolinux do. Basically, I want to boot DOS from a floppy, run some DOS stuff, then reboot to the hard drive while leaving the floppy disk in the drive.

Hello Gene, thank you for your answer > > - Is there a standard approach to use different vesamenu.c32 (and other architecture depending ) files in the pxelinux.cfg/default file depending on the boot architecture - especially for BIOS/Legacy and EFI64? > I'd say there's no standard but there are choices. Check out this page I wrote up. >

> > ---------- Forwarded message ---------- > From: Frederic BOHE <fbohe-guest at alioth.debian.org> > To: nut-commits at lists.alioth.debian.org > Date: Wed, 16 Mar 2011 14:57:09 +0000 > Subject: svn commit r2940 - in > branches/windows_port/scripts/Windows/Installer: . ImageFiles > ImageFiles/Binary ImageFiles/Others ImageFiles/emptyDir >

> Hello everyone, > > I'm using a windows PXE server and I try to upgrade a existing PXELINUX menu structure with actually with BIOS/Legacy mode to work in UEFI mode too. > > Since I have to use ZENworks tftp on the windows server I have only one TFTP-root directory not 2 different tftp-root directories like on a standard windows > deployment server. ZENworks itself uses for

Dear All I have a problem with my Compaq EVO n410c laptop. I want to install Windows (Win98/WinXP) on it. But this laptop don't have any floppy/cdrom to boot from. I have try to use My USB Drive to boot, using syslinux. Here's my step 1. Format the USB Drive using "HP USB Disk Storage Format Tool" 2. Install syslinux (syslinux -f F:). F is my USB Drive 3. Using

Hi. We've been using PXELINUX for years, to kick off OS installations (floppy images) and booting assorted tools. The addition of ISO support in memdisk opened up some new alternatives that we also use, e.g. booting WinPE ISO images over PXE. Today I downloaded a BIOS for a HP EliteBook 8440p and discovered that the BIOS file is 3 MB. I could probably squeeze it onto a 2.88 MB floppy image

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

Hello Peter, is it possible to boot a CD-Image of a bootable CD (no disk emu) via pxe. I've build up the infrastructure to boot normal floppy images via PXE (under W2K and/or Netware). I have a ISO image of the bootable CD (1 tack TAO eltorinto with an a single boot sect -> bootimage is 2kB, ISO image about 600 MB) I suspect that a combination of MEMDISK and PXELINUX with activated UNDI

Hello, I have the following problem. I am trying to pxeboot a virtual machine using Sun's Virtualbox. I am trying to experiment with the menu options of pxelinux and this is my pxelinux.cfg/default file. # generated by fai-chboot for host cdbexample with IP 172.16.31.200 default menu.c32 prompt 0 default fai-generated timeout 300 #ONTIMEOUT local MENU TITLE PXE Menu LABEL fai-generated

> > Hello everyone, > > > > I'm using a windows PXE server and I try to upgrade a existing PXELINUX menu structure with actually with BIOS/Legacy mode to work in UEFI mode too. > > > > Since I have to use ZENworks tftp on the windows server I have only one TFTP-root directory not 2 different tftp-root directories like on a standard windows > > deployment

Hello, we are experiencing the same problem. Users get a question from Excel 2002 in the format: The file "<insert .xls file here>" may have been changed by another user since you last save it. In that case, what do you want to do?" You are then given the option to save a copy, or to overwrite changes. We are running 2.2.8a, but in similar environments using the same

HPA, I believe I've found a possible bug with /menu. This against the unmodified -pre5 snapshot. SRC: http://www.survivaldisk.com/menutest.c COMPILED: http://www.survivaldisk.com/menutest.com It's easiest explained if you just compile the .c and experience it for yourself, anyways. If you have two submenus nested within each other and then call a third menu it will bring up the

On Dec 8, 2014 5:24 AM, "Leenders, Peter" <Peter.Leenders at computacenter.com> wrote: > > > Hello everyone, > > > > I'm using a windows PXE server and I try to upgrade a existing PXELINUX menu structure with actually with BIOS/Legacy mode to work in UEFI mode too. > > > > Since I have to use ZENworks tftp on the windows server I have only one

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.

Thanks for the comment. The next pass for a file format ... ------ FILE BEGINS ----- # Comment lines [menu] item="text to display" status="status line text" action= SUBMENU | INACTIVE | whatever submenu= <number> data="arbitrary string" item="text to display" status="status line text" action= SUBMENU | INACTIVE | RUN | EXIT submenu=

Citeren Frederic BOHE <fbohe-guest op alioth.debian.org>: > +REM copy DLL files from system > +copy /Y c:\mingw\msys\1.0\bin\msys-1.0.dll .\ImageFiles\Others > +copy /Y c:\mingw\msys\1.0\bin\msys-crypto-1.0.0.dll .\ImageFiles\Others > +copy /Y c:\mingw\msys\1.0\bin\msys-ssl-1.0.0.dll .\ImageFiles\Others > +copy /Y c:\mingw\bin\libgnurx-0.dll .\ImageFiles\Others How can we be

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

> On Mon, Dec 8, 2014 at 10:44 AM, Leenders, Peter > <Peter.Leenders at computacenter.com> wrote: > > > This look promising, if I could separate the config files for the different > > boot architectures Bios and UEFI. I have 2 different boot files in 2 > > different locations, but after startup they both refer to the > > tftproot/pxlinux.cfg/default config