Update your Win 7 installation media

SIW2, How can I capture all the standard out from the 7UPDATER script? Is there an easy way to make it take a txt file as standard in so I can then run it command line and just pipe its output to another file? I'm betting if I sent you all the output you'd see the problem immediately.

Don't want you to think I'm being lazy. I'm looking online too how to do this, but no love yet. This is easy to do in shell. But I've found things I expect to be easy sometimes don't exist in cmd. (Like how isn't there an easy way to 'ls -l' a file?? And what about chmod?) I can't help but think that easy ways *do* exist in cmd, and that I just haven't managed to discover them yet...

Also, please ignore this part of my earlier message. I'm just shooting in the dark in all of this. Turns out the message I was talking about doesn't look like an error, and it does in fact occur for each Windows version. But I'm still poking at this idea that only HomeBasic is being modified by 7UPDATER, and maybe not correctly...

marley10 said:

First, while running the script at one point it says "Deleting as;ldfkh\Windows7HomeBasic\askljfa;gh;lkj..." (not sure of the exact file name) but it never says this for any of the other Windows versions.

marley10 said:

You know, I was assuming this was a weird Windows thing (from a Linux perspective) since no one on this forum seems concerned by it, but why DOESN'T the modification date change after the 7UPDATER script runs?? Okay, it shows it was accessed when I ran the script... good...but at least in Linux, it SHOULD'VE had a new modification date whenever anything had been written to the file.

(Talking about the install.wim images here...)

SIW2, am I totally barking up the wrong tree here?

HOLY SH-T!!!! I think I have progress!!!

So, going on the assumption that only HomeBasic was being modified by 7UPDATER, I went ahead and installed HomeBasic. Everything proceeds as before, except now I have functioning USBs in Windows 7! Unfortunately, all the other drivers and devices that were missing before are still missing, including ethernet. Please tell me this is consistent with not having the NVMe drivers working??

Actual "screen shots" of the Lenovo after Home Basic install. First are shots of the Device Manager showing some of the missing drivers and hardware ids:




Holy crap! A working USB 3!!! So beautiful...

My conclusions:

1) 7UPDATER for some reason isn't successfully rewriting the Windows 7 images 2-4.
2) When I try to include the NVMe update (either MS's or Samsung's) it somehow breaks the USB3 functionality during Setup. Very probably something I'm doing wrong?

Any seconds out there on these opinions? SIW2? Thanks.

Paul Black said:

Hi marley10,

Are you talking about something like DISM?
You can put things like WU [Windows Update] etc in a folder and run a script [batch] to integrate them.
There is also DISM++ which can be used to integrate drivers etc on a mounted image.

.... Not sure. My understanding is that 7UPDATER is calling various .cmd files, and these are calling the DISM program--among other things--many, many times. Right? So, on my machine 7UPDATER opens a cmd window and writes all standard out to it, including prompts for key presses. I'm hoping I can redirect all the output of all of its calls to a txt file via

Code:

C:\blahblah\7UPDATERv30>.\7UPDATER.cmd >> .\out.txt

run from an admin cmd window. But I would still need to give it the key presses it's expecting.

I guess I could do it the brute force way: Run it normally. Write down all the key presses in the order they're asked. Run it again and just input the right key presses in order. I guess I could probably "tail" (don't know the Windows-equiv command) the out.txt in order to tell when it's waiting for input?

Edit: Oh, rereading your question, I think the answer is no. I just want to run your 7UPDATER script and capture everything it's spewing to my screen. I'm pretty sure it's given me things I'm not recognizing as errors. Whether these are generated by its calls to DISM or trying to perform other operations, could be both.

Addendum: Aside from wanting to send you the output from 7UPDATER, I'd like to be able to study it myself. It flashes by too quickly in places, and overwrites the window contents (or closes and opens a new cmd window, I'm not sure which) for me to catch everything that it reports as it runs.

Great thing, marley10!
Long live Windows 7.
In my script I add the two NVMe-Hotfixes first an the USB3-Drivers second.
Maybe this helps you to get even more success.

Thanks! I also just discovered that the Windows equivalent to Linux's "tail" is... "tail". Just need to install a Windows Resource Kit.

By the way PAtrikK, you may have something there with the order of the NVMe and USB3 updates. I believe 7UPDATER does it in the other order.

I've been avoiding trying to alter SIW2's 7UPDATER script, because I think I have about a 98% chance of breaking it.