Update your Win 7 installation media

[Paul Black]

Sorry SIW2, I have confused myself!

That is why it is common practice to remove the \ from %~dp0

I have just turned my other computer off but I will see tomorrow if this one liner works [just out of curiosity really]...

SET TP=%TP:~0,-1% systeminfo > "%TP%"\My_System_Specs.txt

 

[erpster4]

I've burned the Win 7 HP August 2018 (7601.24214.180801-1700.win7sp1_ldr_escrow_CLIENT_PROFESSIONAL_x64FRE_en-us.iso) that I've downloaded from HeiDoc on a DVD+R DL.
For my surprise I could only boot it as UEFI. Tried to force a Legacy boot that failed.
I'm not aware of DVD boot sequence. Does a DVD has a MBR to boot as Legacy?
Don't know if the iso didn't have the MBR(?) or if a DL DVD has a different kind of SL DVD MBR(?).
If you can give me a link that explains CD/ DVD boot sequence I'll appreciate.

it depends on the motherboard or hardware you have.

I can boot that directy in MBR because I'm using older PCs that use traditional BIOS chips, not UEFI

 

[SIW2]

Version 22 on first post. Updates till 10th april 2019.

 

[Paul Black]

Hi SIW2,

3. SET TP=%TP:~0,-1%

means remove the last character from %TP%. It removes the backslash.

So now if you echo the variable %TP%, it returns this:

C:\Users\SIW2\Desktop

It was just out of curious why I couldn't get it to work. I know what was confusing me now. I was running it on a Vista machine!

@echo off
echo. &echo.
SET tp=%tp:~0,-1%
echo %tp%\abc.txt
echo. &echo.
pause

This gives me => ~0,-1\abc.txt.

So I did this...

@echo off
echo. &echo.
SET tp=%~dp0
IF "%tp:~-1%"=="\" SET tp=%tp:~0,-1%
echo %tp%\abc.txt
echo. &echo.
pause

This gives me => C:\Users\<username>\Desktop\abc.txt [single backslash].

 

[Paul Black]

Version 22 on first post. Updates till 10th april 2019.

Thanks SIW2 .

 

[SIW2]

@echo off
echo. &echo.
SET tp=%tp:~0,-1%
echo %tp%\abc.txt
echo. &echo.
pause

That doesn't work because you haven't assigned a value to the TP variable. You need to SET TP=%~dp0 before removing the last character with SET tp=%tp:~0,-1%.

 

[Paul Black]

Brilliant, thanks SIW2 .

 

[Megahertz07]

SIW2, as I'm studying line by line of your previous 7UPDATERv21B.zip, can you please tell what are the difference between version 21B and v22?

 

[SIW2]

SIW2, as I'm studying line by line of your previous 7UPDATERv21B.zip, can you please tell what are the difference between version 21B and v22?

Only the new updatepack for now. I am thinking of making some changes.

If you want to use %~dp0MOUNT and %~dp0TEmp_N as your temp files, you can use these to replace 7Updaterv22.cmd and the couple of cmd files in the BIN folder

View attachment 7UPDATER22B.zip

 

[Megahertz07]

SIW2, on :MountBootWim you look for updates on Updates folder.

What kind of update you slipstream on boot.wim?


Can you use *.msu files on Updates folder to update install.wim (and boot.wim)?

 

[Megahertz07]

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.

 

[SIW2]

After the boot.wim is updated you copy boot.wim as WimRE.wim to replace the WimRE.wim on Windows\System32\Recovery, correct?

Image 2 of updated boot.wim is used to create the new winre.wim.

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.

 

[SIW2]

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.

 

[SIW2]

Net framework Add-On

vc redist

 

[SIW2]

Integrating updates and Net Frame 4.8 and VC runtimes:



Install.wim is larger,of course. The add-ons integrate very quickly.

 

[Megahertz07]

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?

 

[SIW2]

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:

[USER=353699]echo[/USER] 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

That will return:
$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.

 

[Megahertz07]

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:

[USER=353699]echo[/USER] 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

That will return:
$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.

It is more strange as it finds and set size= to the correct number value.
Thanks

 

[SIW2]

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

 

[Megahertz07]

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?