zorphnog

I'm not familiar with this application. What kind of installer does it use?

Ok. I downloaded the KB883667 hotfix and installed it on my baseline and it appears to fix the problem. I've tested it with the NSC1100 & ATM1200 chips and have not seen the issue again. On a side note I have ran into this issue before I had the hotfix and found a crude way to prevent it. As far as I can tell, this method will work for any device that causes the Hardware Device Wizard pop-up during mini-setup. If you add a ConfigFlags=0x40 entry for the Device Instance ID of the afflicting device to the registry before syspreping, the wizard will not popup. The only problem with this method is that you need to know the Device Instance IDs of all versions of the device that is causing the problem. Before I used the hotfix, these are the registry settings I used to import before sysprep: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\NSC1100\4&58fa20d&0] "ConfigFlags"=dword:00000040 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\ATM1200\4&38462492&0] "ConfigFlags"=dword:00000040 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\ATM1200\4&2909ad21&0] "ConfigFlags"=dword:00000040 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\NSC1100\4&58fa20d&0] "ConfigFlags"=dword:00000040 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\ATM1200\4&38462492&0] "ConfigFlags"=dword:00000040 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ACPI\ATM1200\4&2909ad21&0] "ConfigFlags"=dword:00000040 The hotfix is the way to go, but if it doesn't work for you thats a viable workaround. Finding the instance ids is the biggest hurdle though.

I'll try it out. Not quite the same problem, but maybe it will work (who knows).

I have a sysprep'd XP image for multiple hardware platforms. I have learned from past experience that the IBM TPM driver will cause problems during mini-setup if you allow it to be installed (TPM must have a certain HAL loaded to install). So I have completely removed the TPM driver install files from my image. This was working fine for quite some time, until recently. Now when windows goes through the mini-setup driver installation portion I always get a hardware wizard for a "Unknown" driver which is the TPM security chip. This wizard pauses the unattended mini-setup until the user cancels. I have UnsignedDriversPolicy=Ignore and UpdateInstalledDrivers=Yes in my sysprep.inf. I have searched the baseline image for any cached references to TPM.inf/.sys and have found none. Personally, I am baffled as to why a wizard prompting the user for action is even occurring during an UNATTENDED mini-setup. Has anyone experienced this issue or know of a workaround?

I add WMI, HTA, Scripting and XML to my image, but you shouldn't need HTA or WMI so it may just be the XML package. Doesn't make since to me but give it a try.

Look in the Application Installs for silent install switches.

strBody = strBody & "<td><Input type=radio name=envList checked value=Production onclick=proBG>" &_ "Production" & "</BUTTON><BR>" strBody = strBody & "<Input type=radio name=envList value=Development onclick=devBG>" &_ "Development" & "</BUTTON></td>" Sub proBG bg.InnerHTML = "<img src='probg.bmp'>" End Sub Sub devBG bg.InnerHTML = "<img src='devbg.bmp'>" End Sub

You know you can add WMI support to WinPE 2.0 and you won't get these errors. I haven't tried using WPI in PE, but I do use several other hta's and just as a rule of thumb I always add scripting and wmi support. You can add them to your PE image by using the peimg tool. i.e. peimg /install=*scripting* <pathtoPEmount>\Windows peimg /install=*wmi* <pathtoPEmount>\Windows

I believe he is installing tools/apps that cannot be integrated into the PE image.

Did you disable the firewall?

Do you have a winpeshl.ini file in your system32 directory? If you do, it will be used to load your shell instead of startnet.cmd.

Sounds like a bug. You could try invoking a sleep command after the reboot command to make it wait a while. Try something like: "%wpipath%\Tools\sleep.exe 10".

You want to create silent installs. Go to this forum to find silent installs for applications: http://www.msfn.org/board/Application_Installs_f80.html.

No. All on one line. "Filecopy <source> <destination>". Read the manual.

How did you make your comment? You realize that the following is one line not two? Setup=SetupX.exe /qb! /NORESTART RebootYesNo="No" NERO_SCOUT="FALSE" serialnum_userval="xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx" AgreeToLicense="Yes" EULA_AGREEMENT=1 Silent=2

7-Zip, WinZip, WinRAR....

I haven't looked at it lately. I've just been too busy to mess with it anymore and I'm not sure that there is anything more we can do from the HTA/JavaScript side. I really think this has something to do with something beyond the scope of WPI. From best I can tell, it has something to do with Office 2003 pausing/resetting/killing mshta. I'm out of ideas. Sorry. I will say that I've never experienced this issue when I slipstream the updates using an administrative installation point and Office Resource Kit. Here is a copy of the notes I made when I created my installation package for Office 2003:

I try - I have only pl-pl folder: \boot\pl-pl\bootsect.exe.mui - still english text... en-US is the default language. Its always going to be in English if you don't put bootmgr.exe.mui in a en-US folder or change the bcd. Rename the pl-pl folder to en-US: \boot\en-US\bootmgr.exe.mui Yes you can use bcdedit.exe. WinPE 2.0 is based off of the Vista kernel/architecture. Thats why it uses BCD and bootmgr to boot from rather than boot.ini and ntldr.

I'm not aware of any built-in authentication options. The only thing I can think of doing is to have your batch script or whatever you want to run located on a network share. Create a simple HTA, VBScript, or batch file that asks for authentication information and attempts to connect to the network share using this information. Set this hta, script, or batch file as your winpe shell using winpeshl.ini. Hope that makes some sense.

I'm guessing you want to change the bootloader to another language? If that is the case, then placing the pl version of the bootmgr.exe.mui file in the ISO\boot\en-US folder should work. If that doesn't work, then you will have create a folder for pl, ISO\boot\pl-PL, and place the bootmgr.exe.mui file in there. Then you will have to change the bootmgr language to pl-PL by modifying the BCD (ISO\boot\bcd).

You can throw in an alert line that will display the value. Something like: alert("Architecture value = "+getArch()). Put it in WPI.hta somewhere after the api.js file is loaded.

Edit your WPI\WPIScripts\useroptions.js file. Look for an entry that says ShowExtraButtons and set it to true. If you are running it from cd, change teh DoNotShowIfCD to false.

I don't think that this will be of much help, but just remember that 1GB = 1024 MB not 1000. So 12GB = 12288MB, 19GB = 19456MB, and 9500MB = 9.28GB.

Look for winpeshl.ini in the WAIK documentation.

Just the original error with it not running WPI. The registry keys would have to be saved to HKLM to work in any profile.