maxXPsoft

I would say No way. Autoit script maybe but that would be a pain getting that right for different resolutions I have been pursuing for such a long time for myself to set list view and make it default for all folders and there is nothing. I've tracked changes to the system probably since xp with every known reg and file tracker and found nothing when those changes are made.

you probably need icacls to grant permissions to you as 'Administrators' with Administrators name in your language I don't think it would be good to do whole WIM folder, try to get the sub folders try instead cmd.exe /c takeown /f "D:\7Work\WIM1\Windows\Resources" /R && icacls "D:\7Work\WIM1\Windows\Resources" /grant Administrators:F /t should see a window with it applying

yep you did miss but only cause you didn't know, it don't count the hidden Recovery partition Gets worse if you unhide that partition and that changes all the rest of your drive letters. I choose not to create it so i can keep my backup drive set as D so all my shortcuts stay intact And as bphlpt stated below you, Installer uses any free drive letter initially so Win 7 install could even be on L drive but after extraction and reboot it changes it to C:\, even with another installed Windows OS which it changes its letter to next available. The boot menu when it starts changes each Win install letter to C You can change that but not worth the headache to me so to sum it all up when Win 7 boots Windows will be on %systemdrive%

It stays on the drive just like the DRV. Could run a cmd during firstlogoncommands to delete it. Nope I don't see how that worked either but it did lay it down on the drive, thats why I said all path would just have to be is %systemdrive%\DRV

You can see it searches for the $WinPEDriver$ PnPIBS: Checking for pre-configured driver paths ... 2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory C:\$WinPEDriver$. Was the folders on the target drive just like that? $OEM$\$1\DRV Reason I ask is I wanted to know if that altiris copied the folders to the drive same way Windows installer does, apparently not cause Windows would have just placed the DRV folder on root

Sure, attach the setupact.log from Windows\$Panther folder on installed system. I gotta see this.

No , just like I said <Path>%systemdrive%\DRV</Path> I do not know if that altiris will use the $OEM$ same way as intended

lots of things changed with Vista and later Using $OEM$ and <Path>%systemdrive%\DRV</Path> so you would place the whatever name you use like this $OEM$\$1\DRV Windows 7 recurses the specified folder so you only need the root folder Only .inf drivers can be added to a Windows image by using this procedure. in other words extracted just like XP was

With Win 7/8 you place the $OEM$ within the sources folder and they are copied to respective locations. lawson23 Glad you finally told me what you are using. When I searched the @ProcessArchitecture it was returning sym,antec links and I wondered why Symantec Puts Altiris Unit on the Block You could use $1\DRV or even $1\$WinPEDriver$ but any boot critical will not be available till the driver setup routine you talk of has run

Are you saying the Drivers do not work? If not you may need to add this <settings pass="generalize"> <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls> </component> </settings> and then do not add any more reference to Driverpaths. Remove from your <settings pass="offlineServicing">

NOPE it probably won't processorArchitecture="@ProcessArchitecture" If your 64 bit then processorArchitecture="amd64" or processorArchitecture="x86" also why change things, use what is given <PathAndCredentials wcm:action="add" wcm:keyValue="1" 1 mistake in an xml and thats it, it will take you down PERIOD Once again the correct way and all you change is processorArchitecture <component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="1"> <Path>$WinPEDriver$</Path> </PathAndCredentials> </DriverPaths> </component>

Create the $WinPEDriver$ on root of DVD like this picture and add the <DriverPaths> to your xml and drop all driver folders within the $WinPEDriver$ folder. This can also be on root of a usb drive where I place the Autounattend.xml. I place xml on a separate usb jump drive so if it gets error I can easily fix in another PC

Win 7 recurses the driver folder if it finds it so need for any other paths The way Win 7 installs the C drive you refer to is not renamed to that till after a reboot. Depending on how many drives you have it could be any letter. People have used configsetroot which tells windows to look on root where the xml is <Path>$WinPEDriver$</Path> by far is easiest if not injecting with folder created like this dvd\$WinPEDriver$

$WinPEDriver$ Windows scans all drives for this folder and uses that if found. It will do this in first pass and is perfect if you also had a boot critical It should be just on the root of any drive like a USB jump drive or the install dvd. D:\$WinPEDriver$. You can see it can have long path names like my picture. I usually inject mine into my image

This is easiest method for Drivers if you don't want to inject them. and yes $OEM$ are still useable even on Win 8

<CreatePartition wcm:action="add"> <Order>1</Order> <Type>Primary</Type> <Extend>true</Extend> </CreatePartition> <Extend> is the key

when PC is booting make sure it loads the uefi part of bios made corrections in WinPE pass try this xml Autounattend.xml

In windows 7 it is simply Control Panel\All Control Panel Items\Backup and Restore Or type sdclt in a cmd prompt or Run box.

On Win 8 in Control Panel there is a 'Windows 7 File Recovery' which was same as Win 7. It did work on 7 but I haven't tested on Win 8.

I tried everything possible, it is no longer loaded from there. The thing Win7BootUpdater updates are C:\Windows\System32\bootres.dll C:\Windows\System32\winload.exe C:\Windows\System32\en-US\winload.exe.mui C:\Windows\System32\winresume.exe C:\Windows\System32\en-US\winresume.exe.mui bootmgr on Hidden partition Use at your own risk though. I have an acronis image I can restore if I have problems There are lots of downloadable files from links in program but I created one of my own. My boot don't get past where the balls join in middle so I don't see the rest so that suits me 2012-12-28_104120.wmv

If you are looking to change boot animation, since SP1 it don't work changing Firstuxres.wim so use coderforlife stuff here http://www.coderforlife.com/projects/win7boot/ I completely redone my Firstuxres.wim like this and didn't work so I am trying with coderforlife link

That was some time ago I done those batch files 2010-03-22, I haven't updated those files for SP1 After they moved my post which was a unattended thing I quit updating that If you're getting a component issue then this is not mod files but rather if you inject IE9 do you know that there are requirements to have about 3 other updates installed prior to inject ????????????????> For Windows 7 Service Pack 1 (SP1), the following prerequisites must be installed: KB2484033, KB2488113, and KB2505438.

Audit is to set things up for all users I guess like an OEM would do with drivers and their Oem programs and such I hadn't tried removing a user but then the things you done with them would Prob be a mess.

Why not go into Audit as the Administrator? <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Description>Enable Admin Account</Description> <Path>net user administrator /active:yes</Path> </RunSynchronousCommand> </RunSynchronous> </component>

cmd /c opens a new command prompt and executes the command given. Theres no waiting or nothing and it will leave a window open as Tripredacus said /c Carries out the command specified by String and then stops. Reason to use the Exit in cmd files /k Carries out the command specified by String and continues. If you want to wait till command finishes this won't work because it will start the command line and then move on to next Start is actually a command by itself but doesn't work as intended so we use the cmd /c Start /wait together. Even this is not perfect for all things, I have had trouble with some Autoit scripts Windows Command Reference still in use even on Windows 8 http://www.microsoft.com/en-us/download/details.aspx?id=2632