Jump to content
15 posts in this topic

Recommended Posts

Anyone have any pointers as to why screenflow might not be starting on my iPC setup? I have QE/CI working very well (somebits of Quartz test in Xbench up to 4x faster than my brand new iMac) and sound is also good.

 

edit: I was using 1.2.1 but 1.0.2 seems to be ok

Welcome to the Club!

 

I have the same problems and as far as i got help from the company who wrote screenflow this is no issue with the graphiccard, it is a issue with the non-standard ethernet-ports on hackintoshs (i got a gigabyte-board GA-EP35-DS4, it simply didn't work!).

 

I tried several things but there is no chance. I bought the program! Support? Forget about it! I even waited weeks for a response, no the program is sold to another company i even have lesser hopes! Maybe some techie from the community colud look ito that.

 

I use screenflow now only on my macbook pro....:-(

  • 1 month later...

Same here using an almost fresh xXx 10.5.6 install

 

1.2.1 used to work for a long time on Leo4all then "something" (update after 10.5.6 i guess) broke it...

 

Funny thing besides NO error or what so ever displayed in console, it wont launch BUT you can record...

 

get inside the app (package) -> /Contents/MacOS/ScreenflowHelper.app

 

Now you can record (menubar) but still as soon as the MAIN app tries to launch.....

 

Fatal initialization error :P

Great, 2 hours till law-lecture and instead of sleeping -> whole night.. google research....

 

Now I understand less than before :) kind of

 

Things i found out:

 

My onboard chip is a Realtek 8111B, which works "out of the box" using Leo4All v3, Ipc 10.5.6 and xxx 10.5.6 (now running xXx release). I had that Error 35 with xXx so i followed this guide http://sneosx86.freeflux.net/blog/archive/...around-fix.html

 

No more errors in Console.

 

Main thing i don't understand after research:

 

System Profiler shows AppleRTL8169Ethernet.kext under Extension (which i thought means --> loaded -besides that's not my chip). But since i have the Disabler.kext (found in QT 7.6 Solution for mouselag thread) running (and working - since it fixed my lag) and STILL showing those 2 kexts that it should block in Extensions under Profiler.... i am clueless. (why even though blocked through the disabler they still show up under SystemProfiler/Extensions)... maybe it's supposed to be that way.

 

My assumption so far: SystemProfiler shows kexts under Extensions-tab even though they are disabled through a Disabler.kext. Plus+ I am using the "wrong" kext, but everything (really everthing from Appzapper to Xslimmer) works. - except Screenflow.

 

So before messing around with replacing old kexts. I have to verify HOW the whole kext-"things" really work in OSX86.

 

Still can't imagine why Screenflow (and no other app) refuses to start because of an Ethernet-issue...

 

Hope somebody with better OSX86 skills hops on this thread and gives another hint or tip. :D

 

so long...

 

cheers

Fixed it :)

 

What i did: (as usual i am not exactly sure if each step is necessary)

 

 

[*]trashed the NetworkInterfaces.plist

 

[*]OSX86Tools -> checked "Set Extensions permissions", "Clear Extensions Cache" and "Touch Extensions Folder"

 

[*]Osx86Tools -> Added Efi Ethernet Strings - didn't hit restart -> again did Step 2 (repairing, cleaning)

 

[*]Rebooted (i always do this through menubar, since when i click restart in OSX86Tools it seems like a "wooosh reboot (1sec)"

[*]-f @ darwin

 

[*]System Preferences Network told me that it found a new Ethernet device, then deleted the one that was still listed but was "iguess an old "corpse".

 

 

Even though OSX created a new NetworkInterfaces.plist, still no "35" errors in console, Timemachine works again (i found out that i had that - couldnt find Ethernet interface error- TM error) PLUS Screenflow works again :)

 

Hope that helps :)

 

cheers

 

ps: BIG thanks to the "Ethernet related clue" !!!! I would have bet that this was a GFX related error :)

 

pps: missed law lecture :D

  • 1 month later...

stanfordbinet - congrats on getting it working. I'm having the exact same problem (same Gigabyte GA-EP35-DS4 mentioned earlier in the thread). I tried your solution but adding the Efi Ethernet Strings resulted in a hang on boot, so I had to go back to an earlier com.apple.Boot.plist.

 

I just want to make sure I'm doing this step of your instructions right so:

 

- in OSX86tools, click on 'Add EFI Strings'

- in next window click 'Ethernet Strings'

- in next window click 'Import String to boot editor'

- 'apply changes to com.apple.boot.plist'

 

Is that correct?

 

I notice you're using Leo4All install, whereas mine is a retail install (like this one) so maybe it's never going to work. I'd REALLY like to get Screenflow running though. Any help greatly appreciated.

  • 1 month later...
i still dono what to do.. please help me... :(

 

did you try this?

 

[1]trashed the NetworkInterfaces.plist

 

[2]OSX86Tools -> checked "Set Extensions permissions", "Clear Extensions Cache" and "Touch Extensions Folder"

 

[3]Osx86Tools -> Added Efi Ethernet Strings - didn't hit restart -> again did Step 2 (repairing, cleaning)

 

[4]Rebooted (i always do this through menubar, since when i click restart in OSX86Tools it seems like a "wooosh reboot (1sec)"

 

[5]-f @ darwin

 

[6]System Preferences Network told me that it found a new Ethernet device, then deleted the one that was still listed but was "iguess an old "corpse".

 

before doing this make sure you have a bootable backup!

  • 6 months later...
×
×
  • Create New...