myselfidem

Thanks. Enjoy

Select correctly the ImageX.exe and DISM.exe paths! However, I don't know if you can use 7Customizer with an upgrade Windows 7 Home version x86/x64 ! Try to use the correct paths and let us know! Cheers

Check if you can use: BlueScreenView v1.45 - View BSOD (blue screen) crash information stored in dump files http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/

I found on a french forum a guy solving the problem removing and replacing the memory modules (RAM)! And after Windows start fine...But of course you need to remove the bad driver. http://www.inforumatique.fr/forum/ecran-bleu-physical-memory-dump-t9529.html

I see Windows may start only if you see at the bottom of the BSOD an increasing number (like 60-90-120) and the computer restart and Windows boot! Happens to me many times with Windows XP. Maybe that can help you also:

You can try to start your computer and if you see the BSOD, just wait and after some time Windows may start! Which OS do you have installed? Tool to repair (not tested): Fix Blue Screen Of Death in 2 Minutes Resolving stop (blue screen) errors in Windows 7

Maybe you can find useful infos here: AMD Catalyst™ Software Suite Version 12.6 Release Notes Check if you need NET Framework SP1 for your OS! Maybe you need to uinstall ATI 12.6 with Safe mode and install the working ATI previous version.

You can update WPI v8.5.2 to get the new release WPI v8.5.3. Regards

Thanks for the new Manual! Just needed to change the path to download the "Sources.rar" folder with SetupComplete.cmd included: http://www.msfn.org/...ost__p__1005981 Regards

Inside the new Manual for WPI it's needed to change the path to download the file "Sources.rar" with the SetupComplete.cmd included: Inside: Manual\en\ Chapiter-10.html\line 53: 1 = Download this <a href="http://www.wpiw.net/downloads/Sources.rar">Pre-configured sources\setupcomplete.cmd archive.</a> "Click-able link!"<br /> Just needed to change: "sources.rar" to "Sources.rar" http://www.msfn.org/...post__p__980388 Regards *Edit: Thanks to move this post, because it's not inside the right topic!

Maybe you can try this one. I made some changes.

You can try to add inside your Autounattend.xml file, these lines and adapt to your needs: <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UserData> <Organization>TEST</Organization> <FullName>test</FullName> <AcceptEula>true</AcceptEula> </UserData> <DiskConfiguration> <WillShowUI>OnError</WillShowUI> <Disk wcm:action="add"> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Type>Primary</Type> <Size>100</Size> </CreatePartition> <CreatePartition wcm:action="add"> <Order>2</Order> <Type>Primary</Type> <Extend>true</Extend> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Format>NTFS</Format> <Label>system</Label> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> <ModifyPartition wcm:action="add"> <Format>NTFS</Format> <Label>Main</Label> <Letter>C</Letter> <Order>2</Order> <PartitionID>2</PartitionID> </ModifyPartition> </ModifyPartitions> </Disk> </DiskConfiguration> <ImageInstall> <OSImage> <InstallFrom> <MetaData wcm:action="add"> <Key>/IMAGE/NAME</Key> <Value>Windows 7 ULTIMATE</Value> </MetaData> </InstallFrom> <InstallTo> <DiskID>0</DiskID> <PartitionID>2</PartitionID> </InstallTo> <WillShowUI>OnError</WillShowUI> <InstallToAvailablePartition>false</InstallToAvailablePartition> </OSImage> </ImageInstall> </component> </settings>

Many thanks! Works fine now. Regards

We can't get the new update with WPI v8.5 to WPI v8.5.2 but it is possible with WPI v8.1.0 Regards

Where could we download more themes? The link is dead: http://www.msfn.org/...post__p__998611 Thanks in advance. Regards *Edit: The corrrect path is: (just needed to change the first letter t to T for Themes) http://www.wpiw.net/...ds/Themes_1.rar Do the same for PNG_Collection.rar to png_Collection.rar for the correct path: http://www.wpiw.net/downloads/png_Collection.rar Thanks, I found the repository! http://www.wpiw.net/downloads/ Regards

@adrien426 *Edit: Answer removed ! However be careful because you are using a warez : http://www.msfn.org/...ost__p__1004538 You can get the Windows 7 SP1 original iso here. straight from MS http://www.msfn.org/...post__p__973012

As johnhc suggested, attach your full answer file, please! Cheers

Answer removed see below post for reasn ~~~ KEL ~~~

If you don't find your language inside the folder Lang, you can use Google translator! Cheers

Yes, the integrated updates will be visible! Enjoy

And the feature with the selected option will be saved inside "useroptions.js" // WPI Options 8.1.0 // // User defined options // // Features tab ShowCommandInInstaller=false; Enjoy!

Yep! Always check the correct path (example): cmds[pn]=['msiexec.exe /i "%wpipath%\\Install\\AdobeReaderX\\AcroRead.msi" /qb TRANSFORMS=AcroRead.mst REBOOT="ReallySuppress" /f']; Cheers

SetupComplete.cmd: Add a Custom Script to Windows Setup SynchronousCommand: <FirstLogonCommands> with <SynchronousCommand wcm:action="add"> Regards

Don't worry... It was interesting to see the problem about regedit.exe 32-bit and regedit.exe 64-bit using {REGEDIT} with WPI in the context of Windows 7 AIO ! Regards *Edit-1: However it's strange because we can read: C:\windows\sysWOW64\regedit.exe- Can someone explain to me what this might be? Registry Keys Affected by WOW64 It seems using for Windows 7 x64 with WPI: REGEDIT /S the regedit.exe 64-bit is used (%Windir%\regedit.exe) And using {REGEDIT} the regedit.exe 32-bit is executed (%Windir%\SysWOW64\regedit.exe) and keys are redirected. *Edit-2: However works also fine using {REGEDIT}: config.js WPI_Log.txt Windows 7 x64 WPI_Log.txt Windows 7 x86

Many thanks ! But I'll have repeatedly suggested to use: REGEDIT /S as a workaround for Windows 7 x64: http://www.msfn.org/board/topic/157072-help-importing-reg-file-please/page__view__findpost__p__1001560 http://www.msfn.org/...ost__p__1002143 http://www.msfn.org/...ost__p__1002192 I haven't seen the problem about using regedit.exe 64-bit with {REGEDIT} for HKLM 32-bit keys on Windows 7 x64! I'm happy the problem is solved! Regards