search for: loronix

Hello... I have PXELINUX working nicely on FreeBSD, but I have exactly zero experience with Windows Server. What I would like to do is: Have PXE client connect to Windows DHCP server to get value "filename pxelinux.0" Have PXE client connect to Windows TFTP server to download pxelinux.0, display, pxelinux.cfg/default, memdisk, and appropriate initrd files (really bootable floppy

Hello... Last week I demonstrated a problem with PXELINUX's ability to launch the FreeBSD "pxeboot" program. Mr. Anvin suggests that this can be fixed. I'm glad, because this PXELINUX/pxeboot problem is the very last technical issue for a project on which I've been working since September. My company has a proprietary disk-imaging system that they would like to replace.

Hello again... I'd like to confirm that I really understand what the LABEL property in the PXELINUX config file is doing: Assume that at the "boot:" prompt, I want to issue the command "memdisk initrd=floppy1", and I want to attach this command to label "A". If I were to put this in the config file: LABEL A KERNEL memdisk APPEND initrd=floppy1 Then if

Hello again... PXELINUX shows my DISPLAY file nicely, but seems to ignore the "special codes" noted in the SYSLINUX documentation. Perhaps I'm using them incorrectly? My display file looks like: *************************************** <FF> <SI> 5e Message message. Message message message message. <EM> *************************************** The

Hello... Added real control characters to the file, but they were still ignored-- until I added "IMPLICIT 0" to the config file, and then they were interpreted properly. Now if I can figure out how to eliminate the "Could not find kernel image:" message, this'll look really sharp. -Chris -----Original Message----- From: McMahon, Chris Sent: Monday, November

Set "PROMPT 1" in the config file. -----Original Message----- From: McMahon, Chris Sent: Monday, November 17, 2003 12:40 PM To: McMahon, Chris; 'syslinux at zytor.com' Subject: Found it; getting closer. RE: Use DISPLAY codes with PXELINUX? Hello... Added real control characters to the file, but they were still ignored-- until I added "IMPLICIT 0" to the config

Hello... With syslinux pre7, I am consistently getting what looks like a stack dump out of the FreeBSD loader. I have seen this behavior from pxeboot before. Maybe once out of every fifty or so runs of pxeboot, I would see an error message like the one below, but it was both rare and inconsistent. Now I am getting this message every time pxelinux invokes pxeboot: BTX loader 1.00 BTX

Hello... I put pre9 in place and it works great. Thank you very much! This really was The Very Last Problem in a pretty complex system. -Chris -----Original Message----- From: H. Peter Anvin [mailto:hpa at zytor.com] Sent: Friday, November 21, 2003 1:13 AM To: H. Peter Anvin Cc: McMahon, Chris; 'syslinux at zytor.com'; 'mike at flux.utah.edu' Subject: Re: [syslinux]

Dirk Haus wrote: >What would be the syntax to call other NBPs vom >pxelinux (and has someone already tried it with 3Com`s >Boot Image Editor "imgedit" bootstraps)? I haven`t >found a single word about this feature in the pre-7 >tarball. Mr. Haus, I would very much like to know about your experience invoking another NBP from PXELINUX. I'm trying and failing to

Hi again... The text under "BTX loader..." should appear as a block where each line is 56 characters long. "BTX halted" is on its own line. Apologies for my mailer... -Chris -----Original Message----- From: McMahon, Chris Sent: Wednesday, November 19, 2003 8:32 AM To: 'H. Peter Anvin'; McMahon, Chris Cc: 'syslinux at zytor.com'; 'mike at

Hello... In the split-second before the reboot, I can see that the pxeboot.0 process is indeed started-- pxeboot gets out just over 2 lines of text before the reboot occurs. So it's not a "ready" message. The text in question is (without *'s): ****************************************** PXE Loader 1.00 Building the boot loader arguments Relocating the loader and the

The stack dump message is white text on black background. Right above the stack dump message, still in yellow-on-blue from the PXELINUX settings, is the text: Building the boot loader arguments Relocating the loader and the BTX Starting the BTX loader <change to white-on-black> BTX loader 1.00 BTX version is 1.01 <stack dump> Would that business of "arguments...

Hello, I hope this doesn't bounce again... I'm having trouble passing control of the PXE process from PXELINUX to the FreeBSD "pxeboot" program. I tried invoking "pxeboot" from the PXELINUX "boot:" prompt. This causes an error "Invalid or corrupt kernel image." I named pxeboot "pxeboot.0" and tried invoking pxeboot.0 from the