Kai GUI/Service "apparently dies" on WinXp

Posted: Fri Sep 24, 2004 11:01 am

Greetings All,

I'm somewhat in a conundrum.

In essence I'm trying to connect my XBox via a router to play games.
After a period the Win32 Kai Link software appears to die with the service/gui fading into oblivion. (This happens on 2 different WinXP Prof machines I have). To date I have not been able to play a game.

As such I'm asking for assistance in the following:
a) rectifying the dying Kai service/GUI on XP
b) configuring AVALAUNCH to utilise XLink Kai service and fire a game

My configuration is as follows:

SMC 7008ABR Router - UDP Port 30000 forwarded to local machine IP
WinXP Prof. SP1 running latest XLink GUI Client (No firewall software)
XBox Evox Dash 3935 - Configured with Static IP
XBox Media Centre Sep 04/2004 Build
Avalaunch 0.49
Latest WinPCap as per instruction ie. uinstalled then let XLink Kai reinstall

What I am able to do is the following:

- Start Win32 XLink Kai software and view 'arenas' and friends. Have not managed to connect to an IRC room, but I believe that is user error.
- See the XBOX under performance when a system link game is running (should you be able to 'discover' an xbox prior to this ?)
- In XBMC, fire XLink KAI to sort of see arenas and 'friends/online etc. who I have configured. I have not launched a game.

Problems:

In Avalaunch 0.49, it says its connecting then appears to hang, I believe this inter related with the dying Win32 software/service.

Any troubleshooting advice or direction would be much appreciated.

Regards

Joined: 30 Jul 2006 Posts: 0

Quote:

After a period the Win32 Kai Link software appears to die with the service/gui fading into oblivion. (This happens on 2 different WinXP Prof machines I have). To date I have not been able to play a game.

By default, the engine will close on loss of UI... connecting to the engine wih Ava/XBMC causes the PC UI to be closed - hence the engine closes.

I recommend you look into the kaiConfig tool.. especially the dashboard profile option..

TD

Posted: Fri Sep 24, 2004 2:18 pm

what i do is set it for the Dashboard option, then check the box to launch the UI as well.

That way it will still run the UI and if ava/xbmc connects 1st it will just close the UI and the engine will still be there.

Also works so you can go through the arena's on the PC 1st if you want then jump over to the xbox to make the final decision.

Posted: Fri Sep 24, 2004 2:36 pm

Thanks for the help so far. A true reflection on what the internet should be used ie. sharing of knowled.

Onwards...

The engine doesn't appear to be 'closing' now as a result of your suggestions.

Hence part appears to be solved Smile

... sort of...

It appears to work for XBMC, I can go in and see it retrieving arenas and users etc. in the interface, however whilst using Avalaunch it correctly locatest the Kai engine on the local PC but then freezes on the "Login Successful" screen.

Anymore suggestions? Once again, thank you for your time and effort.