MrJinje Posted January 20, 2010 Author Share Posted January 20, 2010 replace the # in "/index:<#>" with the index # of the instance inside the WIM you actually packagedIn the past these were usually a case of mistaken image identity, one reader accidentally integrated his updates into image #1 not knowing that image #5 (#4 on x64) was actually the Ultimate he was looking for.Ok what did i miss, cause I don't see any mention of which image Index is which, other then here that says 4 is Ultimate .Didn't miss anything, I mistakenly assumed everyone was familiar with the WIM image format and never posted the list.Here you go - These are the default images inside an untouched ISO - obviously vLite users who remove all images can disregard. they only have 1 image in their iso'sx861 - Starter2 - Home Basic3 - Home Premium4 - Professional5 - Ultimatex641 - Home Basic2 - Home Premium3 - Professional4 - UltimateHope that helps. Link to comment Share on other sites More sharing options...
killalot Posted January 21, 2010 Share Posted January 21, 2010 replace the # in "/index:<#>" with the index # of the instance inside the WIM you actually packagedIn the past these were usually a case of mistaken image identity, one reader accidentally integrated his updates into image #1 not knowing that image #5 (#4 on x64) was actually the Ultimate he was looking for.Ok what did i miss, cause I don't see any mention of which image Index is which, other then here that says 4 is Ultimate .Didn't miss anything, I mistakenly assumed everyone was familiar with the WIM image format and never posted the list.Here you go - These are the default images inside an untouched ISO - obviously vLite users who remove all images can disregard. they only have 1 image in their iso'sx861 - Starter2 - Home Basic3 - Home Premium4 - Professional5 - Ultimatex641 - Home Basic2 - Home Premium3 - Professional4 - UltimateHope that helps.I see,I didn't realise you had to do that I thought all the hotfixes etc where applied to all version.Do you just select which version with the drop down box,1-7.In my case x64 ultimate will be number 4 Link to comment Share on other sites More sharing options...
MrJinje Posted January 22, 2010 Author Share Posted January 22, 2010 Do you just select which version with the drop down box,1-7.In my case x64 ultimate will be number 4Yes Link to comment Share on other sites More sharing options...
killalot Posted January 24, 2010 Share Posted January 24, 2010 Do you just select which version with the drop down box,1-7.In my case x64 ultimate will be number 4YesCheers,i have done the disk now and applied what i needed,thanks for the help. Link to comment Share on other sites More sharing options...
gotenks98 Posted February 25, 2010 Share Posted February 25, 2010 I am going to give this tool a try. Does anyone know if it will intergrate drivers that are unsigned in 64-bit or do I have to do all of those manually with the forced command? Link to comment Share on other sites More sharing options...
MrJinje Posted February 25, 2010 Author Share Posted February 25, 2010 This doesn't use the force command (run it separately if you need) but it seems to integrate them, because I get a pop up during installation asking permission to install an unsigned driver. Link to comment Share on other sites More sharing options...
gotenks98 Posted March 3, 2010 Share Posted March 3, 2010 This doesn't use the force command (run it separately if you need) but it seems to integrate them, because I get a pop up during installation asking permission to install an unsigned driver.Any chance you can add this force command functionality in future revisions? Its pain to sort out which drivers need to be redone when you got like 200+ drivers. Link to comment Share on other sites More sharing options...
MrJinje Posted March 8, 2010 Author Share Posted March 8, 2010 I would try something like this first.Dism /Image:D:\Mount /Add-Driver /Driver:D:\Drivers /Recurse /ForceUnsignedreport back if that allows you to force all 200 of your drivers in a single command. Link to comment Share on other sites More sharing options...
ricktendo Posted March 8, 2010 Share Posted March 8, 2010 Or use dir /b switch to get a list of the INF filesfor /f %i in ('dir /b "X:\Unsigned\*.inf"') do dism /image:X:\mount /add-driver /driver:"X:\Unsigned\%i" /forceunsigned Link to comment Share on other sites More sharing options...
Gremo Posted March 16, 2010 Share Posted March 16, 2010 a (really really) stupid question: integrate cert/insert key is used to get windows 7 already activated on install? I'm trying to achieve this on my notebook but i don't know here to find the cert file...Thanks Link to comment Share on other sites More sharing options...
MrJinje Posted March 16, 2010 Author Share Posted March 16, 2010 a (really really) stupid question: integrate cert/insert key is used to get windows 7 already activated on install? I'm trying to achieve this on my notebook but i don't know here to find the cert file...ThanksThat only works for OEM computers that came with Windows 7 originally. See this articleIf you have an Windows 7 OEM computer you might be able to find the proper certificate in your "C:\Windows\System32\OEM" folder. As for the OEM key, do not use the one on your sticker. That will not work because that key is retail COA not OEM:SLP. Run a product key checking tool on the machine to determine what Product Key your machine is really using, then use that key. Otherwise, if you do not have a Windows 7 OEM machine, forget it, that method will not work for you (but driver integration still should). Link to comment Share on other sites More sharing options...
maxXPsoft Posted March 16, 2010 Share Posted March 16, 2010 open admin cmd prompt and type slmgr -dliif OEM then then under description it will say OEM_SLP channelor type this for more slmgr -dli | slmgr -xpr | slmgr -dlv Link to comment Share on other sites More sharing options...
Gremo Posted March 16, 2010 Share Posted March 16, 2010 open admin cmd prompt and type slmgr -dliif OEM then then under description it will say OEM_SLP channelor type this for more slmgr -dli | slmgr -xpr | slmgr -dlvThis is what i get:So what should i do if it's OEM? Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted March 16, 2010 Share Posted March 16, 2010 You are using the Key from the Product Stocker (COA), not the generic SLP Key from OEM. Link to comment Share on other sites More sharing options...
Gremo Posted March 16, 2010 Share Posted March 16, 2010 You are using the Key from the Product Stocker (COA), not the generic SLP Key from OEM.This is a clean install of windows 7 homepremium x64 retail, with product key on the laptop cover, phone activation. No chance to get the activation file and put them on dvd? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now