UefiSeven: Easily boot Windows 7 on UEFI class 3 devices

Discussion in 'Windows 7' started by manatails, Aug 3, 2020.

  1. manatails

    manatails MDL Novice

    Jul 23, 2014
    33
    40
    0
    It does not work for _all_ machines, as every implementation of UEFI differs from device to device, a specific device may not have functions required for UefiSeven to run, or behave in a way that breaks something UefiSeven uses.
     
  2. NoTears

    NoTears MDL Novice

    Aug 24, 2020
    18
    3
    0
    I see. Thanks for this information.
    Were you able to find compatible graphic drivers for both your machines Galaxy Book 12 and GPD MicroPC after installing win7 using UefiSeven ?
     
  3. manatails

    manatails MDL Novice

    Jul 23, 2014
    33
    40
    0
    I didn't really install Windows 7 on Galaxy Book 12, but I think it won't be difficult because it is based on Kaby Lake.
    I only worked with MicroPC but MicroPC's Gemini Lake SoC makes use of weird UHD 600 graphics that is not compatible with Coffee Lake drivers (UHD 6XX graphics), I couldn't find one that is compatible with MicroPC
     
  4. manatails

    manatails MDL Novice

    Jul 23, 2014
    33
    40
    0
    oops, mistake
     
  5. NoTears

    NoTears MDL Novice

    Aug 24, 2020
    18
    3
    0
    In one of your posts, you said there is no official graphic driver for 8th 9th 10th gen, so that would means that if you have the chance to find these drivers, they will be modified drivers. Correct ?
     
  6. NoTears

    NoTears MDL Novice

    Aug 24, 2020
    18
    3
    0
  7. manatails

    manatails MDL Novice

    Jul 23, 2014
    33
    40
    0
    You can do it yourself by examining the *.inf files in the package and looking for matching VEN/DEV IDs or device names
     
  8. polygaryd

    polygaryd MDL Novice

    Nov 7, 2016
    44
    2
    0
    @manatalis would you agree with some of the other posters on here that say if you get past the windows logo then uefiseven is fine and its a driver issue vs what I have said that maybe on some systems that maybe some hardware is using the memory locations that uefiseven is using causing a crash or another instance where uefiseven / vgashim / etc, could cause other instability issues for certain computers? I ask because you made the fork and should know better than any of us.

    My theory is Being as though uefiseven is basically a testing program and not made / tested to work on every machine like a final product, that my machine is having some issue with uefiseven or the like, and is hanging it vs a driver issue. If you follow the logic that windows 7 will install without any slipstreamed drivers (turning off usb 3 in bios) in legacy mode then why would my issue be a driver issue vs the int10h emulator?
     
  9. NoTears

    NoTears MDL Novice

    Aug 24, 2020
    18
    3
    0
    So you confirm that if there's no official graphic driver and if you have the chance to find one, it means that the driver is already modified. Correct ?
     
  10. manatails

    manatails MDL Novice

    Jul 23, 2014
    33
    40
    0
    If you got to the point where 'Install Windows' dialog is I suspect that it is a driver issue.
    UefiSeven only modifies IVT and VGA memory area, no legit drivers should have an issue with that.
     
  11. andreidi

    andreidi MDL Novice

    May 24, 2020
    34
    9
    0
    I tested the biostar version. It is unsigned, which gives me the impression that it's a modified driver. Installed it on my uhd 620, all good, including h265 playback working. I think it's the same as the videohelp version you create yourself. I'll test further to see if i still get bsod.
     
  12. !Absolute Zero!

    !Absolute Zero! MDL Novice

    Aug 19, 2020
    3
    0
    0
    #156 !Absolute Zero!, Aug 26, 2020
    Last edited: Aug 26, 2020
    @ manatails: Can you say anything about my problem (trying to run a UefiSeven-W7 from DVD instead of USB stick) ? (Posting #122)

    In manatail's guide, the UefiSeven files are inserted after the .iso has been created and mounted/"burned" onto a USB drive. In my case, for obvious reasons, I cannot modify an image after it has been burned onto a DVD - so, I copied the contents of my original Win7 install DVD and created a folder "boot" (because it was missing) inside the \EFI\ folder and there, I inserted the 3 files into that folder (same structure as with the USB stick method) and then run oscdimg (with the script I mentioned in my first posting) in order to create a burnable/mountable .iso image. Finally, I burned the .iso image onto an empty DVD.

    And I can assure you: the number of files & folders, folder structure/file position - EVERYTHING on the image mounted on the DVD looked exactly the same like the one mounted onto the USB stick!

    That means, the 3 modified files were already integrated BEFORE the image was mounted onto physical media (DVD) and even before the .iso file was generated...

    AZ
     
  13. polygaryd

    polygaryd MDL Novice

    Nov 7, 2016
    44
    2
    0
    I wasn't thinking drivers would have an issue with uefiseven but what if the uefi firmware wants to use the vga memory area for something else since it doesnt need it for vga since there is no csm and then when in legacy mode it obviously would not be able to use that memory area or it has its own emulator that takes windows 7 vga requests and points them to a different memory area for vga usage than uefiseven does or something. Without knowing how vgashim, uefiseven, etc work internally exactly and without knowing how thie uefi bios works internally its really hard to say whats happening.

    Maybe I cannot get across what I'm trying to say I don't know, but I'm wondering if this could be whats going on in my system. Drivers unless for some reason work in legacy mode but not in uefi should not be the issue here. I don't see why that would be the case.
     
  14. manatails

    manatails MDL Novice

    Jul 23, 2014
    33
    40
    0
    bootx64.efi is the first thing the computer tries to load from a fat32 disk so UefiSeven takes advantage of it.
    but in CD/DVD drives there is a separate boot sector so the computer tries to load that instead,
    as can be seen in your oscdimg command line

    oscdimg.exe -m -o -u2 -udfver102 -lWIN7 -bootdata:2#p0,e,b"C:\Win7\boot\etfsboot.com"#pEF,e,b"C:\Win7\efi\microsoft\boot\efisys.bin" "C:\Win7" "C:\ISO\CustomWin7Image.iso"

    efisys.bin is the actual efi bootloader that acts like bootx64.efi

    Not sure if you can remove those boot sectors from the image to force the system to use bootx64.efi instead
     
  15. CEW

    CEW MDL Senior Member

    Jan 21, 2011
    273
    143
    10
    #159 CEW, Aug 28, 2020
    Last edited: Aug 28, 2020

    You are supposed to merge the reg file . It says import before installing

    biostar.jpg
     
  16. Lometon6254

    Lometon6254 MDL Novice

    Nov 8, 2018
    5
    0
    0
    @manatails
    I am having an issue with my computer. Z370 chipset. Gigabyte Z370 HD3.
    I did the guide as you said on the github page. I get to Windows boot manager fine.

    I select Windows 7 and hit enter. I see starting windows and the flag assembles. Then, the flag pulsing freezes as soon as my keyboard lights up and i see my hdd activity light max out. numlock and caps light do nothing, and my keyboards "rainbow" color effect freezes. Im suspecting it is bluescreening.

    I then ran Bluescreenview on the drive. No bugchecks.

    It could also be running chkdsk. Either way, I don't get a video output. So UefiSeven is not functioning in my case.

    I booted it with boot logging. No boot log file was created for some odd reason.

    I saw some of your replies earlier. If this isn't a UefiSeven problem then my AMD driver sucks. I tried a different method a while back by replacing it with the Windows 10 bootloader. Windows 7 booted but no display, stuck at starting windows. I managed to RDP into it and it told me a lie:

    "AMD RX 5700 XT"
    "This device is working properly."

    Any ideas? Id love to get this working.