Jump to content

myselfidem

Member
  • Posts

    2,515
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Switzerland

Everything posted by myselfidem

  1. You can try to launch WPI.exe with Autounattend.xml and without a new batch file (WPI.cmd). Add inside your Autounattend.xml: <settings pass="oobeSystem"> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>cmd /c for %i in (C 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:\wpi\wpi.exe start %i:\wpi\wpi.exe</CommandLine> <Description>Windows Post Install Wizard</Description> <Order>9</Order> <RequiresUserInput>false</RequiresUserInput> </SynchronousCommand> </FirstLogonCommands> Check your Autounattend.xml file with Windows System Image Manager (WSIM) include with WAIK for Windows 7. Check if inside your SetupComplete.cmd you have write EXIT at the end!
  2. You can use an other batch file to launch WPI, like WPI.cmd inside the folder SCRIPTS. And add a command inside your Autounattend.xml pointing to this batch file. See the description here (at the end): RT Seven Lite - RC build 1.7.0 and Beta build 2.6.0 Cheers
  3. It's possible to create an ISO file Windows 7 64-bits on a computer running 32-bits! If you want use 7Customizer you need to choose the Architecture x86 to do that! You can also do manually or use others programs like RT Se7en Lite or Se7en_UA. Note 1 : But the problem is when you want test your image ISO; Oracle VM VirtualBox display an error, because your computer is Architecture 32-bit an not 64-bit! Note 2 : The test on a computer 64-bit with the virtual Machine works fine an the test is successful, because I can choose Windows 7 64-bit! I don't know if you can do the test with WMware on a computer x86!? The error displayed is on the Virtual Machine with a computer 32-bit: Windows Failed to start File: \windows\system32\boot\winload.exe Status: 0xc000035a Info: Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode.
  4. I use GIMP 2.6 because it' is a freeware and works fine! I don't have Photoshop. The channel is important because if you save the image 32-bits with channel X8 R8 G8 B8 the image will not be displayed!!! About the Manifest: You can read the description when you want add the Manifest file: Yes, I think you can change the: processorArchitecture="amd64" inside the Manifest. The file with processorArchitecture="x86" works also on a 64-bits computer and I've tried! You can download the tutorial for Restorator 2007: Manual Cheers *Edit: for the XP Manifest you can use an asterisk (star= *) processorArchitecture="*"
  5. Many thanks Glimmerman! If you want customize the source 516 you can use GIMP. More help: Installers for GIMP for Windows Gimp on Wikipedia 1) At first open spwizimg.dll with Restorator 2007 and save the source 516. 2) Lauch GIMP and open the source 516 saved. 3) Drag and drop an image you want add inside the source 516 and customize this one like you want (colors, size,..). 4) Save this new customized source 516 inside an other folder with the same name, color 32-bits and channel A8 R8 G8 B8 (use Advanced options), .bmp format. Now you can add this new source 516 inside your customized spwizimg.dll with Restorator 2007. You can also add a Manifest (XML file) with Restorator inside spwizimg.dll to improve the installation (you can see that inside the spwizimg.dll I've given you)! Cheers
  6. It seems that the process are not the same with Autounattend.xml and without using the xml file! In fact I have the same trouble like you! I've found an workaround and I've modded the source 516 with your image. I've spend time but I think now it's OK. If you want try the spwizimg.dll I've made you can download here, I've tested with Autounattend.xml and without!: spwizimg.zip No there is not spwizimg.dll inside boot.wim 1! I hope that can help you!
  7. Could you please send as attachment your spwizimg.dll, and I will take a look ? You can try my spwizimg.dll (64-bits) customized like the example above, here: 7background_X64_French_dlls.rar But I'm not sure that will working with your localized Windows version! You can also extract the source 516, but I've just add one image inside! I think that the trouble is with the source 518. It seems that with Autounattend.xml the boot.wim 1 is loaded and without this is the boot.wim 2 (customized) which is loaded!? You can try the new RT Seven Lite 1.7.0 RC! Thanks *Edit: You can also use RT Se7en Lite to integrate your customized spwizimg.dll !
  8. Thanks! I think it works even if you don't set the output location! You can use search to see where is the new file! Cheers
  9. Weird! When I use the command inside Start | Run C:\Windows\system32\makecab.exe C:\LogonUI.exe C:\LogonUI.ex_ All is fine! Just specify the output path (location). You can also add inside your registry this reg file (output inside the same folder): REGEDIT4 ; Add command Expand and Makecab on right-click [HKEY_CLASSES_ROOT\*\shell\Expandit\command] @="expand -r \"%1\"" [HKEY_CLASSES_ROOT\*\shell\MAKECAB\command] @="\"makecab.exe\" \"%1\""
  10. Because I think that something is missing! I've the same customized images with an unattended installation (Autounattend.xml) or manual installation, even if I choose French installation or English installation. You can check your Autounattend.xml with WSIM include with WAIK for Windows 7. Which program are you using to customize dll's files? Restorator 2007? *Edit: Check if all spwizimg.dll (with source 518 and source 516 customized) customized have been replaced inside your distribution folder (boot.wim 2 and install.wim 4 and inside %DVD%\sources\spwizimg.dll)! Inside your Autounattend.xml you need to set the correct IMAGE/INDEX If you have all the images. For you is <Value>4</Value> for Windows 7 Ultimate 64-bits. <InstallFrom> <MetaData wcm:action="add"> <Value>1</Value> <Key>/IMAGE/INDEX</Key> </MetaData> </InstallFrom> You can also use: <InstallFrom> <MetaData wcm:action="add"> <Key>/IMAGE/NAME</Key> <Value>Windows 7 ULTIMATE</Value> </MetaData> </InstallFrom> Unattended Windows Setup Reference for Windows 7.chm
  11. I think you need to copy the originals folders boot.wim and install.wim inside your distribution folder (Example C:Win7), and delete the others one. First integrate the Dutch language pack like my example above (boot.wim and install.wim). Do not integrate updates now. The updates must be integrated after! Try with the Virtual Machine first without unattend file! I hope that will help you! Add a Package to a Windows PE Image Check the Autounattend.xml (yours amd64): Delete this line: I've misunderstood the language pack needed for you! You want add Dutch and not German. Sorry!!! I've updated my last post for Dutch language! The batch file works fine but you need to adapt to your needs
  12. I've also found help here: HowTo : create a multi language Windows 7 or Windows 2008 R2 server DVD installer. The language for boot.wim is on the WAIK for Windows 7 DVD ; insert this one on your drive CD\DVD (E:\ with this example). Addapt the path and the batch file to your needs. I've created a batch file to automate the process for adding the language pack (nl-nl) inside boot.wim 2 and install.wim 4 WAIK must be installed on your computer! Add_Language-nl-NL.cmd @echo off REM Integrate Dutch language inside the source folder for Windows 7 Ultimate amd64 boot.wim 2 et install.wim 4 REM Copy your DVD Windows 7 - Whithout updates integrated - on your patition C:\ REM Language Pack Dutch on C:\Lang REM Creates a temp folder "C:\Mount" echo. "C:\Program Files\Windows AIK\Tools\amd64\Servicing\Dism.exe" /Mount-Wim /WimFile:"C:\Win_new\sources\boot.wim" /index:2 /MountDir:"C:\Mount" echo. "C:\Program Files\Windows AIK\Tools\amd64\Servicing\Dism.exe" /Image:"C:\Mount" /Add-Package /PackagePath:E:\WinPE_LangPacks\amd64\nl-nl\lp.cab "C:\Program Files\Windows AIK\Tools\amd64\Servicing\Dism.exe" /Image:"C:\Mount" /Add-Package /PackagePath:E:\WinPE_LangPacks\amd64\nl-nl\winpe-setup_nl-nl.cab "C:\Program Files\Windows AIK\Tools\amd64\Servicing\Dism.exe" /Image:"C:\Mount" /Add-Package /PackagePath:E:\WinPE_LangPacks\amd64\nl-nl\winpe-setup-client_nl-nl.cab "C:\Program Files\Windows AIK\Tools\amd64\Servicing\Dism.exe" /Image:"C:\Mount" /Add-Package /PackagePath:E:\WinPE_LangPacks\amd64\nl-nl\winpe-scripting_nl-nl.cab "C:\Program Files\Windows AIK\Tools\amd64\Servicing\Dism.exe" /Image:"C:\Mount" /Add-Package /PackagePath:E:\WinPE_LangPacks\amd64\nl-nl\winpe-srt_nl-nl.cab "C:\Program Files\Windows AIK\Tools\amd64\Servicing\Dism.exe" /Image:"C:\Mount" /Add-Package /PackagePath:E:\WinPE_LangPacks\amd64\nl-nl\winpe-wds-tools_nl-nl.cab "C:\Program Files\Windows AIK\Tools\amd64\Servicing\Dism.exe" /Image:"C:\Mount" /Add-Package /PackagePath:E:\WinPE_LangPacks\amd64\nl-nl\winpe-wmi_nl-nl.cab echo. "C:\Program Files\Windows AIK\Tools\amd64\Servicing\Dism.exe" /Image:"C:\Mount" /Gen-LangINI /distribution:"C:\Mount" echo. "C:\Program Files\Windows AIK\Tools\amd64\Servicing\Dism.exe" /Unmount-WIM /MountDir:"C:\Mount" /Commit echo. "C:\Program Files\Windows AIK\Tools\amd64\Servicing\Dism.exe" /Mount-Wim /WimFile:"C:\Win_new\sources\install.wim" /index:4 /MountDir:"C:\Mount" "C:\Program Files\Windows AIK\Tools\amd64\Servicing\Dism.exe" /Image:"C:\Mount" /Add-Package /PackagePath:"C:\Lang\windows6.1-kb972813-amd64-nl-nl.cab" "C:\Program Files\Windows AIK\Tools\amd64\Servicing\Dism.exe" /Unmount-WIM /MountDir:"C:\Mount" /Commit echo. "C:\Program Files\Windows AIK\Tools\amd64\oscdimg.exe" -u2 -m -o -lWin_new -b"C:\Win_new\boot\etfsboot.com" "C:\Win_new" "C:\Win_new.iso" echo. echo ==End process== echo. pause I've tested for me successfuly (Windows 7 Ultimate x86 French version with English added)!
  13. If you integrate a language pack inside boot.wim and install.wim you can use this language for the installation: Example for Windows 7 Ultimate x86: boot.wim 2 and install.wim 5; or install.wim 1 and boot.wim 1 if only one image is saved! With my localized French version with English integrated I can do the installation in English. Walkthrough: Add Multilingual Support to Windows Setup Understanding Multilingual Deployments
  14. When you customize the spwizimg.dll (or others .dll's files) be carefull to save your new file inside an other folder and AFTER change the original one (need to take ownership), otherwise your modifications are lost! Add and Remove Language Packs Offline For me, I've created at first a Windows 7 Ultimate x86 with dll's modded (spwizimg.dll, imageres.dll, etc.) and working fine. And I use this new DVD to add after language pack en-US, updates, drivers, etc. *EDIT: Walkthrough: Add Multilingual Support to Windows Setup With my French localised version Windows 7 Ultimate x86, I can install with English after I've integrated this language (inside boot.wim 2 and install.wim 5)!
  15. You can check the image 518 Mount install.wim 4 and boot.wim 2 inside boot.wim 2 : C:\Temp folder\sources\spwizimg.dll\518 inside install.wim 4 : C:\Temp folder\Windows\System32\spwizimg.dll\518 inside C:\%DVD%\sources\spwizimg.dll\518 Look also inside Windows\SysWOW64\spwizimg.dll\518
  16. I think you need to integrate the correct language pack (Dutch x64): Windows 7 MUI language packs Understanding Multilingual Deployments
  17. Thanks! Sometimes I see that I choose 120 seconds before the desktop finish loading the first time , but when WPI starts, I see that I've lost some seconds. Remaining seconds: 57 I don't use SetupComplete.cmd but WPI.cmd (inside the folder "scripts") launched with Autounattend.xml at Firstlogon. WPI starts immediatly for you?
  18. Works fine for me and tested. Take care with the path!
  19. Silent switches for picpick_inst.exe are: start /Wait C:\picpick_inst.exe /S /D=C:\"Program Files"\PicPick
  20. You can check inside your useroptions.js if the values are always defined. Example inside mine useroptions.js:
  21. You can try to make an ISO file with RT Se7en Lite only with your drivers needed and integrate the updates. Perhaps there exists a conflict with some drivers! *Edit: there is many updates KB947821 Catalogue Microsoft Update *EDIT: Download the updates for Windows 7 here: Catalogue Microsoft®Update
  22. You can add this reg file: Enable Task_Manager.reg Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System] "DisableTaskMgr"=dword:00000000
  23. I've found some informations here: Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2 "0x80070490" error code
  24. First thing, I can see inside your setupact.log: [quote ]---- DiskSpaceReqs: Windows image size (from metadata) = [15551918882] bytes 2010-12-13 20:40:38, Info [0x0601bb] IBS DiskSpaceReqs: Windows image size (after padding) = [17643981682] bytes 2010-12-13 20:40:38, Info IBS DiskSpaceReqs: Windows image contents: [17643981682] bytes 2010-12-13 20:40:38, Info IBS DiskSpaceReqs: ~BT volume (estimate): [0] bytes 2010-12-13 20:40:38, Info IBS DiskSpaceReqs: Install volume (estimate): [17643981682] bytes 2010-12-13 20:40:38, Info IBS DiskSpaceReqs: ~LS volume (estimate w/o padding): [0] bytes 2010-12-13 20:40:38, Info IBS CalculatingRecommendedSpaceForWindows: RequiredSize [17643981682] bytes 2010-12-13 20:40:38, Info IBS CalculatingRecommendedSpaceForWindows: Recommending [21610728306] bytes 2010-12-13 20:40:38, Info IBS Callback_ValidateInstallDrive:Install volume -- required free space = [17643981682] bytes 2010-12-13 20:40:38, Info IBS Callback_ValidateInstallDrive:Install volume -- recommended free space = [21610728306] bytes 2010-12-13 20:40:38, Info IBS Callback_ValidateInstallDrive:Summary - CCP check passed; able to calculate space reqs; able to find install location; location type meets installation reqs; size of location IS too small; location free space is NOT enough; location free space does NOT meet the recommendation---- And you have many updates not installed:
  25. Look inside %Windir%\Panther\setupact.log Example inside my setupact.log:
×
×
  • Create New...