Raoul90

I just mount my particular install.wim and drop all the installation files in same folder as setupcomplete.cmd.

Hi, I want to disable the PCA Service. The service handles these screens: And in my FirstLogon script there are a couple of programs that make that screen popup. So I want to disable the service during Windows 7 Setup, if possible? The regkey: I allready had this ones in one of my autounattend.xml files, but I cant find it anymore, I know its possible without creating a .reg and them importing it, should be possible to do it directly from command prompt. Thanks in advance! edit: Think I found it: <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> <Path>cmd /c "cmdow @ /HID & reg add HKLM\SYSTEM\CurrentControlSet\Services\PcaSvc /v Start /t REG_DWORD /d 4 /f</Path> </RunSynchronousCommand> </RunSynchronous> </component>

/////

I allready solved the problem.

Ashampoo Burning Studio 10.0.7 released.

Just put rarreg.key in a sfx: ;SFX-script Path=%systemdrive%\Program Files\WinRAR SavePath Silent=1 Overwrite=1

Ashampoo Burning Studio 10 was released, someone has updated script allready? - no dekstop icon - no myshampoo toolbar - no internet explorer start after install Thanks!

Raoul90, it is saying that you DLed the the 32 bit version of RT7Lite and are trying to install on a 64 bit system. Go back to the RT7Lite site and DL the 64 bit version. The versions have been separated into four, for Vista, W7, 32 and 64 bit. Enjoy, John. ah lol. Thanks

Hmm, I get this msg: But it worked before on x64? huh

Right click .dll, add to archive, click make sfx archive, go to comment tab, add this: ;SFX Path=%systemdrive%\windows SavePath Silent=1 Overwrite=1 Change path to the folder where the .dll you want to override is located.

Yes, I have found a working solution: SetupComplete.cmd: @echo off SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Post Installation" /F REG ADD %KEY%\1/VE /D "Enkele Updates" /f REG ADD %KEY%\1 /V 1 /D "%SYSTEMROOT%\Setup\SCRIPTS\OptionalUpdates.exe" /f REG ADD %KEY%\2/VE /D "DirectX Februari 2010 Redist" /f REG ADD %KEY%\2 /V 1 /D "%SYSTEMROOT%\Setup\SCRIPTS\directx_feb2010_redist.exe" /f REG ADD %KEY%\3/VE /D "Silverlight 4.0.5.0" /f REG ADD %KEY%\3 /V 1 /D "%SYSTEMROOT%\Setup\SCRIPTS\Silverlight4050.exe" /f REG ADD %KEY%\4/VE /D "Register Settings" /f REG ADD %KEY%\4 /V 1 /D "%SYSTEMROOT%\Setup\SCRIPTS\RegisterSettings_reghack.exe" /f REG ADD %KEY%\5/VE /D "MSSE 1.0.1961.0" /f REG ADD %KEY%\5 /V 1 /D "%SYSTEMROOT%\Setup\SCRIPTS\MSSE-NL-v1.0.1961.0-X64-UP2DATE.exe" /f REG ADD %KEY%\6/VE /D "Windows 7 Settings" /f REG ADD %KEY%\6 /V 1 /D "%SYSTEMROOT%\Setup\SCRIPTS\Install.CMD" /f Exit

START /WAIT is a cmd upon itself to do correctly cmd /C START /WAIT and they will close Ah, right! So this will work right? <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>cmd /C start /wait %systemdrive%\APPSX64\MSSE-NL-v1.0.1961.0-X64-UP2DATE.exe</CommandLine> <Description>MSSE</Description> <Order>1</Order> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <CommandLine>cmd /C REGEDIT /S %systemdrive%\APPSX64\RegisterSettings.reg</CommandLine> <Description>RegisterTweaks</Description> <Order>2</Order> </SynchronousCommand> </FirstLogonCommands>

Hmm OK, will give that a try. BTW why this happens: At firstlogon? And it doesnt continue until I shut those cmd prompts manually. FirstLogon.cmd looks like this: @echo off START /WAIT %systemdrive%\APPSX64\MSSE-NL-v1.0.1961.0-X64-UP2DATE.exe REGEDIT /S %systemdrive%\APPSX64\RegisterSettings.reg RD /S /Q %systemdrive%\APPSX64 EXIT

It is working now! But I still want to install from DVD: <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>cmd /c "FOR %%i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) do if exist %%i\sources\install.wim set MEDIA=%%i"</CommandLine> <Description>Setting Path Variable</Description> <Order>1</Order> <RequiresUserInput>false</RequiresUserInput> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <CommandLine>cmd /c REGEDIT /S %MEDIA%\APPSX64\RegisterSettings.reg</CommandLine> <Description>Register Tweaks</Description> <Order>2</Order> <RequiresUserInput>false</RequiresUserInput> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <CommandLine>cmd /c start %MEDIA%\APPSX64\MSSE-NL-v1.0.1961.0-X64-UP2DATE.exe</CommandLine> <Description>MSSE-NL-v1.0.1961.0_64bit</Description> <Order>3</Order> <RequiresUserInput>false</RequiresUserInput> </SynchronousCommand> </FirstLogonCommands> Wont work tho.

OMG, you gotta be kiddin me, will change it, lol.

do you only have 1 image file in your wim file also what what image are you installing with autounattend.xml i,e ultimate or is it enterprise. enterprise fair enough only one image but windows 7 x86 has 5 and x64 has 4. I only use Professional 32 and Professional 64bit. you may only be installing professional but which is install.wim Image Index: 4 in x86 and Image Index: 3 in x64 but when you are modding the image it looks like image number 1 you are mounting which is starter or have you removed all other images. Yes I removed all other images, since I dont need them. Only other thing i can think of are you unmounting the wim file but didn't use commit. I did use comit, and also I tried the $OEM$ folder, both time the APPSX64 folder was present at %SYSTEMDRIVE%, I try to call the .cmd in the APPSX64 folder from autounattend.xml file: <component name="Microsoft-Windows-Shell-Setup" 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"> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>cmd /C start /wait %systemdrive%\APPSX64\FirstLog.cmd</CommandLine> <Description>FirstLogonScript</Description> <Order>1</Order> </SynchronousCommand> </FirstLogonCommands> But it the autounattend file doesnt call the .cmd. I attached my X64 autounattended. autounattend.xml

do you only have 1 image file in your wim file also what what image are you installing with autounattend.xml i,e ultimate or is it enterprise. enterprise fair enough only one image but windows 7 x86 has 5 and x64 has 4. I only use Professional 32 and Professional 64bit. you may only be installing professional but which is install.wim Image Index: 4 in x86 and Image Index: 3 in x64 but when you are modding the image it looks like image number 1 you are mounting which is starter or have you removed all other images. Yes I removed all other images, since I dont need them.

do you only have 1 image file in your wim file also what what image are you installing with autounattend.xml i,e ultimate or is it enterprise. enterprise fair enough only one image but windows 7 x86 has 5 and x64 has 4. I only use Professional 32 and Professional 64bit.

Allright, I did another tests and as expected it aint working again.

Yes, $1 represents the system volume (the one Windows is installed to), which is of course usually C: on a clean install unless you've changed the drive letter with autounattend. That means that during installation (near the end, after the WIM has been laid down onto the disk) the contents of $OEM$\$1 will be copied to the system volume as their folder names - so for example, you would see this folder post-install as %systemdrive%\APPSX86. Yeah, lol I know about the $OEM$ folders and structures, same as with XP. But what I meant was, I mounted the image, and copied the appsx86 folder to the %MOUNT% folder, which is the same as %systemdrive% after install, since the appsx86 was present @ %SYSTEMDRIVE% after installation. edit: The APPSX64 folder was between those when I mounted wim and copied folder!

APPSX86 directory is present after installation? But if you say I should use $OEM$ then I will give that a try..

I mounted image and copied the APPSX86 folder to the systemdrive.

Lol at this code boxes. Anyways, it aint working, I am getting kinda frustrated now, since I have no idea on how to install the applications otherwise? @ maxXPsoft What switches do you use after the attrib?

Allright, I have time to test again, so I will basically test this now: X86: @echo off REGEDIT /S %systemdrive%\APPSX86\RegisterSettings.reg Start /Wait %systemdrive%\APPSX86\MSSE-NL-v1.0.1961.0-X86-UP2DATE.exe RD /S /Q %systemdrive%\APPSX86 EXIT X64: @echo off REGEDIT /S %systemdrive%\APPSX64\RegisterSettings.reg Start /Wait %systemdrive%\APPSX64\MSSE-NL-v1.0.1961.0-X64-UP2DATE.exe RD /S /Q %systemdrive%\APPSX64 EXIT Called from FirstLogonCommands in autounattend.xml: <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>cmd /C start /wait %systemdrive%\APPSX86\FirstLog.cmd</CommandLine> <Description>FirstLogonScript</Description> <Order>1</Order> </SynchronousCommand> </FirstLogonCommands> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>cmd /C start /wait %systemdrive%\APPSX64\FirstLog.cmd</CommandLine> <Description>FirstLogonScript</Description> <Order>1</Order> </SynchronousCommand> </FirstLogonCommands> Hope it works!

AH! Thanks dude, it works again! !!