Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations


About dcolpitts

dcolpitts's Achievements



  1. I've been started searching for this exact same thing for a couple of days now for DaRT 8.1 x64. I want to completely bypass the keyboard layout screen, or at the very least only show "US". But no luck so far. I though maybe if I added the follow three commands to winpeshl.ini in front of recenv.exe that it might do it, but I guess not: %systemdrive%\windows\system32\wpeutil.exe SetKeyboardLayout 0409:00000409%systemdrive%\windows\system32\wpeutil.exe SetMuiLanguage en-US%systemdrive%\windows\system32\wpeutil.exe SetUserLocale en-USLet me know if you ever figure it out. dcc
  2. I'm not sure about previous versions, but 0.2.5 does not handle spaces in the path name to the source (ie C:\SHARED\ISO IMAGES\WINDOWS7\x86\en_windows_7_ultimate_x86_dvd_x15-65921 where en_windows_7_ultimate_x86_dvd_x15-65921 is the extracted ISO image). Log Output: dism result end. added: "C:\Program Files\Windows AIK\Tools\x86\imagex.exe" /XML /info "C:\SHARED\ISO IMAGES\WINDOWS7\x86\en_windows_7_ultimate_x86_dvd_x15-65921\sources\install.wim">work\imagesinfo.xml Starting imagex Imagex created imagesinfo.xml Successfully Reading images information from imagesinfo.xml First 5 lines of imagesinfo.xml Error opening file [C:\SHARED\ISO]. Moving en_windows_7_ultimate_x86_dvd_x15-65921 to c:\SHARED\en_windows_7_ultimate_x86_dvd_x15-65921 works fine as does renaming "ISO IMAGES" to "ISO_IMAGES" dcc
  3. Interesting app you have here... I'd like to see two additional elements added it to. First is disk partitioning, and second is join domain/workgroup (and the necessary credentials for the user that has join domain rights). Add those, and you'd have a pretty darn good app that would do probably about 95% of what System Admins require the overly complex WAIK for. dcc
  4. I've ran into an issue doing a cross-platform install of Windows 7 x64 Enterprise from a 32bit PE (actually it's BartPE/XPE). Basically, I pre-partition the HDD prior to launching setup (so I don't end up with the 100MB reserved service partition), then I run the following command: \\server\win7ent_x86_setup\setup.exe /installfrom:\\server\win7ent_x64_setup\sources\install.wim /unattend:\\server\setup\unattend.xml I've mounted both the x86 and x64 iso images on the server, and shared them as win7ent_xYY_setup, so the entire DVDs are available to setup.exe. So setup takes off and runs basically the entire initial file copy and just prior to the first reboot sequence, I get a pop-up: setup.exe - Bad Image The application or DLL C:\Windows\System32\en-US\bootstr.dll.mui is not a valid Windows image. Please check this against your installation diskette. If I click OK it, then I immediately get: setup.exe - Bad Image The application or DLL C:\Windows\System32\bootstr.dll is not a valid Windows image. Please check this against your installation diskette. If I click on that, then the installation carries on its merry way and finishes, then reboots into Windows 7 x64. Now - I can understand why setup.exe thinks those are bad images - obviously those are the 64bit versions of the files. But the question is, why is setup.exe attempting to open them, and secondly, how do I avoid this from happening, because it is not really an unattended installation if you have to click OK twice in the middle of it. dcc
  5. If you have selected the option to show publish dates, show those publish dates on the during the download.

  • Create New...