search for: computacenter

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

...=0 smb_tid=0 smb_pid=0 smb_uid=0 smb_mid=0 smt_wct=0 smb_bcc=0 session request failed root@sonne(1019)/> Do you have in idea how to make it run? Thanks in advance. Mit freundlichen Gruessen - Yours sincerely Malte Neubecker Administrator Support Services CC CompuNet AG & Co. oHG A part of Computacenter plc Europaring 34-40, 50170 Kerpen, Germany Phone: +49 (0) 2273 597-8487, Fax: +49 (0) 2273 597-222, Mobile: +49 (0) 172 8167940 E-Mail : Malte.Neubecker@computacenter.com Visit us on the Internet: http://www.computacenter.com This email is confidential. If you are not the intended recipient, you...

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

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

...s fails to start, and also some dependent processes, so no domain login is available. If i try to logon directly after the join process (without the restart) it works fine, all shares are available. Has anyone heard of this before?? Best regards, D.Landmann Visit us on the Internet: http://www.computacenter.com This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document.

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.

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

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

Hello Peter, do you know a way to integrate existing submenu's created by the 3com boot image editor into pxelinux? I know it is possible to build the menu's in pxelinux and use memdisk for imagefiles, but it will mean to recreate about 70 menu's and 350-400 image files. Yours sincerely Peter Leenders

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

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

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

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 Legacy mode a patched

>I could be wrong about this, but... I think that it could still be possible to get multiple architectures / firmwares mixed together >while using c32 modules, without dhcp options, and perhaps even without applying pxelinux-options. > >If I understood correctly, this tftp server can choose between 2 boot files, depending on BIOS/UEFI client, and the problem is >choosing a

>>According to prior pcap reports, syslinux.efi searches for syslinux.cfg (too), while (l)pxelinux.0 will be searching for "default". >This means that using something *similar* to: >> pxelinux.cfg/default: >> PATH bios >> CONFIG common-config.cfg ::bios >> # the bios modules should be located in the bios subdir >> >>and >>