zorphnog

Perhaps you have a bad file, I'm not sure. Have you checked out your TFTP log to see what file its getting stuck on? It should try to read the files in this order: startrom.0 ntldr bootfont.bin (not needed) ntdetect.com winnt.sif winpe.iso

Does your iso boot as a CD?

First of all, your startrom.n12 should be renamed to startrom.0. The entry for winPE should look like this: label winpe kernel startrom.0 If your iso is in root directory, your winnt.sif should look like this: [SetupData] BootDevice = "ramdisk(0)" BootPath = "\I386\System32\" OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=winpe.iso" Architecture = "I386"

How about just loading WinPE the way you want it. Install the software. Mount a share. Image the PE drive to the share. Use the new image as your winPe boot. I don't know if it is possible to do that, as far as installing the software on PE goes, but it would be worth a try rather than trying to enter in all those reg entries.

Well, first of all there are multiple hives that you will have to load. Here are a few of them: HKLM\SOFTWARE = mount\windows\system32\config\SOFTWARE HKLM\SYSTEM = mount\windows\system32\config\SYSTEM HKEY_CLASSES_ROOT = Classes key under mount\windows\system32\config\SOFTWARE HKEY_USERS and HKEY_CURRENT_USER = Comprised of ntuser.dat files of your local user profiles (i.e. mount\Users\*\ntuser.dat) Quite frankly the list you posted was rather long so I didn't go into it. My question is what exactly are you trying to do? There may be an easier way.

I've never tried doing it, but you should be able to add the drivers to the original wim. Do the following, where c:\vistadvd\boot.wim is the original wim: mkdir C:\vistadvd\mount imagex /mountrw C:\vistadvd\boot.wim 1 C:\vistadvd\mount peimg /inf=C:\IBMdrivers\driver-01.inf C:\vistadvd\mount\Windows peimg /inf=C:\IBMdrivers\driver-02.inf C:\vistadvd\mount\Windows ... peimg /inf=C:\IBMdrivers\driver-NN.inf C:\vistadvd\mount\Windows imagex /commit /unmount C:\vistadvd\mount Unless they are a using CRC or some other type of file corruption detection method on the WIM file, that should work.

How were you trying to add the drivers to the original WIM? You should be using the /inf switch for PEImg which is still available even after a /prep command has been issued. Should look something like: peimg /inf=c:\mydevice.inf c:\winpe_x86\mount\windows

You don't need Windows 2008. WinPE 2.0 is based off the vista architecture so you should be fine. I don't use WDS so I am not familiar with the folder and file structure. Since you say it works on DVD, then it should just be a matter of putting the bootmgr.exe.mui file in the right location. I can't really tell you where that is without seeing the folder structure. Mainly, where are the 'bootmgr' and 'BCD' files?

Try putting it in: C:\RemoteInstall\Boot\en-US

Forget about the {current} comment. That appeared because I was in that PE environment when I ran the command. The acutal GUID didn't change.

Ok I set up a test box with you parameters and duplicated the error. I added a batch file and bcdedit to the \sysprep\i386\$OEM$ directory to add the correct entries back to the bcd. Worked flawlessly, but for some reason renamed the GUID to {current}. bcdfix.bat: @echo off bcdedit -set {ramdiskoptions} ramdisksdidevice partition=C: for /f "tokens=2,3*" %%i in ('bcdedit -enum bootapp') do set guid=%%i bcdedit -set %guid% device ramdisk=[C:]\sources\boot.wim,{ramdiskoptions} bcdedit -set %guid% path \WINDOWS\System32\boot\winload.exe bcdedit -set %guid% osdevice ramdisk=[C:]\sources\boot.wim,{ramdiskoptions} bcdedit -set %guid% systemroot \WINDOWS bcdedit -set %guid% winpe yes bcdedit -set %guid% detecthal yes Cmdlines.txt: "cmd /c \sysprep\i386\$OEM$\bcdfix.bat"

Have you tried it? Seems to me that the situation would still apply.

From M$ http://technet2.microsoft.com/windowsserve...3.mspx?mfr=true: Seems like fixntfs.exe should do the trick. So perhaps you could add this to a script and put it in sysprep\I386\$OEM$\CmdLines.txt

What does your boot.ini look like originally?

I have PE 2.0 and 1.6 booting from my pxe server using pxelinux as a boot menu. To get 1.6 to work, you need the following files: \ <--- root of your pxe boot folder ntldr ntdetect.com startrom.0 (renamed startrom.n12) winnt.sif \sources\winpe2005.iso Your winnt.sif file should look something like this: [SetupData] BootDevice = "ramdisk(0)" BootPath = "\I386\System32\" OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=sources\winpe2005.iso" Architecture = "I386"Note that you can put the iso wherever you want and name it whatever you like. Then just point your DHCP server to boot from startrom.0 (option 67). The only thing I don't like is that you have to hit F12 once your startrom.0 kicks off. I never have been able to figure out how to get rid of that prompt, but I rarely use 1.6 for one old prototype server that doesn't meet the requirements for PE2.0.

F2 will get you to the options menu and you can change the settings for displaying extra buttons.

Does the application execute when you try it manually?

Whats up Kel!? I'm doing fine. Just trying to catch up on WPI as I've been too busy to keep up with it lately. Looks like you've got everything under control though.

You need to have a default or as you say 'backup' wallpaper so that the user doesn't have a blank screen if they do not have one of your defined resolutions. Additionally, you can move all of this into one script tag. Here's what I've come up with: <img id='bgpic' src='./Themes/vista/defaultwallpaper.jpg' width="100%" height="100%"> </div> <script type="text/javascript"> switch(screen.width) { case 1920: if(screen.height==1200) { document.all.bgpic.src = "./Themes/vista/wallpaper1920ws.jpg"; } break; case 1600: if(screen.height==1200)) { document.all.bgpic.src = "./Themes/vista/wallpaper1600.jpg"; } else if(screen.height==1050) { document.all.bgpic.src = "./Themes/vista/wallpaper1600ws.jpg"; } break; case 1280: if(screen.height==1024) { document.all.bgpic.src = "./Themes/vista/wallpaper1280.jpg"; } break; case 1024: if(screen.height==768) { document.all.bgpic.src = "./Themes/vista/wallpaper.jpg"; } break; } </script>

I don't think that is possible. You can edit the boot loader within PE, but you are going to have to reboot for it to take effect. Then perhaps make a startup or shutdown script within XP so that it sets the boot loader back.

Have you tried installing the drivers silently without using WPI? It sounds like the problem is with your installer, not WPI.

Perhaps you have a corrupt wim file.

grub, lilo (linux) bcd (vista) boot.ini (XP, 2000, 2003)

Go into Options -> Installer tab and make sure that "Disable when dependencies are not met" is NOT checked.

http://www.autoitscript.com/gimagex/ <- works fine.