New
#411
paul,
can you replicate any of this?
Hi Marley.
Dont know where its picking that Modified date field from, but you can change it
Home | Attribute Changer
Roy
Introducing a 3rd party program is not going to help. We are trying to find out why this particular system/user is having a problem with this particular script.
It works fine for me. Until he describes exactly what he did, I can't see if it can replicated.
I have tested several scenarios and all are successful.
Last edited by SIW2; 24 Jul 2019 at 20:55.
Hi SIW2,
I can see where your coming from.
I highly suspect its his system set-up. Would be handy to know exactly what it is.
(dual boot / extra drives / OS's etc)
The dates can only be picked up from Bios or explorer.exe
possible red herring that modified date is suspiciously close to the time Service pack 1 was released
Roy
Last edited by torchwood; 25 Jul 2019 at 06:20.
Hi Roy, You want the details of the computer I'm using to create the media or the computer I'm trying to install it on? The machine I'm using to create the media is a Sager D9F Intel i7 12 GB RAM 64 bit running Windows 10 Pro. The one I'm trying to install is an off-the-shelf Lenovo T460s (ThinkPad,ThinkPad T460s,Model:20F9003GUS).
I ordered a 20F90038US which comes with Windows 7 Pro. They sent me a 003GUS not 0038US. The 003GUS comes with Windows 10 not Windows 7. By the time I figured out they'd sent me the wrong model, I couldn't get my money back so I decided to try to install Windows 7 myself. I had to repartition the drive in order to install Windows 7, and in doing so I wiped out the original Windows 10 installation, naturally. So, it's currently not got an OS. You want the BIOS for this one?
As I've said I'm not a Windows person. Give me Linux or a Mac any day. Does that give you the information you need?
Hi SIW2
I'm not sure if you didn't see or understand my earlier answers, or if I'm not managing to understand what you are asking.... I'll try restating it.
I've done this two ways.
1) Using the 7UPDATERv30 script and file structure exactly as downloaded in the zip file. I update all images. With the v30 version, when I run set up, on the pop-up where I am to select the version I want to install, I now see the Windows 7 Professional (which I didn't with v29 or v28), but all Windows versions have the incorrect modification date of 11/21/2010. I proceed to install Windows 7 Pro but none of my drives or drivers can be seen by the Device Manager inside Windows 7 Pro, specifically I have no internet or USBs, among others.
2) Adding to the 7UPDATERv30 directories exactly as I described earlier for v28:
When I do this and run set up, I get the "A required CD/DVD driver device driver is missing..." error again and can't move on.
Please tell me if it's still not clear.
Tried repeating process 2 above but without the Samsung NVMe drivers. Same result. "A required CD/DVD driver device driver is missing...".
"A required CD/DVD driver device driver is missing..."
That usually means setup.exe can't find install.wim.
Most likely cause is not having integrated the correct usb3/3.1 drivers.
Another possibilty is that the boot.wim has MS nvme updates integrated, but they weren't extracted to the installation media sources folder.
Have a look at the installation media sources folder and check, for example, if the setup.exe there is the new version. It should match the setup.exe in the boot.wim image 2 sources folder.
Install media sources folder:
Line 222 in the script extracts the boot.wim image 2 sources folder into the installation media to ensure all the setup file versions match.
%wimlib% extract "%wimdir%\sources\boot.wim" 2 /Sources/ --no-acls --dest-dir="%wimdir%"
I had the exact same issue - the windows 7 installer can even detect the NVMe-drive, but you can't install windows on it.
For my Windows 7 SP2.8-series I want to have native NVMe-support with using MS's two NVMe-Updates. I ordered a ssdpekkw 12 for this, that, for my surprise, supports installation to it in GPT and MBR, for testing/developing. It took me 6 really fu**ing frustrating hours to figure it out (due to my ADHD i can get annoyed pretty fast). To get it working like i wanted to - using Gigabyte's Tool or combining a Windows 10's ISO and a Windows 7's install.wim, which would both work, tested it - wasn't an option for me because but I want it to have as Windows 7-native as possible.
Here's how i did it:
It took me some 'attempt's' to really notice it but in MS's how-to there's an, at least for me, unusal way for slipstreaming this:
First you have to add the two updates as usual, but DIRECTLY AFTER slipstreaming the two updates, you need to copy the contents from your mount-directory to the sources-directory that you use to create your ISO later:
dism /mount-wim /wimfile:w:\extract\sources\boot.wim /mountdir:%mount% /index:2
dism /image:%mount% /Add-Package /PackagePath:%v1%Updates\%arc%\NVMe
dism /image:%mount% /add-driver /driver:%v1%driver\%arc%\usb3 /recurse /forceunsigned
xcopy /s /y %mount%\sources w:\extract\sources
dism /unmount-wim /mountdir:%mount% /commit
Hope this helps, interested in replys.