How to make my Win7 OS drive work on new PC

Page 4 of 5 FirstFirst ... 2345 LastLast

  1. Posts : 16,187
    7 X64
       #31

    EFI>
    Microsoft > Boot >
    BCD, bootmgfw.efi, bootmgr.efi, memtest.efi (and a bunch of language folders)
    Boot > bootx64.efi (757,760 bytes)
    Sounds right for esp partition contents.

    Did you use the esp partition from the .tibx image ? It presumably contains some kind of shim or modded files to get around lack of csm support.


    p2p is paragon. It means adjust Physical to Physical disk.

    no boot folder on the C drive
    for bios booting using mbr disk , there would a Boot folder on the active partition.

    - - - Updated - - -

    I had a look at those .tibx images

    Used seagate discwizard to mount the .tibx image partitions and then captured the mounted partions into .wim files.

    [seagate discwizard is a free cut down Acronis but only works if you have a seagate disk attached. Western digital do a similar one which only works if you have a wd disk attached]

    It is then easy to apply the contents of the wim files onto a prepared esp partition and os partition. Then it is simple to adjust the osletter and fix the bcd entry before attemting to boot.

    If there is a bsod then p2p or similar can be used.


    How to make my Win7 OS drive work on new PC-tibx-mount1.jpg

    How to make my Win7 OS drive work on new PC-tibx-mount2.jpg

    How to make my Win7 OS drive work on new PC-tibx-mount3.jpg

    After the partitions are mounted ( using letters I and J in the screenshot above ) capture partition I into a .wim

    Then capture partition J into a .wim file.

    Then unmount the partitions.

    Same with the other image. Here are the .wims

    How to make my Win7 OS drive work on new PC-tibx-wim.jpg

    I used wimlib command line tool to capture the mounted partitions,

    wimlib-imagex.exe capture SOURCE DestinationWIMFILE IMAGE_NAME [IMAGE_DESC] [OPTION...]

    wimlib-imagex.exe capture I:\ "d:\UEFI_Win7_Pro_3888-ESP.wim" "UEFI_Win7_Pro_3888-ESP" --compress=fast
    wimlib - Main page


    but a gui such as dism++ could also do the job

    https://github.com/Chuyu-Team/Dism-M....1.1002.1B.zip
    Last edited by SIW2; 22 Feb 2024 at 16:25.
      My Computers


  2. Posts : 124
    Windows 7 Ultimate 64-bit
    Thread Starter
       #32

    SIW2 said:
    Sounds right for esp partition contents.
    Ok good, just making sure.
    Did you use the esp partition from the .tibx image ? It presumably contains some kind of shim or modded files to get around lack of csm support.
    Yes and it works, I don't know why I got that BCD error before but I can't reproduce it.
    p2p is paragon. It means adjust Physical to Physical disk.
    Alright, I got the Paragon WinPE and ran the "Adjust OS" feature. It said my OS needed the chipset driver and two ethernet drivers. It found the chipset driver but not the other two. The OS on the TIBX booted on my new PC! But both my keyboard and mouse stopped working (USB, wireless) so I couldn't do anything on it, couldn't fix the 640x480 resolution. We're making progress!

    But I'm a bit confused because this feature wasn't called the P2P wizard, just "Adjust OS" for new hardware so I assume it's the same thing?

    Anyway, you want me to convert the mounted TIBX image into two WIM files. Copy my original OS to the spare SSD, plug into new PC, then replace the install.wim on the Windows 7 ISO with the UEFI_Win7_8th_9th_noCSM.WIM to install.wim, then do a repair install?

    Is this accurate?
      My Computer


  3. Posts : 16,187
    7 X64
       #33

    image into two WIM files
    No, that is just what I did.

    You say you have already restored the image . Chipset infs are available here Intel Chipset Device "Drivers" (= INF files) - Win-Raid Forum

    But both my keyboard and mouse stopped working (USB, wireless) so I couldn't do anything on it, couldn't fix the 640x480 resolution.
    usb is an issue. Does the bios have port 60/64 emulation ?
      My Computers


  4. Posts : 124
    Windows 7 Ultimate 64-bit
    Thread Starter
       #34

    Yeah but the input devices didn't work. I'll keep the EFI partition and then see if I can copy my original OS and do the Paragon P2P on it.
    It's gonna be annoying because my original OS has no EFI drive and I can't copy a MBR disk to a GPT disk, so there will be a lot of partition dancing.
      My Computer


  5. Posts : 16,187
    7 X64
       #35

    I can't copy a MBR disk to a GPT disk
    capture your original os partition into a wim file. It is file based and can therefore be applied to a gpt partition.

    EITHER

    format ( not delete ) the gpt target partition before applying the wim

    OR

    create a folder on the target partition call it something sensible like TIBXOS. Then MOVE everything on that partition into the TIBXOS folder before applying the wim. That way all the stuff you restored from the .tibx will be in TIBXOS folder in case you want it later.

    After applying the wim :

    You will need to adjust the os to new hardware AND fix the osletter. Cant remember if paragon fixes the osletter as part of the adjust process, I think it has a separate module for that.

    I have made a thing to do the osletter fix

    How to make my Win7 OS drive work on new PC-bcdbootdisk-fixosletter.jpg

    In addition

    Your original os wont have the usb3 drivers so I sugggest using the usb3_win7_2021.zip update and drivers linked at the bottom of all my posts
      My Computers


  6. Posts : 124
    Windows 7 Ultimate 64-bit
    Thread Starter
       #36

    Okay this is weird, EaseUS was able to copy my MBR partition to the GPT SSD. I was able to keep the system reserved and EFI partition, I just overwrote the TIBX OS partition with my OS partition. I booted with Paragon PE and did the adjust OS thing. This time it didn't complain about a chipset driver missing but about SATA RAID driver. I rebooted and it complains that system32/winload.efi is corrupted or missing. You think I can replace it with the one from the TIBX OS?

    EDIT: Paragon PE had a boot correcting feature like yours to change the registry drive letter. It said none so I changed it to C. It didn't make it bootable but now when I try to access that feature, it crashes the liveUSB. Wtf?

    I may just try your method to do a WIM.
      My Computer


  7. Posts : 16,187
    7 X64
       #37

    EaseUS was able to copy my MBR partition to the GPT SSD...
    system32/winload.efi is corrupted or missing
    Easeus might have changed the partition id but not the bcd entry, which is why bootmgfw cant find winload.efi.

    If so, fix the bcd os entry to make it point at the windows partition
      My Computers


  8. Posts : 124
    Windows 7 Ultimate 64-bit
    Thread Starter
       #38

    SIW2 said:
    Easeus might have changed the partition id but not the bcd entry, which is why bootmgfw cant find winload.efi.

    If so, fix the bcd os entry to make it point at the windows partition
    How do i do that again?

    - - - Updated - - -

    bootrec /fixboot and bcdedit were returning access denied/not found errors, but that doesn't matter because I just re-copied the EFI partition from the TIBX and my OS partition. This time I chose the "correct BCD/boot errors" feature from the Paragon WinPE as well as the adjustOS.

    I was able to boot into my OS!!! But the problem of input devices not working remains. Why is this? The mini receiver doesn't even light up when I press the button, but they certainly do work on the boot menu or on a liveUSB.

    usb is an issue. Does the bios have port 60/64 emulation ?
    I don't see that option there, no. I tried all USB ports, both 2.0 and 3.0. Why does this happen?

    - - - Updated - - -

    It doesn't work on safe mode either.
      My Computer


  9. Posts : 16,187
    7 X64
       #39

    Have you integrated the usb3 update and drivers linked at the bottom of all my posts ?
      My Computers


  10. Posts : 124
    Windows 7 Ultimate 64-bit
    Thread Starter
       #40

    SIW2 said:
    Have you integrated the usb3 update and drivers linked at the bottom of all my posts ?
    I tried, Paragon was able to add the UASPSTOR one but not the XHCI one. Then I was gonna just install it on my running OS here and re-copy the entire partition, but running the .msu returned a "This update is not applicable to your computer." Trying to install either of the .INFs returned "The INF file you selected does not support this method of installation"

    EDIT: I got them installed via pnputil. Will re-copy partition and report back.
    EDIT2: Still no dice.
    EDIT3: ****in' A! I disabled driver signature enforcement during that advanced options screen you get when you press F8, and now my input devices work!

    This will make things much easier.

    However, I'm disturbed how fragile this installation on this new UEFI/GPT layout is. I tried installing a temporary Windows 7 on some unused space on the SSD using the latest patched ISO from that 7upv64P you linked to. It failed to get past the dancing balls during login so I abandoned the operation, but for some reason this affected my ability to boot into my adjustedOS as well. Even after deleting that botched-install partition and correcting boot parameters with Paragon, it still failed, so I had to redo everything all over again.

    This fragility worries me. But oh well, the hardest part of the learning curve is over.

    Thanks SIW2 for your patience and guiding me thru all this.
    Last edited by BlueBonnett; 25 Feb 2024 at 11:21.
      My Computer


 
Page 4 of 5 FirstFirst ... 2345 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 10:20.
Find Us