Haven't implemented the integrate feature yet, thats something for the next few days now that I have a bit more free time on my hands (so I can sit down and do it, test it etc).
Hi bufadel, I have been using the Updates Installer V21 test4g to integrate into mounted images. I change this line in the cmd file just so you know what has been changed. I also rem out the lines that check the version so I could use it on a mounted x86 version. (When you release the version with the integrate feature how are you going to check if it is an x86 or x64 image?) I have noticed it does not integrate this update KB943790-x86 when it is already in CAB form. When I leave it as a MSU it integrates fine. This is only the x86 version I believe the problem is that the CAB file looks like this see how it starts with 6.0 [Windows6.0-KB943790-x86.cab] like I said if I integrate it as an MSU and let you convert it to a CAB it works fine. Code: :PP set ldr= if not exist list%p%.txt (if exist %kb958559% (Title Installing Microsoft Virtual-PC&%z%dism.exe /Image:C:\Mount /NoRestart /Add-Package %vpc%&goto :finishedcab) else goto :finishedcab) for /F "delims=" %%i in ('type "list%p%.txt"') do set ldr=!ldr! %%i if %p% equ 1 (if %kb958559% neq 0 set vpc=/packagepath:"%kb958559%"&set ldr=!ldr! %vpc%) set /a listcount+=1 set /a p+=1 Title Update list %listcount% of %list%, %listc% GDR and force LDR packages total %z%dism.exe /Image:C:\Mount /NoRestart /Add-Package %ldr% goto :PP
Thanks, I've fixed the installation of KB943790 when its already in .cab form locally Since x86 doesn't have a syswow64 folder (for example) I'll just do a check for that. In terms of whether they've mount an sp1 image or a RTM image etc, thats a little more difficult... any suggestions?!
For those on x86, looks like Microsoft uploaded the full installer (x86 & x64) after I did the whole thing with the web installer! - wasn't expecting them to release a full installer for this.
Ok so you are going to leave the check in place like it is now? If I do not rem it out right now and try to integrate to an image that is x86 and I am running on a x64 machine it will not work. So when we try to use the option to integrate to an image will you be checking the mount directory? for mounted version? What about something like this to get the mounted version info Code: DISM.exe /Image:C:\Mount /Get-CurrentEdition > C:\Users\dolivas\Desktop\DISM\CurrentEdition.txt
Thanks, I was forgetting about that version check method The alternation between x86 and x64 integration in the actual integrate/install part of the code should be very simple, its mainly the initial checks which need to be altered and added to.
@dolivas, If you have been successful, could you possibly provide a modified version of Trinket's tutorials, which of course were originally based on rick's, referencing rick's latest files showing how you were able to get to a final successful build? This might help us all catch up to where you and rick have gotten. Even if it's just a cosmetic fix, it's always nice to have it looking as professional as possible. I'm sure even Trinket would appreciate it. Of course if the new 4.5 version will end up replacing this, doing a version for that would be even better. Cheers and Regards
Yeah its exactly the same, like I said before 4.5 is essentially a big service pack for Net Framework 4, it even uses the same Net framework folder (v4.0.30319). This is different to Framework 3.5 which was a separate entity to Framework 3. The only reason why I didn't include the x86 msi's is because the full installer wasn't out when I posted it. Besides that, the installer made with the full installer should be identical to that which I posted, except with those 2 x86 msi's.
There is new Windows6.1-KB958488-v6001 hotfix inside 4.5 dev preview... ill check it tomorrow if its needed or not. Not sure if ill be using whole .net 4.5 because dev preview means there wont be any hotfixes for it...
again at work with time to go read old posts well this certs are a mess, they should just release new hotfix! anyway need to check some day whats all about this slim .net 4.0 installer...
doesnt seems to be needed for SP1, since SP1 have 6.2.7601.17514 and hotfix have only preSP1 compontents (6.2.7600.16513).
There probably won't be any hotfixes for it, although if there are any security updates that affect it they should be released. Instead of releasing hotfixes, we'll probably see a Release candidate, or at least another release or two before the final.
the standalone installer is the same like in win 8. i have tried to install it and look if it is newer. or i have done a mistake. can you please add win 8 support for your bat? cause there is a cab and a psf file inside the archive.
Windows 8 is not even in beta yet. It shouldn't be used for anything other than what it is—a preview.