Chameleon

Issue 297: on unsupported Mac hardware, use real (hardware) UDID

Reported by sti, Nov 5, 2012

This is a roadblock for users of early MacBooks and similar models 
where Mountain Lion is not officially supported despite the fact 
that their 64 bit hardware is compatible, because having a virtual 
UDID prevents proprietary software based on UDID to check its 
licence's validity from running.

In my specific case, I had no OS X friendly PC, which is the reason 
why I bought a refurbished Mac not so long ago; now I'm blocked on 
10.7 as long as this issue remains: 
this means buying another Mac or OS X friendly PC in the short term 
if it remains so, which I would love to avoid…

I'm willing to contribute to the effort either by code or by money, 
please tell me what you need.

Comment 1 by Cosmosis Jones, Feb 1, 2013

mek i know u boot your own lappie sometimes w/ chameleon. can we add 
the UDID loading to a real mac. we eithe rtry to automagically  know 
we are on a mac, or we use a flag?
Status: Accepted
Owner: meklort

Comment 2 by Evan Lojewski, Feb 1, 2013

In order to support this, you *must* use the FileNVRAM module.
Additonaly two things must happen
the nvram platform-uuid variable must be set with your platfomr id
The /efi/platform/systemid variable must not be published by 
chameleon.

Comment 3 by Evan Lojewski, Feb 1, 2013

Relations: duplicates 309

Comment 4 by Evan Lojewski, Feb 1, 2013

Status: Duplicate

Created: 6 years 7 months ago by sti

Updated: 6 years 4 months ago

Status: Duplicate

Owner: Evan Lojewski

Followed by: 1 person

Labels:
Priority:Medium
Type:Defect

This issue duplicates
309 - Req...riding preset Hard UUID.