zorphnog

He's talking about how to apply the image to a machine using Windows PE (Pre-Installation Environment). However, doing this still has no affect on the HAL issue.

You can enable ActiveX using registry keys. I haven't tested it out, but I think should work: Windows Registry Version 5.00 [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3] "1001"=dword:00000000 "1200"=dword:00000000 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3] "1001"=dword:00000000 "1200"=dword:00000000 Is there any reason you are updating via the web page vice using automatic updates? Personally I have a script to enable automatic updates and prompt the WSUS to update the machine.

Ok, I'm at a loss. Can you post the code as you are using it in your HTA? It would give me a better idea of the context in which you are trying to run the command.

You have to edit the BCD for your PXE boot as well. Did you perform step 6 for your PXE BCD? It should be located at <pxeroot>\boot\bcd.

Most likely HAL or chipset drivers.

If you are applying an image to the exact same hardware then you shouldn't have any problems. If you intend to use the image for multiple hardware platforms then you will need to to sysprep the machine with all the drivers you need for your various hardware, and you will have to address the HAL issue properly.

Nope. The HAL issues still exist. Supposedly with vista you won't have to worry about HALs anymore, but with XP it is still an issue. Whether you use file-based (imagex) or sector-based (ghost) imaging doesn't matter.

Um...why aren't you just integrating updates into your unattended build?

No, no. No WPI. And it is no traditional GUI, it is only a non-affectable list with an arrow pointing at the program being installed at the moment. The image is linked from the RunOnceEx page in the excellent MSFN guide, Unattended Windows. Forgot to mention, when I run the RunOnceEx.cmd file, the list shows up as it should be right after next boot. It just wont do it during windows install. Sorry, I was thinking of something else. I believe your use of the CDROM variable is the cause of your issue. When you add a registry entry using the reg.exe tool, it does not replace local variables with their associated value. Therefore, when you add that a registry entry with that variable it still stores it as %CDROM% instead of the value of CDROM. My suggestion would be something like this: Commands.txt: [Commands] "rundll32 advpack.dll,LaunchINFSection nLite.inf,U" "Programmer.cmd" "Register.cmd" "%systemroot%\Cursors\Aero.cmd" "MakeRunOnceEx.cmd" "%systemroot%\RunOnceEx.cmd" "del /f /q %systemdrive%\RunOnceEx.cmd" MakeRunOnceEx.cmd: cmdow @ /HID @echo off FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\CD.txt SET CDROM=%%i: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx SET CMDFILE=%systemdrive%\RunOnceEx.cmd echo cmdow @ /HID > %CMDFILE% echo @echo off >> %CMDFILE% echo REG ADD %KEY% /V TITLE /D "Installerer noen kjekke programmer" /f >> %CMDFILE% echo REG ADD %KEY%\001 /VE /D "Fliqlo screensaver" /f >> %CMDFILE% echo REG ADD %KEY%\001 /V 1 /D "%CDROM%\Software\fliqlo.exe /VERYSILENT /SP-" /f >> %CMDFILE% echo REG ADD %KEY%\002 /VE /D "Rollercoaster Tycoon 2" /f >> %CMDFILE% echo REG ADD %KEY%\002 /V 1 /D "%CDROM%\Software\RCT2.exe" /f >> %CMDFILE%

Ok I've read some more and I think I was wrong about the sze switch as it is not necessarily needed, but still think the error is in the syntax of your switch. I've searched and I cannot find a mode=restore. There is a mode=prestore or mode=load. The prestore mode restores a specific partition and the load mode restores the entire disk. Heres a link to the -clone syntax. Switches: Cloning

WinPE 2.x is based off of the vista kernel, so I don't know that drivers from 1.6 (2003/XP) will work.

I've used VPC to mount an iso of my WinPE boot with ghost and spanned files, and to boot from network (PXE) into WinPE and restor spanned ghost files from the network. In both cases I have had no trouble.

I've had this problem too. As far as I know, there is no workaround for the issue other than finding a logo tested driver. I found a M$ article about how replacement of system protected files will cause the driver signing policy to be automatically elevated - Driver Signing Policy Is Automatically Elevated for Unsigned Drivers

I'm not sure where you got that picture from, but RunOnceEx does not have a GUI associated with it. I believe that picture is of a modified version of WPI (Windows Post-Installer). Check out their forum http://www.msfn.org/board/Windows_Post_Ins...rd_WPI_f93.html.

Just looked into some more and the eventlog service is running if you look at the services tab of the task manager in PE. My guess is that you are looking for some way to view the event logs which is where the problem lies. MMC is not on the PE build so there is no way to view the eventlog snap-in.

winpeshl.ini is used for starting a shell other than the default startnet.cmd command prompt. I'm not sure how you add a service to PE, I'll have to look into it more.

I use ghost and PE just fine in VPC.

You're missing the last part of the clone command, the sze parameter.

Try adding InstallFilesPath=<path to i386 directory> to the Unattended section of your winnt.sif.

I usually extract the .exe and find the .inf files. If you open a driver .inf it will have a section labeled [sourceDiskFiles]. The files listed in this section are the only files needed for the driver. So I delete all the extraneous files and only keep the ones needed, making sure I keep the folder structure intact. I then place all these files in a folder (C:\drivers) and add a them to the devicepath registry entry using the sysprep driver scanner tool. Oh and don't delete any of the .cat files, they are the security descriptors for the drivers.

I'll try to tackle some of these for you. Sysprep: Use setupmgr.exe to make your sysprep.inf file. This will allow you to cover most of the basic settings. I just use the GUI for syspreping, no command lines. I check mini-setup and click reseal. HAL: I tackle the HAL by forcing the "Advanced Configuration and Power Interface (ACPI)" driver before I sysprep. This way the image will work on any HAL platform. After I apply my image (Ghost) I scan the system to see if another HAL needs to be loaded and add the correct entry to the unattended portion of the sysprep.inf file. (I'm not sure what the 'haldetect.vbs" script does, but it should be something similar.) Mass Storage: Sysprep does not strip out all of the chipset drivers. The reason you have to use the BuildMassStorage section is because Windows needs to read extended portions of the hard disk during the boot loader. If you have not included mass storage drivers this extended section cannot be read causing the dreaded 0x7B BSoD. I don't use driverpacks bc I have a limited/known set of hardware platforms. I just add the drivers to the build before sysprep and use the sysprep driver scanner tool to add the paths to infs to the registry. I386 folder: The i386 folder isn't necessarily needed. If you want to add a cmdlines.txt or add files through the $OEM$ folder then you can use it, but it is not mandatory. Keep in mind that the entire sysprep folder will be deleted.

I've never tried accessing a database, but I believe your issue results from IE zone settings. In your software registry hive goto the key: SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Zones. For each zone (0-4), ensure that the value for the 1406 entry is 0. I'm fairly certain that zone 3 is the only one that matters, but I'm not sure so just try all of them. Heres a M$ page about zones and their settings: http://technet2.microsoft.com/windowsserve...3.mspx?mfr=true

What is the exact command you are trying to run?

Have you tried just calling wpeinit.exe instead of calling startnet.cmd?

My guess is that the registration info is either stored in a configuration file (.ini or similar) or the registry. Have you tried using filemon and regmon to trace what files and registry entries are being manipulated when you save the registration info? I would try myself, but i don't have/use this application. RegMon FileMon