New
#231
After the boot.wim is updated you copy boot.wim as WimRE.wim to replace the WimRE.wim on Windows\System32\Recovery, correct?
That is something I haven't think. The recovery WimRE.wim must also has the updated drivers. Very good.
After the boot.wim is updated you copy boot.wim as WimRE.wim to replace the WimRE.wim on Windows\System32\Recovery, correct?
That is something I haven't think. The recovery WimRE.wim must also has the updated drivers. Very good.
Image 2 of updated boot.wim is used to create the new winre.wim.After the boot.wim is updated you copy boot.wim as WimRE.wim to replace the WimRE.wim on Windows\System32\Recovery, correct?
I could possibly offer the option to create boot.wim and winre.wim with extra functions, such as explorer, diskmgmt, etc. - similar to my own boot media. But that would make them larger.
If you use simplix:
Also supports integration: SmartFix , DirectX , .NET Framework , Visual C ++ . Addon files should be placed in the same folder as UpdatePack7R2. (Place the add-on files next to 7update.cmd before running the cmd file)
Info
It is recommended that the resident antivirus monitor be unloaded from memory while the kit is running.
Last edited by SIW2; 13 Apr 2019 at 23:59.
SIW2, need your help.
I'm doing a small sub routine to check install.wim size (attached)
I have a big Install.wim file (5.7G) that I compare with Fat32 limit size (4G)
If I compare Install.wim file with 400M it gives me a correct result that is bigger.
If I compare Install.wim file with 4G it gives me a incorrect result that is smaller.
Can you help me?
4000000000 is too big for cmd to cope with - cannot process numbers larger than 2147483647
You can add extra non numeric characters e.g. $ to get around it:
That will return:Code:@echo off setlocal set n1=5711961982 set n2=4000000000 if $%n1%$ gtr $%n2%$ echo $%n1%$ is greater than $%n2%$ if $%n1%$ lss $%n2%$ echo $%n1%$ is less than $%n2%$ pause
$5711961982$ is greater than $4000000000$
It is weird - if you put those extra characters, then it processes as a string, and sorts correctly.
I don't know why there is that limitation on numbers.
Last edited by SIW2; 17 Apr 2019 at 10:15.
v22c on first post. Temp is now the mount folder in 7updater parent directory. Have changed messages for clarity.
Also an extra cmd file if you want to d/l latest dism for use by 7updater.cmd
On most PLC you have a different limit for integer and real numbers. On a CMD environment, numbers are treated as integer or as real?