Jump to content
59 posts in this topic

Recommended Posts

oopps sorry ... :)

I think it's posted in the correct place ... combo build 13E9a can only be accessed by SeedConfigurationUtility ... not from the Apple Store ... :)

Thanks for always keeping us informed, Wayang-NT! You don't need to prove your posts..

  • Like 2

If you have 13E9, you cannot install 13E9a (and it will not show up in App Store.)  Here's some details at the bottom of the article.

 

http://pikeralpha.wordpress.com/2014/05/28/os-x-mavericks-10-9-4-build-13e9-seeded/

  • Like 1

Please -

 

Can anyone describe the method to make the nVidia Web Drivers (which worked under 10.9.3) work under 10.9.4?

 

Is this possible? I've tried to research the issue but come up blank.

 

Thanks in advance for any help.

Please -

 

Can anyone describe the method to make the nVidia Web Drivers (which worked under 10.9.3) work under 10.9.4?

 

Is this possible? I've tried to research the issue but come up blank.

 

Thanks in advance for any help.

 

Edit NVDAStartup.kext/Info.plist

Change NVDARequiredOS key to your build number.

That's it.

  • 2 weeks later...

new seed ... 13E16

oops. I've been waiting for the new seed for damn long -,-

the first beta for 10.9.4 made me lose power management for my I3-380M :(

 

Confirmed. CPU speedstep is back to life.

Edited by p.H
  • Like 1

It's not that good, the web driver loads but GPU PM is broken and stays on max all the time when you use apps like preview and so on

 

Did you edit the right bits?

 

I have a ga-z87n-wifi, MSI GTX660 OC and it definltey does not clock up, nor stay clocked up when using preview and the like.

 

You have to be careful with what/how you edit.

 

Anyway, could be due to something as simple as mobo or GPU on your end.

Did you edit the right bits?

 

I have a ga-z87n-wifi, MSI GTX660 OC and it definltey does not clock up, nor stay clocked up when using preview and the like.

 

You have to be careful with what/how you edit.

 

Anyway, could be due to something as simple as mobo or GPU on your end.

What bits did you edit then? I only edited the NVDAStartup.kext with the build number to allow it to load forced? Is there anything else?

 

PS. Ignore this, it's working now after a couple of reboots

Guest
This topic is now closed to further replies.
×
×
  • Create New...