did you ever got to try the NVCAP key on the booter?
Edit: link to Asere's booter topic; check "Update Version 1.1.9" on first post.
Hi, thanks for the info about that nvcap overwrite key. I didnt tried that already. But perhaps that code isnt (isnt planned) in our chameleon builds.
Here the info of the link in one "view":
I simple patched my boot file by hexedit with the values from NVCAPMaker.Whats interesting is:
Most changes (to the orig. static/fixed values of chameleon ) can be seen in IORegistry but not all.
Ioregistry explorer shows taht, whats OS X at the end (after driver / system is up) has in use.
I made an screenshoot of orig. cameleon NVCAP and after that with mine (hexedited).
Orig. chameleon: 04 00 00 00 00 00 0d
00 00 00 00 00 00 0a
00 00 00 00
You see all injected as fixed coded in chameleon beside one byte which is shown 1c (hard coded 00 in orig. chameleon)
patched NVCAP = 04 00 00 00 00 00 03
00 00 00 00 00 00 07
00 00 00 00
(of orig.) shown in IOregistry in both
cases as 1c
(00 coded in orig. / 0c coded in patched) was changed by OS X : 00 > 1c or 0c (patched) > 1c
0d + 0a bytes (in orig.) was changed as in hexedit to 03 and 07 and stays changed in iOregistry view.
conclusion: Both (also orig. hard coded chameleon NVCAP) worked for me (near, only sleep often gets blue screen after wake).
I believe that the NVCAP IOregistry key is not real static ( i mean its read/write): OS X needs some correct basis information of NVCAP to work at early boottime but may change some details after boot is compledted by its drivers to that value. Maybe like Monitor prefpane which detects monitor, other NV driver parts.