HI There, Firstly a bit about me. I am a bit of an old school PXE user from the Kingdom of Gates. I have also spent years in the Linux playground. While I have never been a programmer I am fairly competent in scripting languages, both on windows and Linux. My occupation is "System Builder" I build operating System images and discs (not the OS itself). So I actually customize OS's. This year The Gates crowd have stepped up our game and we had to upgrade to Windows 2008 Svr, Purely to manage the new (5 year old) image format by Gates and his buddies. Wim file or Windows Image Files. I have to hand it to them. What I normally store in 1.1TB using Ghost I now store in 80GB. Pretty good, but the MS WDS PXE sucks. And there are so many limitations to the system that I am giving the PXE Linux a go on Win2008svr and I have it working and I love it. I have 6 distros configured with our corporate branding using kickstart files and scripts to automate the installations of OS's to PC's. My idea is to load Linux on every system a customer buys from us, so that people can see, feel and try. I have deployed close to 10000 systems in the past 5 years with Linux loaded, if 2% have kept it I am more than happy. My Problem. The one problem I face is that you should press F12 to boot from network, if you don't - the system must continue to boot from the next boot device. This is not what happens to me with PXELinux 3.72, I don't press F12 and the system still boots from network. Is there a solution to preventing this from happening? I would really appreciate some help here. Regards Chadley RHCT
> > My Problem. > The one problem I face is that you should press F12 to boot from network, if you don't - the system must continue to boot from the next boot device. > This is not what happens to me with PXELinux 3.72, I don't press F12 and the system still boots from network. > > Is there a solution to preventing this from happening?Yes. Set the BIOS boot order correctly. I have no such issues, and somewhere north of 1000 client machines. -- ian
Chadley Wilson <chadley at pinteq.co.za> writes:> The one problem I face is that you should press F12 to boot from > network, if you don't - the system must continue to boot from the > next boot device. This is not what happens to me with PXELinux > 3.72, I don't press F12 and the system still boots from network.I'm confused. Surely you know that the priority of boot devices is determined by the BIOS. Enter the BIOS setup and configure it to your liking. PXELinux is only started if the computer is already booting from the network, so it has absolutely nothing to do about this... -- Feri.
Thank you all this has solved the issue perfectly. I really appreciate a list where people make an effort. To a first class group of people I Salute you.. -----Original Message----- From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On Behalf Of H. Peter Anvin Sent: 22 October 2008 06:06 PM To: For discussion of Syslinux and tftp-hpa Subject: Re: [syslinux] PXE Linux boot to F12 automatically Claus Andersen wrote:> > LABEL Localboot > MENU LABEL Localboot > MENU DEFAULT > KERNEL util/localboot.c32 > APPEND 0 >Or just: LABEL Localboot MENU LABEL Localboot MENU DEFAULT LOCALBOOT 0 _______________________________________________ Syslinux mailing list Submissions to Syslinux at zytor.com Unsubscribe or set options at: http://www.zytor.com/mailman/listinfo/syslinux Please do not send private replies to mailing list traffic.