Having trouble with ISBoxer & YAR - Failed to find new Diablo III

[MokiCzech]

Hey guys,
I recently started botting and decided to buy ISBoxer. I am however having trouble starting D3 through it. When I link it with YAR, YAR throws following log:

[5.1.2013 2:03:31] <Bot #1> We are scheduled to start
[5.1.2013 2:03:31] <Bot #1> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[5.1.2013 2:03:31] <Bot #1> Language set: English (Brittain) : enGB
[5.1.2013 2:03:31] <Bot #1> Region set: Europe : eu.actual.battle.net
[5.1.2013 2:03:31] <Bot #1> Starting InnerSpace: D:\Apps\InnerSpace\ISBoxer Toolkit.exe
[5.1.2013 2:03:31] <Bot #1> With arguments: run isboxer -launchslot "Team" 1
[5.1.2013 2:03:31] <Bot #1> Searching for new process: Diablo III
[5.1.2013 2:03:51] <Bot #1> Failed to find new Diablo III
[5.1.2013 2:03:51] <Bot #1> Stopping

I linked all executables right, so I don't see where the problem could be. Even if I try to run D3 just via ISBoxer, it gets stuck and "loading" symbol (Diablo's head) and game never opens.
Anyone can help?
Thanks!

[Legendofbrett]

I have no idea about YAR, but speaking about Innerspace not loading even on its own, it sounds like maybe you are having issues with hard disk space or just not waiting long enough? When Inner space first launches D3 it will try to create a copy of d3 cache folder for each game, it will set on the diablo head screen for a while, 2-3min or longer depending on your setup.

edit- should be noted it only creates the cache folders on first start up, subsequent start ups it will use the previously created ones