untermensch

I wrote a script to do this, it's primary purpose was to "pre-activate" a Windows 7 install DVD but it grew to also install drivers, updates, setup background customization and a few more things. Is this not the preactivation kit from MDL. yes this is the preactivation kit I posted on MDL there is no way to get around updating each and every edition in install.wim but with the scripts you can do something else for the hour it will take to get the job done.

I wrote a script to do this, it's primary purpose was to "pre-activate" a Windows 7 install DVD but it grew to also install drivers, updates, setup background customization and a few more things. [link removed] updated the scripts on 07/06/2010 a little more user friendly now.

I use this batch script for 7Zip @echo off IF %PROCESSOR_ARCHITECTURE%==AMD64 ( msiexec /i "%~dp07z465-x64.msi" /qn ) ELSE ( msiexec /i "%~dp07z465.msi" /qn )

the easy way OEM background. OEMBackground.zip

I have patched setup to allow just this. fire up a hexeditor and edit winsetup.dll in dvdroot\sources and boot.wim\sources after the mod you will be able to create a whole disk partition during setup by manualy creating the partition, if you just click next windows will use the default partition layout. 32 bit Comparing files orig_winsetup.dll and mod_WINSETUP.DLL 00077798: 74 EB 64 bit Comparing files orig_winsetup.dll and MOD_WINSETUP.DLL 00084AC4: 74 EB premoded winsetup.dll here http://www.mediafire.com/file/ao423wzdjko/...ed_winsetup.zip doesnt work with unattended installs, someone better with IDA than me will have to give that a try look sorta easy if you know assembly.

this .bat script works awesome!!! get all the .net service packs and updates integrated as well. http://www.msfn.org/board/Silent-NET-Maker...l&hl=dotnet

Ok I just tried installing on a virtual machine, and had the same result, reboot loop after first reboot durring install. so I tried to see if the problem is reproducable by reusing the same last sesion.ini on a new run with nlite. EVERYTHING the same as before. this time I got a working install. also I have gotten corupted files in the ISO's in the past with this version of nlite. but agin I cant reproduce the problem.

Im having the same problems, not sure what is causing it.

I tried this but the install didnt start, I tried a half hearted attempt to figure out how the install was started but when I noticed that the winpe.wim was quite abit larger than the stock one I gave up and just updated the hal.dll

This problem occurs if the following conditions are true: • The computer uses more than 3 GB of RAM. • The computer uses a storage system that is running the Storport miniport driver. • The computer uses a controller that uses 32-bit direct memory access (DMA). clearly your system doesn't meet all the above requirements, and an update from microsoft does not update your install DVD, if your getting blue screen when booting from the install DVD then you will have to remove some RAM to get Vista to install which can be a PITA. I choose to update my install DVD so I would not have to unplug all the cables to my HTPC remove it from the rack then remove the video card remove a stick of RAM reverse the process install Vista take the computer apart agin install the RAM and then put the computer back together.

http://www.coffincruisers.com/gimagex.zip gimagex with the fixed hal.dll version 6.0.6000.16407 http://support.microsoft.com/?kbid=929777

99% of the time I dont have a problem with 4GB of memory installed, but once in a while Ill get a blue screen when booting from the DVD, then I restart and get the same blue screen, so I shutdown pull a stick of ram boot up with with no problem then shutdown put the ram back in boot up agin and no blue screen. WTF? anyways I havent had a problem since I replaced Hal.dll in boot.wim

mount sources\boot.wim image 2 with imagex and replace system32\hal.dll with an updated pre SP1 hal.dll

if you have trouble booting from the USB flash drive try formating to NTFS, My Gigabyte motherboard wont boot from a fat32 usb drive, has to be NTFS also do a quick format or you'll have to wait a loooonnnngggg time. format quick fs=ntfs would be the way togo IMHO.

I just tested this, and boot.wim did not get updated with the new driver. the other option is to update boot.wim the hardway. http://apcmag.com/how_to_inject_drivers_in...ndows_pe_20.htm I just tested the above method, I can see the new driver. but without the hardware I cant test if it will load at boot.