RR doesn't start Phoco on initial load..
Hi all, first post but i've been reading this forum for quite a while.
Seems that all wisdom needed for my carpc is found here:D
I've got this problem and have been searching and googling for solutions without succes.
(and i guess somebody is gonna respond 'but you didn't search hard enough nOOb look here....'-:rolleyes: )
but anyway here goes
i found similar problems but no real solutions
I want to use Phoco intergrated in RR
I got Phoco 1.5 registered and just downloaded the latest RR and LiquidSmoke skin.
Set up RR to the correct Phoco path and clicked the remote button.
Phoco is working fine standalone
Now when i start RR it says starting Phoco in the splash and nothing happens on the BT-icon or my phone or whatever.
When RR is loaded at the starting menu the PC is still busy and after a while i can see the phoco icon appear in the taskbar and also the BT-icon turning green(=active)
I can see a BT connection made on the phone
Only when i click the phone-menu in RR it doesn't show my battery status etc and i can't dial receive(in fact i can but nothing happens on my phone)
Now when i close down RR i get an error message from Phoco that it failed to load resources and i have to check my setup
Now when i've started AND CLOSED DOWN Phoco BEFORE starting RR,then RR starts up and does show batterystatus etc and is functional(after loading)
Of course i can start Phoco and LEAVE IT OPEN and then start RR and it will be functional no problem but then RR doesn't shut down Phoco on 'shut down' and gives an error message when the PC tries to shut down(someting about the BT stack server-it takes Windows too long to kill it)
Now i'm guessing this, dunno if its relevant;
I've read somewhere that RR tries to start Phoco and if it doesn't succeed in 10 sec then gives up
Phoco takes a longer time on initial load because of the .NET-stuff that needs to be loaded
Is it then possible that it just take too much time to load Phoco initially with RR on my humble 800mhz pc and if so is there a workaround
And if my guessing is totally wrong, is there another solution to the above problem?