Author |
Message |
[SaD]TizzO
Team XLink Moderator
Joined: 21 May 2004
Posts: 1215
|
Posted:
Wed Nov 03, 2004 4:40 pm |
|
Is your network reachable? yes
Are you using a port-forward? yes
Is your console being detected? yes
Brief description of your network setup:
Internet connected to modem, modem to router, both PC and xbox to router
Do you use a software firewall? What brand? Have you made any changes to it? no
Operating System? windows XP SP2
Problem description? see below kaiconfig
[KaiUserConfig]
kaiUsername=[SaD]TizzO
kaiPassword=***
kaiPort=34518
kaiDeepPort=0
kaiAccept=LOCAL
kaiTimeout=NOUI
kaiNIC=0
kaiLaunch=BOTH
kaiHomebrew=OFF
kaiPAT=ON
kaiAutoLogin=ON
kaiWireless=
kaiUI=Default
Just to be clear: Kai works but..
When console is already in 'searching for game' mode, before I boot up Kai, Kai crashes when I launch it and I get the 'report error to MS?' popup.
The same happens when I launch Kai, then put my console in 'searching for game' mode. It crashes the moment I hit 'system link' on the xbox.
This happens everytime, on different orbs.
I have to keep rebooting Kai and then suddenly (sometimes after 5 mins, sometimes after 30 mins) it doesn't crash and I can play the rest of the time without problems. This happens without me changing anything.
As you can imagine, although Kai works so not a serious problem, this is getting very annoying. Hope I can be helped (maybe by changing something small in the config or something ).
TiA -tizzo |
_________________
******************************
Killing peeps since '03 |
|
|
|
DIE-HARD
Team XLink Administrator
Joined: 25 Apr 2004
Posts: 2024
Location: USA - Utah
|
Posted:
Wed Nov 03, 2004 5:44 pm |
|
Do you have more than one NIC in that PC?
Try selecting the NIC that is used to connect to the router in Kaiconfig |
_________________ XLink Kai.
GLOBAL NETWORK GAMING
DIE-HARD @ teamxlink.co.uk |
|
|
|
[SaD]TizzO
Team XLink Moderator
Joined: 21 May 2004
Posts: 1215
|
Posted:
Wed Nov 03, 2004 6:20 pm |
|
I only have one NIC. Also searched for driver updates for it.
thanks for quick reply, -tizzo |
_________________
******************************
Killing peeps since '03 |
|
|
|
DIE-HARD
Team XLink Administrator
Joined: 25 Apr 2004
Posts: 2024
Location: USA - Utah
|
Posted:
Wed Nov 03, 2004 6:29 pm |
|
|
|
|
SS-CybrPunk
Kai Enthusiast
Joined: 26 May 2004
Posts: 274
Location: USA - Florida
|
Posted:
Wed Nov 03, 2004 9:27 pm |
|
If I'm not mistaken you've had this issue for a while, right?
I'm wondering if perhaps your system didn't register the pssdk.dll file properly... That would make sense that it would crash only when the system link tunnels are established. It would also, possibly, explain why removing and re-installing the client doesn't fix this for you (I'm not sure, but I beleive I've seen you mention it as well).
I don't want to jump to conclusions here and direct you on how to unregister and re-register the DLL file - could one of the devs confirm this could be the problem? and also whether or not the regsvr32 command should be run locally from the same directory that pssdk.dll exists in? |
|
|
|
|
[SaD]TizzO
Team XLink Moderator
Joined: 21 May 2004
Posts: 1215
|
Posted:
Wed Nov 03, 2004 10:21 pm |
|
SS-CybrPunk wrote: |
If I'm not mistaken you've had this issue for a while, right?
I'm wondering if perhaps your system didn't register the pssdk.dll file properly... That would make sense that it would crash only when the system link tunnels are established. It would also, possibly, explain why removing and re-installing the client doesn't fix this for you (I'm not sure, but I beleive I've seen you mention it as well).
I don't want to jump to conclusions here and direct you on how to unregister and re-register the DLL file - could one of the devs confirm this could be the problem? and also whether or not the regsvr32 command should be run locally from the same directory that pssdk.dll exists in? |
Yeah correct, I've had this problem from the beginning of the new engine. Not with the old engine. But somehow it seems te have gotten worse after the last update (before it was now and then a crash, after it's every time).
But if it didn't register the pssdk.dll correctly, why is it that after countless kai reboots it does work?
And Diehard, yes the NIC does show up in my configfile.
-tizzo |
_________________
******************************
Killing peeps since '03 |
|
|
|
dfunked
Team XLink Administrator
Joined: 25 Apr 2004
Posts: 7005
Location: Australia - VIC
|
Posted:
Thu Nov 04, 2004 1:02 am |
|
Don't use the 'Autodetect and lock' in the Kai Config. Tool. Just select the actual NIC (that's what DIE-HARD was getting at). |
|
|
|
|
[SaD]TizzO
Team XLink Moderator
Joined: 21 May 2004
Posts: 1215
|
Posted:
Thu Nov 04, 2004 4:21 pm |
|
Quote: |
Hope I can be helped (maybe by changing something small in the config or something ). |
Ahem... am I clairvoyant? I just chose my actual NIC in the settings (after having it on Autodetect and lock and autodetect and don't lock) and this time I booted kai 5 times in a row without problems while searching for games on the console.. So I guess:
Problem Solved
Thanks for the troubles guys!
-tizzo |
_________________
******************************
Killing peeps since '03 |
|
|
|
SS-CybrPunk
Kai Enthusiast
Joined: 26 May 2004
Posts: 274
Location: USA - Florida
|
Posted:
Thu Nov 04, 2004 4:25 pm |
|
Glad to hear it. I'll admit sometimes I look too deep into things but I thought an old school Kai user like yourself would have seen this same problem in other threads. |
|
|
|
|
[SaD]TizzO
Team XLink Moderator
Joined: 21 May 2004
Posts: 1215
|
Posted:
Thu Nov 04, 2004 6:39 pm |
|
Yeah actually I did. And that's why I had selected 'Autoconfig and don't lock' right after the new engine came out.
I have never manually selected 'autoconfig and lock', but maybe this happened with an update or something.
But that's the reason I never looked into that, because I thought I had set it to 'don't lock'. |
_________________
******************************
Killing peeps since '03 |
|
|
|
|