wimboot, I'm stumped
|
2014-01-12, 02:46
Post: #1
|
|||
|
|||
wimboot, I'm stumped
Im hoping i'm missing something particularly trivial here, I cant find the disconnect.
I didnt want to install iPXE directly on my networking card, so i settled on chainloading. I have my TFTP server set up, and can successfully PXE boot, pull the undionly.kpxe, and get to the IPXE> command line from ctrl + B. from there, I decided for now i would manually direct to which setups i wanted to do until i better understood how to configure menus. I have my windows 7 installation media all unpacked and in a folder on a web server. (address 192.168.1.10/Win7) permissions are all set and i can access. I followed the wimboot instructions and set up an boot.ipxe file *well, i named it W7.ipxe). So from the IPXE> command line i type the following and it hangs. so maybe its something in my W7.ipxe file? Code: IPXE> dhcp W7.ipxe is below (note ive tried using relative paths... my install files are in server/Win7/W7, ive tried moving them to server/Win7) Code: #!ipxe is something wrong with my file that i'm missing? as an example, I tried this, with success: Code: IPXE> dhcp If i need to give more information, i gladly will. I'm at a loss for ideas.. Thanks for any help i can get! |
|||
2014-01-18, 20:46
(This post was last modified: 2014-01-18 20:47 by mecasull.)
Post: #2
|
|||
|
|||
RE: wimboot, I'm stumped
So, I created an ipxe file kon my local server that mimiced the demo file on ipxe.org... That file loaded successfully, leading me to believe my file that starts wimboot is botched, or the wimboot files themselves are messed up. Anyone have any clues?
|
|||
2014-01-19, 03:41
(This post was last modified: 2014-01-19 03:42 by MultimediaMan.)
Post: #3
|
|||
|
|||
OK, it's ugly, but you can debug it line by line:
Recommendations:
1) Recreate the file in gEdit or another POSIX-compatible editor. 2) Don't use leading tabs or spaces 3) Do make sure any trailing spaces are deleted. Line By Line debug example: added an echo and a sleep statement with tailing pipes to let the script continue if there are errors. You should be able to see where the problem is in the called script. Code: #!ipxe Best, M^3 "Thus far, you have been adrift within the sheltered harbor of my patience..." |
|||
2014-01-19, 03:50
Post: #4
|
|||
|
|||
RE: OK, it's ugly, but you can debug it line by line:
(2014-01-19 03:41)MultimediaMan Wrote: Recommendations: Meant to hop on here... I tried the leading spaces a couple of hours ago and had success. I feel kind of dumb that this was the problem, but everything is resolved, now. Thank you for your feed back, though, you were spot on. |
|||
2014-01-19, 03:57
Post: #5
|
|||
|
|||
RE: OK, it's ugly, but you can debug it line by line:
I was pretty sure those leading spaces were trouble, but didn't want to dismiss anything out of hand. Another common problem is which bootmgr file you use.
The trailing pipes Code: || Glad you got it sorted! M^3 "Thus far, you have been adrift within the sheltered harbor of my patience..." |
|||
2014-01-20, 08:57
Post: #6
|
|||
|
|||
RE: wimboot, I'm stumped
For the record, if you build iPXE with DEBUG=script it will automatically print every command before it is executed. No need to add lots of echo statements unless your setup makes it hard to recompile and deploy a new iPXE binary.
|
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)