JSmith Posted December 21, 2006 Share Posted December 21, 2006 Hello guys, and thanks for reading this in advance. I decided rather than semi-hijacking other peoples threads to just make a new one.So here is my situation. I've seen and tried to follow some other peoples work here, and it has helped me get *almost* everything I need I believe, but I am missing something yet to get this to PXE boot PE2.For starters, here is my ftp root directory, files and files in subdirectorys. I've tried the shotgun effect in this case so almost all files are in the root and the boot directories.tftpdroot\abortpxe.comtftpdroot\BCDtftpdroot\boottftpdroot\boot.sditftpdroot\BOOTFIX.BINtftpdroot\bootmgr.exetftpdroot\display.msgtftpdroot\en-UStftpdroot\hdlscom1.comtftpdroot\hdlscom1.n12tftpdroot\hdlscom2.comtftpdroot\hdlscom2.n12tftpdroot\P.imztftpdroot\pxeboot.0tftpdroot\pxeboot.comtftpdroot\pxeboot.n12tftpdroot\pxelinux.0tftpdroot\pxelinux.cfgtftpdroot\SETUPLDR.BINtftpdroot\startrom.0tftpdroot\startrom.comtftpdroot\startrom.n12tftpdroot\WdsConfig.inftftpdroot\wdsnbp.0tftpdroot\wdsnbp.comtftpdroot\winpe.wimtftpdroot\winpe_x86.isotftpdroot\boot\abortpxe.comtftpdroot\boot\BCDtftpdroot\boot\bootmgr.0tftpdroot\boot\bootmgr.exetftpdroot\boot\en-UStftpdroot\boot\hdlscom1.comtftpdroot\boot\hdlscom1.n12tftpdroot\boot\hdlscom2.comtftpdroot\boot\hdlscom2.n12tftpdroot\boot\pxeboot.0tftpdroot\boot\pxeboot.comtftpdroot\boot\pxeboot.n12tftpdroot\boot\WdsConfig.inftftpdroot\boot\wdsnbp.0tftpdroot\boot\wdsnbp.comtftpdroot\boot\WinPE.wimtftpdroot\boot\en-US\bootmgr.exe.muitftpdroot\en-US\bootmgr.exe.muitftpdroot\pxelinux.cfg\defaulttftpdroot\pxelinux.cfg\menu.c32tftpdroot\pxelinux.cfg\olddefaultNext is the lovely "pxelinux.cfg\default" file. Some contents ommited that are irrelevant. (I have a load of IMZ files that also boot for other reasons, which are also omitted from the directory structure above)default 1timeout 50implicit 0prompt 1display display.msglabel PE KERNEL \boot\wdsnbp.0LABEL LOCAL localboot 0As a side note, this may be the root of my problems, maybe not. I can't seem to get two of the commands from the "Configure boot configuration" phase to run correctly, maybe you can provide some input on that. The full script is as follows, the two lines that are commented out are the problem lines. The rest run sucessfully with no error. The first commented line will run sucessfully without the /inherit switch and option. The second line doesnt run at all, for any reason I can tell. I have tried swapping the "-" to a "/" as suggested, but it didn't work for me. I am doing this from a Vista Ultimate machine, so I really shouldnt be missing any functionality... I'm stumped.Bcdedit -createstore c:\BCDBcdedit -store c:\BCD -create {ramdiskoptions} /d “Ramdiskoptions” Bcdedit -store c:\BCD -set {ramdiskoptions} ramdisksdidevice bootBcdedit -store c:\BCD -set {ramdiskoptions} ramdisksdipath \boot\boot.sdiBcdedit -store c:\BCD -create {dbgsettings} /d “DebuggerSettings” Bcdedit -store c:\BCD -set {dbgsettings} debugtype serialBcdedit -store c:\BCD -set {dbgsettings} baudrate 115200Bcdedit -store c:\BCD -set {dbgsettings} debugport 1:: NEW GUID CREATED HEREfor /f "tokens=1-3" %%a in ('Bcdedit -store c:\BCD -create /d “WinPEBootImage” /application osloader') do SET GUID1=%%c::Bcdedit -store c:\BCD -create {bootmgr} /d “VISTABootManager” /inherit {dbgsettings}Bcdedit -store c:\BCD -set {bootmgr} timeout 30 ::Bcdedit -store c:\BCD -set displayorder %GUID1%;Bcdedit -store c:\BCD -set %GUID1% systemroot \WindowsBcdedit -store c:\BCD -set %GUID1% detecthal YesBcdedit -store c:\BCD -set %GUID1% winpe YesBcdedit -store c:\BCD -set %GUID1% osdevice ramdisk=[boot]\Boot\WinPE.wim,{ramdiskoptions}Bcdedit -store c:\BCD -set %GUID1% device ramdisk=[boot]\Boot\WinPE.wim,{ramdiskoptions}I appreciate you guys taking the time to read all this, this forum has provided me a lot of help and you guys are great! Link to comment Share on other sites More sharing options...
Jazkal Posted December 21, 2006 Share Posted December 21, 2006 I can't help with most of it, but I can tell you that you will run into problems if your \boot folder isn't "Boot". something about the windows boot loader is case sensitive. Link to comment Share on other sites More sharing options...
JSmith Posted December 21, 2006 Author Share Posted December 21, 2006 Alright, I'll try that out. Thanks! Link to comment Share on other sites More sharing options...
JSmith Posted January 10, 2007 Author Share Posted January 10, 2007 Bump to see if anyone has any ideas. I've been working with Microsoft on making a "flat file" method work, but thus far haven't been able to make either method work. In PXELINUX what would you use as the kernel for booting this? This is where I am stuck and I am not sure Microsoft understands the workings of PXELINUX enough to answer. Link to comment Share on other sites More sharing options...
Jazkal Posted January 10, 2007 Share Posted January 10, 2007 rename startrom.n12 to startrom.0And give me the error message your getting. Link to comment Share on other sites More sharing options...
JSmith Posted January 10, 2007 Author Share Posted January 10, 2007 I'm getting the 'txtsetup.sif is corrupted or missing' error. after it pulls the whole file down. I am currently using an ISO instead of the WIM as well, but can go either way.If my understanding is correct, txtsetup.sif isn't even used in PE2. Link to comment Share on other sites More sharing options...
bj-kaiser Posted January 11, 2007 Share Posted January 11, 2007 ... In PXELINUX what would you use as the kernel for booting this? This is where I am stuck and I am not sure Microsoft understands the workings of PXELINUX enough to answer.try using pxeboot.n12 as kernel in the PXElinux config. Link to comment Share on other sites More sharing options...
Jazkal Posted January 11, 2007 Share Posted January 11, 2007 We are using the WIM file for our pxe booting. we tried the ISO at first, because that is what we were using with WinPE v1.6, but didn't have good luck using it.Here are the files we are using in our "Boot" folder:abortpxe.combootmgr.exehdlscom1.comhdlscom1.n12hdlscom2.comhdlscom2.n12pxeboot.comWdsConfig.infwdsnbp.comboot.sdipxeboot.0BCDAnd we are booting the pxeboot.0 file. Link to comment Share on other sites More sharing options...
JSmith Posted January 11, 2007 Author Share Posted January 11, 2007 Cool, thanks for the ideas, I'll test em out! Link to comment Share on other sites More sharing options...
JSmith Posted January 11, 2007 Author Share Posted January 11, 2007 Hrm, so far no go. Are you guys using pxelinux? I am guessing thats where my complications are comming from, but man it will make things more difficult without it. Link to comment Share on other sites More sharing options...
bj-kaiser Posted January 11, 2007 Share Posted January 11, 2007 (edited) I use PXElinux to boot PE 2.0 from a OpenSuSE box.So far, the only problems I had were related to missing files. I would recommend you get a copy of WireShark if you don't already have it and watch the boot process (since the MS TFTP server lacks a decent logging, as far as I have seen and heard).If you think it could help you, I can post the log of my TFTPd, but since I am back to work on monday, it will take some time. Edited January 11, 2007 by bj-kaiser Link to comment Share on other sites More sharing options...
JSmith Posted January 15, 2007 Author Share Posted January 15, 2007 I'm not 100% sure i'd know what to do with the logs, but perhaps my network guy would. I am going to try a newer version of pxelinux, the one we are using is dated 09/2005 and there are newer versions. Link to comment Share on other sites More sharing options...
bj-kaiser Posted January 16, 2007 Share Posted January 16, 2007 (edited) This is the (shortened) log of my tftpd, while I boot to PE 2.0. As you can see from the NAKs there are some files I don't have in the tftp share, but that doesn't hold the boot of Windows PE in any way (at least it doesn't look like that for me). The interesting information for you are the RRQs with the filenames that are read from the client. You don't need to care about the filenames that follow after the "remapped", that's only because I prefer to have my own directory structure in the tftp share. 07:06:34 in.tftpd[14917]: RRQ from 192.168.X.X filename pxelinux.007:06:34 in.tftpd[14918]: RRQ from 192.168.X.X filename pxelinux.007:06:34 in.tftpd[14928]: RRQ from 192.168.X.X filename pxelinux.cfg/default07:06:34 in.tftpd[14929]: RRQ from 192.168.X.X filename menu.c3207:06:34 in.tftpd[14930]: RRQ from 192.168.X.X filename pxelinux.cfg/default07:06:38 in.tftpd[14931]: RRQ from 192.168.X.X filename /boot/pe20/pxeboot.007:06:38 in.tftpd[14932]: RRQ from 192.168.X.X filename bootmgr.exe remapped to /boot/pe20/bootmgr.exe07:06:39 in.tftpd[14933]: RRQ from 192.168.X.X filename \Boot\Fonts\wgl4_boot.ttf remapped to /boot/pe20/Fonts/wgl4_boot.ttf07:06:39 in.tftpd[14934]: RRQ from 192.168.X.X filename \Boot\Fonts\wgl4_boot.ttf remapped to /boot/pe20/Fonts/wgl4_boot.ttf07:06:39 in.tftpd[14935]: RRQ from 192.168.X.X filename \boot.ini remapped to /boot/pe20/boot.ini07:06:39 in.tftpd[14935]: sending NAK (1, File not found) to 192.168.X.X07:06:54 in.tftpd[14936]: RRQ from 192.168.X.X filename \Boot\BCD remapped to /boot/pe20/BCD07:06:54 in.tftpd[14937]: RRQ from 192.168.X.X filename \Boot\BCD remapped to /boot/pe20/BCD07:06:54 in.tftpd[14938]: RRQ from 192.168.X.X filename \Boot\Fonts\wgl4_boot.ttf remapped to /boot/pe20/Fonts/wgl4_boot.ttf07:06:54 in.tftpd[14939]: RRQ from 192.168.X.X filename \Boot\Fonts\wgl4_boot.ttf remapped to /boot/pe20/Fonts/wgl4_boot.ttf07:06:54 in.tftpd[14940]: RRQ from 192.168.X.X filename \hiberfil.sys remapped to /hiberfil.sys07:06:54 in.tftpd[14940]: sending NAK (1, File not found) to 192.168.X.X07:06:54 in.tftpd[14941]: RRQ from 192.168.X.X filename \Boot\WinPE.wim remapped to /boot/pe20/WinPE.wim07:06:54 in.tftpd[14942]: RRQ from 192.168.X.X filename \boot\boot.sdi remapped to /boot/pe20/boot.sdi07:06:54 in.tftpd[14943]: RRQ from 192.168.X.X filename \boot\boot.sdi remapped to /boot/pe20/boot.sdi07:06:55 in.tftpd[14944]: RRQ from 192.168.X.X filename \Boot\WinPE.wim remapped to /boot/pe20/WinPE.wim07:07:28 in.tftpd[14948]: RRQ from 192.168.X.X filename \Boot\Fonts\wgl4_boot.ttf remapped to /boot/pe20/Fonts/wgl4_boot.ttf07:07:28 in.tftpd[14949]: RRQ from 192.168.X.X filename \Boot\Fonts\wgl4_boot.ttf remapped to /boot/pe20/Fonts/wgl4_boot.ttf Edited January 16, 2007 by bj-kaiser Link to comment Share on other sites More sharing options...
JSmith Posted January 16, 2007 Author Share Posted January 16, 2007 Awesome thanks. With that tip and a little help from a network trace I am now booting!Thanks a ton for your help!On a side note, is there a way to bypass the need to press F12 to PXE boot? It seems to freeze up all the time if you don't press F12 fast enough, and to me that extra key press is an annoyance anyway since I already have the pxelinux menu.Thanks again!John Link to comment Share on other sites More sharing options...
bj-kaiser Posted January 16, 2007 Share Posted January 16, 2007 "pxeboot.n12" is the loader without the F12 request. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now