A related question: if the primary boot option is PXE boot, how do I prevent an infinite loop? Currently linuxboot-4.6 gets booted by PXE, WXP setup.exe configures the disk, but even on the 2nd run it does not recognize that the disk is already formatted and WXP waits to get booted to continue the windows configuration. Can I rename the tftpboot config file (the 32bit hex-IP filename) somehow during or after the first run, so that the "default" file can have localboot as 1st option? Can PXE boot "look" at the hard disk and decide it's worth booting? While playing with unattended I created a file C0A86420 manually (for 192.168.100.32, my test machine) with localboot option (and this works), but I'd like to have even this one automated ;).
Here we set our default boot option to be localboot. We then create hex files for the clients that need to be installed.
We also have a script in our TFTP server that deletes/moves the client hex config file after it finishes handing out the TFTP image.
HTH, --- Ryan Go Renaissance Technologies Corp. Direct: 631-444-7105 ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ unattended-info mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unattended-info
