Skauneboy

Member
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Skauneboy

Contact Methods

  • Website URL
    http://
  1. This might have been tried by others but I think I might be on to a way of finding out what can be removed from winsxs. Taking a snapshot of the COMPONENTS registry hive before and after removing packages with DISM shows the deletion of values corresponding to the winsxs components. Simply deleting these components from winsxs breaks Windows 7 installation but it might just be a question of editing the pending.xml found in the winsxs folder (i.e. removing references to removed packages). Any thoughts on if it's doable?
  2. Thanks for the excellent batch-file Jeronimo! So much easier for me to service my WIM-files now compared to when I did it manually. One question regarding your approach to package and component removal: I've noticed that you choose not to remove some packages with DISM which component's you check for removal in Vlite. Am I correct in assuming that this is done so that Vlite can "see" these packages and remove the files associated with them? I.E. Depending on the package it's preferable to use only DISM, only Vlite and in some cases both DISM and Vlite?
  3. Thanks for your efforts razormoon! I've struggled with the integration of ATI Catalyst drivers but the expand command made the difference. Would be nice if Dism did that automatically though.
  4. Actually it's easier than that You've named the Environment Variable for your source disk to %InstallDrive% but you're calling your FirstLogonCommands from %InstalDrive%. There's an l missing.
  5. I'm not sure what's wrong because I've always used UDF but here's what's working for me: oscdimg -u2 -m -h -b"E:\Program Files\Windows AIK\Tools\PETools\amd64\boot\etfsboot.com" G:\DVD G:\ISO\win7_x64.iso -lGRC1CULXFRER_EN_DVD Obviously, that's for a x64 version.