Print

[BenJeremy]

QUOTE (OUberLord @ Aug 12 2003, 09:28 PM)

Hi all, Heres the problem.  I work at WorthPlaying.com, and do Xbox reviews and previews.  While doing so, in the past I used a debug bios (I believe TATX) and placed XBDM.dll in the E drive, so that I could use Xbox Neighborhood to take screenshots of Xbox games at any time. However, all of a sudden I cannot take screens any more.  When the box is running the TATX bios I cannot even ping the Xbox, and Xbox Neighborhood cannot reach it.  However, if I turn the box off, switch the bios to X2, and boot up EvoX I can ping the xbox successfully using the same IP. To take screens, you just need TATX and the XBDM.dll file in the /E/ root right?  Or am I missing something, some setting or file placement?  It sounds like a network problem, but I know it isnt the network hardware because the same hardware works fine with the X2 bios. XDK 5558 Reg BIOS: X2 4976.02 Debug BIOS: TATX Any help is appreciated.

Your DEBUG IP has changed (Debug IP defaults to DHCP served). Do what I do.... keep trying successive IPs in Xbox Neighborhood until it accepts one.

If you were running XDK Launcher as a dashboard, you would be able to tell exactly what the IP is.

[OUberLord]

Fixed the problem.  I ran a network scanner to find the IP, which did in fact change.  Also, I found that the IP is closed at certain points, namely when the game is cahcing stuff to the HD like some games do immediately upon boot.

[Wishi]

Even when my IP changes my Xbox Neighborhood is fine as I have set up a name for it in the Launcher which I use instead of the IP.

[Mage]

You can set it to be a static ip also, I prefer it that way instead, so you always know the ip.