Mike Taylor

So I have the mentioned docking station D6000 that I can plug in to USB-C or USB-A port. OOB works everything but HDMI/DP ports. Any tips what needs to be done to make the DP working? My current configuration is 1:1 from this thread, running 10.14

It was indeed usb issue. I applied some patches and got it to work. Thanks:)

Unfortunately still the same issue. It hangs on this screen and it is followed with "forbidden" sign pic rel

Hi. So I've followed @Hervé's guide on installing Mojave on Latitude 7490 model, though I couldn't get through the running from USB. I configured the BIOS accordingly and below's my folder structure Then upon running OSX installer from Clover I see tons of lines (too fast to capture, though I can record video if neccessary). I noticed, however, that most of them are very similar to the ACPI errors which you can also see on the screen below. I don't know where to go from this point Thanks!

Right, so conclusion of what I've been doing is as follows. This whole can-not-launch-in-UEFI thing must have something to do with video drivers as Engert was mentioned in the topic I linked in the previous post. Eventually I launched Windows 7 (WinPE 3.1) installer with Legacy ROM support (which is not the same as Legacy Boot) but I did not proceed with the installer. Instead I followed guide by @las_vegas in this thread https://osxlatitude.com/forums/topic/7813-dual-booting-any-os-x-and-windows-not-system-reserved-partition/ Additionally I had a problem that Windows 7 installer did not detect the USB stick it booted from but it's a well known issue that Win7 installer does not have USB 3.0/3.1 drivers so you have to add them to the WIMs. After restarting my laptop I could boot into windows. Then I tried to go back to bios and disable legacy ROM support to see if the windows will boot. Indeed it didn't. I saw the floating windows logo which hanged in the middle but I've heard the windows welcome sound so the system itself booted but the screen hanged which again relates to the video driver issue. Thus I switched legacy ROM support back on again, booted windows, installed Intel Graphics drivers, back to BIOS, disable legacy rom support, back to windows and all worked fine. From this moment onwards I could disable any ROM legacy support in BIOS and be able to boot (via Clover) to both Windows and MacOS. I still sustain the opinion that Windows 7 by itself does not work with pure UEFI. I don't know what INT10 (which Engert mentions in his posts) is, but even if I tried to install Windows 7 via WinPE 5.1 (which probably would work as it might have had proper video drivers for UEFI), I still wouldn't be able to boot into newly installed Windows to be able to install the graphic drivers. To sum up, I wouldn't have done it without enabling Legacy ROM support which satisfies me in 95% but my knowledge isn't good enough to do anything about it.

Thanks for that link, I'll try to play around a bit with WinPE releases and try to use newer WinPE for Win7 than it already has. Unfortunatelly I can't agree. The only way for me to run the installer was to enable legacy ROMs (it's still UEFI boot but with some additional legacy drivers). I urge you to read posts #16, #17, #23 and #24 in this thread https://www.sevenforums.com/installation-setup/398482-windows-7-x64-uefi-install-even-possible-3.html#post3266108 This guy was pondering about this booting in UEFI issue and he concluded that it'll very difficult to make it working in "pure" UEFI without any grasp from legacy. Unfortunatelly I can't confirm that the installer runs in UEFI because the method mentioned in the link you provided is not available in WinPE v3. I'll see if I can run the installer with WinPE 5 and will come back with the results.

Thing is that I dont want Windows 10 -- it's abomination at its finest. I'm worried windows 7 was never successfully installed on pure UEFI...

The result is exactly the same. It's worth noticing that it's exactly the same, meaning the error screen still shows \EFI\Microsoft\Boot Another thing worth mentioning (perhaps) is that when Rufus creates UEFI USB it automatically creates \EFI\Boot folder with BOOTX64.EFI file in it which has exactly the same checksum as bootmgfw.efi from install.wim\1\Windows\Boot\EFI\ so it would mean that it's some generic file?

Shall I then boot it via f12 or clover?

I tried that method too. Same result.

That is what I've doing now and still getting the error attached in the first post. Windows is x64 and the partition was FAT32 (please see the attachement for gui reference). I'm not even at the parition my hard drive+install part, first I need to get to the windows installer itself

Hi. I am aware that this thread has been repeated over and over. Thing is, 90% of the threads end up with "oh well, uefi is borked, just run in legacy and all will be fine" and the other 10% just doesn't work in my case apparently. I don't wanna allow legacy boot (even that my bios has such options) because I've been advised already not do mix legacy and uefi at any point. Thus I disabled legacy completely in BIOS forcing UEFI only. The situation is as follows: I want to install Win7 on the same SSD as current 10.13. Right now I have 3 paritions: #1 EFI, #2 APFS (10.13), #3 HFS+ (a placeholder for windows). I have created a bootable USB stick (pretty sure I did it correctly). I have been trying to do this manually (by partitioning the USB and copying files) as well as automatically (using Rufus tool). Each time I paid attention to partition disk as GPT no-csm. The issue is that each time I try to boot the Windows 7 installer I end up on infamous error page (see attachement) [Google spider: 0xc000000d \EFI\Microsoft\Boot\BCD)] I have tried to boot directly (F12) as well as I have tried to use Clover which is already installed on the SSD but same result each time. (Clover recognizes this EFI correctly -- see attachement). I've tried already having \EFI\Microsoft\Boot and also \EFI\Boot, either or both, no budge. As for the .efi files themselves I tried to use (as suggested on the internet) bootmgfw.efi from Windows' install.wim archive, I tried also to rename it to BOOTX64.efi as well as I tried to use BOOTX64.efi "generated" by rufus. Neither of those 3 options didn't change anything. What other suggestions I shall try? Why is MS installer even trying to "run" this BCD? Shouldn't this file be executed in Legacy only? Thanks

Right I was able, as per your instructions, to create a bootable USB stick. However, I'm not sure if that has nothing to do with changes to HDD EFI. As @Bronxteck, it seems like in some cases it doesn't just look only at USB EFI when booting from USB..

wow! The system booted! What does that tell us? That in fact I don't need to put SSDT files into patched at all? Because the ones taken from the (bios??) are good enough for system to boot? i'll backup now everything I've done so far on MacOS (just in case) and I'll try to create a bootable USB stick myself. I'm really eager to understand more and get it done. I'll keep you updated

Okay so let me get this straight (there's still change I can get my work back). Looking at the entries from your post: Rename HDAS to HDEF Rename HECI to IMEI Rename GFX0 to IGPU Rename _DSM to XDSM Those I understand that I can "fix" using Config, just like this, right? Then LPC Skylake IRQ RTC Mutex HPET OS X Check (Windows 7) HDEF layout1 USB 3.0 _pwr 0x6D Skylake Are patches I can get from Rehabmans repo and patch DSDT only, correct? (not SSDT) + the skylake Intel 520 graphics you plaintext'd Then I recompile DSDT and include it and I'm done? I'm not quite sure what I have to do with SSDT files? I don't have to recompile them? Just remove their suffixes like SSDT-0-SataTabl.aml -> SSDT-0.aml, SSDT-1-sensrhub.aml -> SSDT-1.aml etc and that's it? Is the HDEF layout patch neccessary if I have set layout-id 11 in Clover>Devices>Audio>Inject>11 ? Problems I jumped into when patching: Skylake Intel 520 patch, after trying to complile I get "Input file does not appear to be an ASL or data table source file" LPC Skylake brakes the compilation too with "Name already exists in scope (_DSM)" and a couple of "Object not found or not accessible from scope (^^LPCB.CRID)"