New
#271
There is a simpler way to change the pack date into dd.mm.yyyy format:
for UpdatePack7R2-19.4.10.exeCode:for /f "tokens=1-2 delims=-" %%a in ('dir /b /a-d "%TP%\UpdatePack7R2-*.exe"') do set "dat=%%~nb" & set PACKNAM="%TP%\%%a-%%b" echo. FOR /F "Tokens=1-3 Delims=." %%A IN ("%dat%") DO SET ndat=%%C.%%B.20%%A echo.
%ndat% comes out as 10.04.2019
Convertdatehex.exe should in theory accept that.
It doesn't seem to. Whatever date I feed to convertdatehex.exe:Code:Example of use: ConvertDateHex.exe /d18.04.2019 /t20:30:09
Code:for /f "tokens=1,2 delims=- skip=1" %%a in ('bin\ConvertDateHex.exe /d%ndat% /t22:26:11') do set "HP=%%a"& set "LP=%%b"
it always spits out the current date in hex format.
Not a big issue, it just puts the date the wim was updated, instead of the pack date. That is ok - much better than leaving the original date on there.
Last edited by SIW2; 22 Apr 2019 at 12:15.
SIW2,
Sorry for the low level questions.
- Under Create commands you create UpdatePack7R2Finish.cmd.
- UpdatePack7R2Finish.cmd has instructions to Add-Driver and ADD-PACKAGE to \mount\UpdatePack7Wim and copy WINRE.WIM to mount\UpdatePack7Wim\Windows\System32\Recovery
Questions:
- Does UpdatePack7R2*.exe also add Drivers and PACKAGE to install.wim? If yes, if you update install.wim with UpdatePack7R2*.exe there is no need to previous run :MountInstallWim that also add Drivers and PACKAGES to install.wim, correct?
- Who uses UpdatePack7R2Wim.cmd, UpdatePack7R2*.exe?
- Does UpdatePack7R2Finish.cmd and UpdatePack7R2Wim.cmd must be in same folder of UpdatePack7R2*.exe? (I suppose yes)
Thanks. Unfortunately, InSpectre won't work for what I need. Simply disabling in registry still keeps "Total Media Theater" from running. I think I would have to uninstall/revert back to the original files for it to work. I will give DISM++ a try and see if that helps. If not on that particular system I may just need to leave things at Windows 7 SP1 and not do any updates (or at least updates past 12/15). Which shouldn't be a big deal as that system is only used as an HTPC and not for full work/online. However, it would have been nice to have an a completely up to date system sans the three problematic security updates.
- Does UpdatePack7R2*.exe also add Drivers and PACKAGE to install.wim?
1. Drivers:
The updatepack automatically adds usb3 to install.wim, but not to the bootable wims.
Therefore there is no advantage adding usb 3 drivers to DRIVERS\install%wimarch% folder - no harm if you do.
But you will want to add usb3 drivers to DRIVERS\boot%wimarch%
Any other drivers you want included e.g for your network card, or maybe SD card, or oem nvme drivers - you need to add into the folders.
[Note: As far as I can tell, oem nvme drivers will only work if you also include the MS nvme updates]
2. Updates
MS nvme updates are not automatically included by the updatepack.
Therefore - if you want to include the MS nvme updates - put them in UPDATES\boot%wimarch% and UPDATES\install%wimarch%
1.Yes- Who uses UpdatePack7R2Wim.cmd, UpdatePack7R2*.exe?
2.Yes- Does UpdatePack7R2Finish.cmd and UpdatePack7R2Wim.cmd must be in same folder of UpdatePack7R2*.exe? (I suppose yes)
3. You can also place any addons in the same folder ( next to the updatepack) and they will be included.
The add ons have a .WA extension. Net Frame 4.8 and VC redists etc can be included that way.
NF4.8
Release v2019.04.14 . abbodi1406/dotNetFx4xW7A . GitHub
Lang packs for NF4.8
Release v2019.04.13 . abbodi1406/dotNetFx4xW7A . GitHub
VC redistx64 2005-2008
https://gitlab.com/stdout12/adns/upl...64_SxS_Win7.WA
VC redistx64 2019
https://gitlab.com/stdout12/adns/upl...14.20.27508.WA
VCRedistx86 2005-2008
https://gitlab.com/stdout12/adns/upl...86_SxS_Win7.WA
VCRedistx86 2019
https://gitlab.com/stdout12/adns/upl...14.20.27508.WA
4. Surprisingly, you can also put the SP1 exe in the same folder and it will be integrated if the target image is SP0. I think integrating SP1 only when updating a live install, not for installation media.
Windows6.1-KB976932-X86.exe
https://download.microsoft.com/downl...976932-X86.exe
Windows6.1-KB976932-X64.exe
https://download.microsoft.com/downl...976932-X64.exe
Last edited by SIW2; 24 Apr 2019 at 00:35.
Thanks, SIW2
As UpdatePack7R2Finish.cmd has instructions to Add-Driver and ADD-PACKAGE to \mount\UpdatePack7Wim and copy WINRE.WIM to mount\UpdatePack7Wim\Windows\System32\Recovery to install.wim
Question:
- if you update install.wim with UpdatePack7R2*.exe + UpdatePack7R2Finish.cmd there is no need to call :MountInstallWim that will also add Drivers and PACKAGES to install.wim, correct?
Correct.Question:
- if you update install.wim with UpdatePack7R2*.exe + UpdatePack7R2Finish.cmd there is no need to call :MountInstallWim that will also add Drivers and PACKAGES to install.wim, correct?
It is only if not using UpdatePack7R2*.exe:
check if the user has put drivers or updates in the folders - if yes, then mount install.wim and get dism to install the stuff in the folders - and also copy in the new winre.wim if there is one.
Last edited by SIW2; 23 Apr 2019 at 20:49.
SEW2, here is the problem:
- Some install.wim doesn't have all four images and Win7 x86 installation disk also has a starter image.
- On :Chooseimage you have the options to select all (*) or single (1 to 4)
- How do I do a "for" to only allow the user to select one of the listed images refusing others not listed
(IF /I NOT '%CHOI%'=='1' IF /I NOT '%CHOI%'=='2' IF /I NOT '%CHOI%'=='3' IF /I NOT '%CHOI%'=='4' IF /I NOT '%CHOI%'=='*' goto :Chooseimage)?
- Does UpdatePack7R2* can deal with images with less or more than 4 images to update when all (*) is selected?
- Does your :All script deal with images with less or more than 4 images to update when all (*) is selected?