Metzen

Member
  • Content count

    137
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Metzen

  • Birthday 12/20/1982

Contact Methods

  • Website URL
    http://
  1. Not true. A smaller file size can help speed up PXE booting over a slow link. Sometimes I have to work with a link that takes ~30mins to boot WinPE over PXE. Any reduction is a huge boon! In addition, a smaller boot.sdi will kick off downloading the WIM faster as well.
  2. Just change the registry key for wpeinit to cmd.exe. Copy procmon.exe to your WinPE image and launch procmon and set it to record registry and file monitoring. Then launch Wpeinit. That will usually point you to the culprit. I know with our HP servers it was really slow because of hardware enumeration. The amount of device ID's in the servers I was using just dwarfed your average desktop. I think it had some ~200 device ID's. This was a Proliant G5 370 (IIRC). If you install devcon.exe into your WinPE image you can verify that too.
  3. Just make a script that does the following... Imagex.exe /mountrw %PATH_TO_YOUR_SOURCE% C:\mount %UPDATE_KB123456%.EXE /update C:\mount\$WIN_NT$.~LS Or just update the source and remake the WIM from a virtual machine. As always, you trade speed for complexity. You can use WinPE 2005 instead. Then you won't have to use bootsect.exe but this thread asked about PE2.1. You run winnt32.exe /switches, wait for it to finsih, then your back to your WinPE command-prompt. Now use ImageX.exe. Microsoft has actually been recommending it to be done like that since NT. The changes to this tech article is that instead of installing the drive into a another computer, we're taking an image of that drive and then applying that image to another computer. Just grab it out of the WinPE image. I believe that version works on XP. Or install the WAIK or the Windows OPK. They all contain ImageX among some other tools. You don't need to use ImageX. Ghost will work as well. The flexibility of being able to access the filesystem after applying with ImageX is nice though. We use a script that detects what type of machine you have and then it will copy over the appropriate OEMBIOS.BIN, OEMBIOS.SIG, OEMBIOS.CAT, etc. after applying the image. We also use a script before applying the ImageX that asks a series of questions (eg What role does this machine have? X,Y or Z?) then takes those answers and modifies the hard drive afterwards (ie, copies over certain programs and sets them to auto-install, changes the unattend.txt [which is actually WINNT.SIF at this stage] for certain computer names, copies over appropriate drivers for $OEM$, etc.). In this way, we actually modularize our install. We have the "base" which is kept pure, then a scripted layer for things that can't be auto-detected (ie, what role does the machine play?), and then add scripted layers on top which run silently. This allows us to completely image a machine in about ~15 minutes from WinPE boot to desktop. Naturally, this didn't occur overnight but took about 5 years of evolution starting with WinPE from XPSP1. Though, I think I could implement a solution that matches it in functionality in about a week if I had to start from scratch.
  4. Use Winnt32 and "install" the OS onto the drive but don't reboot. Your harddisk should now be ready for text-mode setup so it's still hardware agnostic. Now using ImageX make an image of the drive back to the network. Now change your flow like so: 1 Initializes net 2 network share 3 creates partitions/formats/bootsector 4 run imagex and restore the image. If you wanted, what we would do is on step 3 we'd create two partitions, a 2GB one and one for the rest of the system. We'd copy the imagex image to the 2GB partition and expand it into the bigger partition. Then we'd use diskpart to delete the 2GB partition and expand the big partition to consume the smaller one. I think you need to re-bootsect after doing so. This would make installs lickty split quick as copying over a single large file over a network is consistently faster than lots of individual files. And copying to a HDD and expanding from there is even faster than trying to expand over the network (which is essentially reading a bunch of small files). The advantage of the imagex image is you can mount the image and manipulate files without having to rebuild the whole thing from PE + winnt32. Adding additional drivers to $OEM$, editing the TXTSETUP.SIF files became a piece of cake.
  5. Please check out this thread for an answer: http://www.msfn.org/board/WinPE_SRT_Package_t104854.html
  6. Since the WinPE SRT package was removed from the RTM build, but I still want it fully operational in my WinPE, I've had to figure out what keys worked and what files are needed. These are my findings: Files required: \Windows\System32 \Windows\System32\bmrui.exe \Windows\System32\MdSched.exe \Windows\System32\rstrui.exe \Windows\System32\spp.dll \Windows\System32\srcore.dll \Program Files\Common Files \Program Files\Internet Explorer \Program Files\Common Files\microsoft shared \Program Files\Common Files\System \Program Files\Common Files\microsoft shared\ink \Program Files\Common Files\microsoft shared\Triedit \Program Files\Common Files\microsoft shared\ink\ar-SA \Program Files\Common Files\microsoft shared\ink\bg-BG \Program Files\Common Files\microsoft shared\ink\cs-CZ \Program Files\Common Files\microsoft shared\ink\da-DK \Program Files\Common Files\microsoft shared\ink\de-DE \Program Files\Common Files\microsoft shared\ink\el-GR \Program Files\Common Files\microsoft shared\ink\en-US \Program Files\Common Files\microsoft shared\ink\es-ES \Program Files\Common Files\microsoft shared\ink\et-EE \Program Files\Common Files\microsoft shared\ink\fi-FI \Program Files\Common Files\microsoft shared\ink\fr-FR \Program Files\Common Files\microsoft shared\ink\he-IL \Program Files\Common Files\microsoft shared\ink\hr-HR \Program Files\Common Files\microsoft shared\ink\hu-HU \Program Files\Common Files\microsoft shared\ink\it-IT \Program Files\Common Files\microsoft shared\ink\ja-JP \Program Files\Common Files\microsoft shared\ink\ko-KR \Program Files\Common Files\microsoft shared\ink\lt-LT \Program Files\Common Files\microsoft shared\ink\lv-LV \Program Files\Common Files\microsoft shared\ink\nb-NO \Program Files\Common Files\microsoft shared\ink\nl-NL \Program Files\Common Files\microsoft shared\ink\pl-PL \Program Files\Common Files\microsoft shared\ink\pt-BR \Program Files\Common Files\microsoft shared\ink\pt-PT \Program Files\Common Files\microsoft shared\ink\ro-RO \Program Files\Common Files\microsoft shared\ink\ru-RU \Program Files\Common Files\microsoft shared\ink\sk-SK \Program Files\Common Files\microsoft shared\ink\sl-SI \Program Files\Common Files\microsoft shared\ink\sr-Latn-CS \Program Files\Common Files\microsoft shared\ink\sv-SE \Program Files\Common Files\microsoft shared\ink\th-TH \Program Files\Common Files\microsoft shared\ink\tr-TR \Program Files\Common Files\microsoft shared\ink\uk-UA \Program Files\Common Files\microsoft shared\ink\zh-CN \Program Files\Common Files\microsoft shared\ink\zh-TW \Program Files\Common Files\microsoft shared\ink\ar-SA\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\bg-BG\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\cs-CZ\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\da-DK\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\de-DE\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\el-GR\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\en-US\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\es-ES\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\et-EE\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\fi-FI\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\fr-FR\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\he-IL\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\hr-HR\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\hu-HU\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\it-IT\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\ja-JP\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\ko-KR\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\lt-LT\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\lv-LV\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\nb-NO\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\nl-NL\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\pl-PL\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\pt-BR\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\pt-PT\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\ro-RO\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\ru-RU\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\sk-SK\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\sl-SI\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\sr-Latn-CS\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\sv-SE\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\th-TH\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\tr-TR\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\uk-UA\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\zh-CN\tipresx.dll.mui \Program Files\Common Files\microsoft shared\ink\zh-TW\tipresx.dll.mui \Program Files\Common Files\microsoft shared\Triedit\en-US \Program Files\Common Files\System\ado \Program Files\Common Files\System\msadc \Program Files\Common Files\System\Ole DB \Program Files\Common Files\System\ado\en-US \Program Files\Common Files\System\msadc\en-US \Program Files\Common Files\System\Ole DB\en-US \Program Files\Internet Explorer\sqmapi.dll \sources\en-US \sources\recovery \sources\recovery\en-US \sources\recovery\PssWiz.exe \sources\recovery\RecEnv.exe \sources\recovery\StartRep.exe \sources\recovery\en-US\PssWiz.exe.mui \sources\recovery\en-US\RecEnv.exe.mui \sources\recovery\en-US\StartRep.exe.mui And then attached is the registry keys required. I didn't filter every single registry key that is essential, I just did a diff of the Vista PE with the WinRE environment to the registry keys of a WinPE without one. You'll need to mount your registry hive as PE_SOFTWARE for the Software hive and PE_SYSTEM for the System hive. DIFF.zip
  7. Digging into the registry I found this was because of 1 registry key. It's located here: [HKEY_LOCAL_MACHINE\pe_software\Microsoft\Windows NT\CurrentVersion\WinPE] "PrepStatus"=dword:00000001 [b]"InstRoot"="X:\\$Windows.~BT\\"[/b] What is needed is to change InstRoot to the directory below your Windows directory. So, to enable this to work you'll need to set InstRoot=X:\ Why does Microsoft do this? So you can use a WinPE install off a harddisk with all the associated expanded files as oppoesd to a large WinPE image. At least, that's what I've figured
  8. Theme files no longer retain or change My Computer and My Network icons...
  9. This happens when you have a product key different from your captured image in your Unattend.xml file. So, if you capture a Ultimate image and your Unattend.xml file has a Home Premium key you'll get that result. This can be verified by removing the product key entry in your answer file and then doing the restore and "skipping" the entry of the product key. You'll find it'll work successfully.
  10. 1) Configures your WinPE environment as specified through winbom.ini (or via it's own defaults, ie, add network support). 2) If the winbom specifies the configset, Lang, etc., copy over all files necessary to run setup 3) launch winnt32 to finish staging files. What running winnt32 does (without factory -winpe): 1) Requires that you have access to local Windows setup files (either staged on CD/HDD or network share) 2) Stages the files and starts setup. Essentially, factory -winpe was supposed to make it easy for you to image home or pro via a single file. All it accomplishes is copying over the i386 folder (and components if staged correctly) to your local drive (again, specified in winbom.ini) and launches the winnt32.exe file.
  11. I found that setup.exe has a /noreboot switch. So, setup.exe /unattend:s:\xml\basic.xml /noreboot will remove the reboot.
  12. BOOTSECT.EXE is a tool available in the OPK/WAIK which does the FIXMBR thingy. MS made it to enable switching between NT5 boot sector and NT6. It's attached. bootsect {/help|/nt60|/nt52} {SYS|ALL|<DriveLetter> [/force] Boot sector restoration tool Bootsect.exe updates the master boot code for hard disk partitions in order to switch between BOOTMGR and NTLDR. You can use this tool to restore the boot sector on your computer. /help Displays these usage instructions. /nt52 Applies the master boot code that is compatible with NTLDR to SYS, ALL, or <DriveLetter>. The operating system installed on SYS, ALL, or <DriveLetter> must be older than Windows Vista. /nt60 Applies the master boot code that is compatible with BOOTMGR to SYS, ALL, or <DriveLetter>. The operating system installed on SYS, ALL, or <DriveLetter> must be Windows Vista or WindowsServer "Longhorn". SYS Updates the master boot code on the system partition used to boot Windows. ALL Updates the master boot code on all partitions. ALL does not necessarily update the boot code for each volume. Instead, this option updates the boot code on volumes that could be used as Windows boot volumes, which excludes any dynamic volumes that are not connected with an underlying disk partition. This restriction is present because boot code must be located at the beginning of a disk partition. <DriveLetter> Updates the master boot code on the volume associated with this drive letter. Boot code will not be updated if either 1) <DriveLetter> is not associated with a volume or 2) <DriveLetter> is associated with a volume not connected to an underlying disk partition. /force Forcibly dismounts the volume(s) during the boot code update. You should use this option with caution. If Bootsect.exe cannot gain exclusive volume access then the file system may overwrite the boot code before the next reboot. Bootsect.exe always attempts to lock and dismount the volume before each update. When /force is specified, a forced dismount is attempted if the initial lock attempt fails. A lock can fail, for example, if files on the target volume are currently opened by other programs. When successful, a forced dismount allows exclusive volume access and a reliable boot code update even though the initial lock failed. At the same time, a forced dismount invalidates all open handles to files on the target volume. This could result in unexpected behavior from the programs that opened these files. Therefore, you should use this option with caution. Example: To apply the master boot code that is compatible with NTLDR to the volume labeled E:, use the following command: bootsect /nt52 E: BOOTSECT.zip
  13. C:<driver path>\Bin\ATISetup.exe -NoUI -Install -Use C:<driver path>\Packages You extract the single binary you download from AMD's website and then in there you navigate into the Bin folder and ATIsetup.exe /? will give you more options including the silent install listed above. Sorry if this is a dupe, I didn't see it here nor find it when I searched for it.
  14. Record an answer file first by going setup.exe -r -f1C:\nvidia.iss and do a install with all the options you want. then save the answer file and you can silently install every time thereafter with: setup.exe -s -f1C:\PATHTO.ISS Note, there is NO space between f1 and the path.
  15. It does work, but you need to kill explorer and relaunch it for it to take: regedit /s REGTWEAK.REG taskkill /im "explorer.exe" /F start explorer.exe