Contribute
Register

[Guide] HP Envy Haswell series J/K/Q/N using Clover UEFI (10.11)

Status
Not open for further replies.
Paologas91 said:
Rehab to make XOSI simulate Windows 2013, should I insert "//" before every Windows in XOSI method and leaving uncommented only Windows 2013? Or I just have to uncomment Windows 2013 and don't care about other Windows?
Thanks.
Click to expand...

Your question is answered in the comments within the file.
As per Microsoft's documentation the other lines (for prior versions) should remain uncommented.
 
RehabMan said:
Your question is answered in the comments within the file.
As per Microsoft's documentation the other lines (for prior versions) should remain uncommented.
Click to expand...
So in my case that I have installed Windows 10 version 1703 is it correct to have XOSI method in this way?

Method(XOSI, 1)
{
// simulation targets
// source: (google 'Microsoft Windows _OSI')
// http://download.microsoft.com/download/7/E/7/7E7662CF-CBEA-470B-A97E-CE7CE0D98DC2/WinACPI_OSI.docx
Store(Package()
{
"Windows", // generic Windows query
"Windows 2001", // Windows XP
"Windows 2001 SP2", // Windows XP SP2
//"Windows 2001.1", // Windows Server 2003
//"Windows 2001.1 SP1", // Windows Server 2003 SP1
"Windows 2006", // Windows Vista
"Windows 2006 SP1", // Windows Vista SP1
//"Windows 2006.1", // Windows Server 2008
"Windows 2009", // Windows 7/Windows Server 2008 R2
"Windows 2012", // Windows 8/Windows Server 2012
"Windows 2013", // Windows 8.1/Windows Server 2012 R2
"Windows 2015", // Windows 10/Windows Server TP
"Windows 2016",
"Windows 2017",
}, Local0)
Return (Ones != Match(Local0, MEQ, Arg0, MTR, 0, 0))
}

Thank you
 
Paologas91 said:
So in my case that I have installed Windows 10 version 1703 is it correct to have XOSI method in this way?

Method(XOSI, 1)
{
// simulation targets
// source: (google 'Microsoft Windows _OSI')
// http://download.microsoft.com/download/7/E/7/7E7662CF-CBEA-470B-A97E-CE7CE0D98DC2/WinACPI_OSI.docx
Store(Package()
{
"Windows", // generic Windows query
"Windows 2001", // Windows XP
"Windows 2001 SP2", // Windows XP SP2
//"Windows 2001.1", // Windows Server 2003
//"Windows 2001.1 SP1", // Windows Server 2003 SP1
"Windows 2006", // Windows Vista
"Windows 2006 SP1", // Windows Vista SP1
//"Windows 2006.1", // Windows Server 2008
"Windows 2009", // Windows 7/Windows Server 2008 R2
"Windows 2012", // Windows 8/Windows Server 2012
"Windows 2013", // Windows 8.1/Windows Server 2012 R2
"Windows 2015", // Windows 10/Windows Server TP
"Windows 2016",
"Windows 2017",
}, Local0)
Return (Ones != Match(Local0, MEQ, Arg0, MTR, 0, 0))
}

Thank you
Click to expand...

The version of Windows installed has nothing to do with macOS/OS X.
The code placed in XOSI just affects what version of Windows is spoofed when running macOS/OS X.
Refer to code that calls _OSI in your ACPI set (DSDT+SSDTs/etc).
And refer to the ACPI spec for more info on _OSI.
 
RehabMan said:
The version of Windows installed has nothing to do with macOS/OS X.
The code placed in XOSI just affects what version of Windows is spoofed when running macOS/OS X.
Refer to code that calls _OSI in your ACPI set (DSDT+SSDTs/etc).
And refer to the ACPI spec for more info on _OSI.
Click to expand...
Ok I will check it. Btw Rehab I just bought from online the hp broadcom BCM94352HMB wifi+bt. U confirm me it will be recognized at all(wifi +bt) from my hp 15.n207sl?
thanks
 
Paologas91 said:
Ok I will check it. Btw Rehab I just bought from online the hp broadcom BCM94352HMB wifi+bt. U confirm me it will be recognized at all(wifi +bt) from my hp 15.n207sl?
thanks
Click to expand...

Only you can test the WiFi hardware to see if it is functional.
I never try to predict the future.
 
RehabMan said:
The version of Windows installed has nothing to do with macOS/OS X.
The code placed in XOSI just affects what version of Windows is spoofed when running macOS/OS X.
Refer to code that calls _OSI in your ACPI set (DSDT+SSDTs/etc).
And refer to the ACPI spec for more info on _OSI.
Click to expand...
In my original DSDT i found this

Method (_INI, 0, NotSerialized) // _INI: Initialize
{
CMSW (0x60, Zero)
Store (0x07D0, OSYS)
If (CondRefOf (\_OSI, Local0))
{
If (_OSI ("Linux"))
{
Store (0x03E8, OSYS)
}

If (_OSI ("NOT_WINP_KEY"))
{
Store (0x03E9, OSYS)
}

If (_OSI ("Windows 2001"))
{
Store (0x07D1, OSYS)
}

If (_OSI ("Windows 2001 SP1"))
{
Store (0x07D1, OSYS)
}

If (_OSI ("Windows 2001 SP2"))
{
Store (0x07D2, OSYS)
}

If (_OSI ("Windows 2001.1"))
{
Store (0x07D3, OSYS)
}

If (_OSI ("Windows 2006"))
{
Store (0x07D6, OSYS)
}

If (_OSI ("Windows 2009"))
{
Store (0x07D9, OSYS)
}

If (_OSI ("Windows 2012"))
{
Store (0x07DC, OSYS)
}

If (_OSI ("Windows 2013"))
{
Store (0x07DD, OSYS)
}
}



and this



Scope (_SB)
{
Device (BTKL)
{
Name (_HID, "INT3420") // _HID: Hardware ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Windows 2012"))
{
If (LEqual (BID, BW2C))
{
Return (0x0F)
}
}

Return (Zero)
}

Method (_PS0, 0, Serialized) // _PS0: Power State 0
{
}

Method (_PS3, 0, Serialized) // _PS3: Power State 3
{
}

Method (PSTS, 0, NotSerialized)
{
Return (RDGP (0x57))
}
}
}
 
Paologas91 said:
In my original DSDT i found this

Method (_INI, 0, NotSerialized) // _INI: Initialize
{
CMSW (0x60, Zero)
Store (0x07D0, OSYS)
If (CondRefOf (\_OSI, Local0))
{
If (_OSI ("Linux"))
{
Store (0x03E8, OSYS)
}

If (_OSI ("NOT_WINP_KEY"))
{
Store (0x03E9, OSYS)
}

If (_OSI ("Windows 2001"))
{
Store (0x07D1, OSYS)
}

If (_OSI ("Windows 2001 SP1"))
{
Store (0x07D1, OSYS)
}

If (_OSI ("Windows 2001 SP2"))
{
Store (0x07D2, OSYS)
}

If (_OSI ("Windows 2001.1"))
{
Store (0x07D3, OSYS)
}

If (_OSI ("Windows 2006"))
{
Store (0x07D6, OSYS)
}

If (_OSI ("Windows 2009"))
{
Store (0x07D9, OSYS)
}

If (_OSI ("Windows 2012"))
{
Store (0x07DC, OSYS)
}

If (_OSI ("Windows 2013"))
{
Store (0x07DD, OSYS)
}
}



and this



Scope (_SB)
{
Device (BTKL)
{
Name (_HID, "INT3420") // _HID: Hardware ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Windows 2012"))
{
If (LEqual (BID, BW2C))
{
Return (0x0F)
}
}

Return (Zero)
}

Method (_PS0, 0, Serialized) // _PS0: Power State 0
{
}

Method (_PS3, 0, Serialized) // _PS3: Power State 3
{
}

Method (PSTS, 0, NotSerialized)
{
Return (RDGP (0x57))
}
}
}
Click to expand...

So your DSDT has no specific support or checks for "Windows 2017"/"Windows 2016"/"Windows 2015", so including them in XOSI is nonsense. It won't have any effect, but you don't need it.

Hint: No such thing as "Windows 2017", "Windows 2016", AFAIK. Windows 10 is "Windows 2015".
 
Hi RehabMan, thanks for the great article. I was able to get El Cap working perfectly on my HP J series laptop using your guide. Just wondering what would I need to do differently if I was going to do a 'clean' install of Sierra? -- thanks in advance
 
jim32190 said:
Hi RehabMan, thanks for the great article. I was able to get El Cap working perfectly on my HP J series laptop using your guide. Just wondering what would I need to do differently if I was going to do a 'clean' install of Sierra? -- thanks in advance
Click to expand...

Sierra is same as post #1.
 
Happy as heck to say that thanks to Rehabman's guide I have managed to create a tri-boot mac system consisting of El Capitan, Sierra an the latest High Sierra Beta 4 with everything working even multi touch screen which i thank Touch-Base for :D
P.S. All systems load with the APFS.EFI and the BOOT drive was just for a spare backup EFI folder. Next install will be a hardware upgrade which will be a 1-2TB msata SSD and 1080P screen :D Once again thank you Rehabman for all your efforts in making all this possible. Also forgot to mention that this was did on a

HP Envy 15T-J000 Quad CTO Edition
 

Attachments

  • Screen Shot 2017-07-24 at 9.55.27 PM.png
    Screen Shot 2017-07-24 at 9.55.27 PM.png
    967.2 KB · Views: 103
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top