|
it sounds more like a missconfiguration problem to me, i've used evox all along since i moded my first xbox and i never had that problem, try this, set up your network card on your computer to use 192.168.2.1, the connect the crossedover cable to the xbox, after you connect the cable, turn your xbox on and go to the configuration screen (i really havent use other dashboard than evox or avalaunch, but i always configure evox and avalaunch gets the configuration right away, on your configuration screen scroll down to the part where it says "use static" and hit YES otherwise evox WON'T save the setting no matter what you input, after you set use static to yes, then (an just then, not before, enter your xbox ip address, lets make it 192.168.2.2, subnetmask on both must be 255.255.255.0, gateway, dns and all other stuff doesn't matter since you are only connecting your xbox locally over a crossover cable so, i wouldn't bother to enter all that stuff, then save your settings, and reboot your xbox, that should do the trick.
after that, try pinging your xbox, (windows xp: start, run, cmd (enter), ping 192.168.2.2 and see if it replies, the reason why evox always gives 0.0.0.0 its because:
1.- you connected your cable AFTER turning on the xbox, and not before
2.- you skiped the step about set your ip address to "use static" and always tries to get ip from dhcp server (which doesn't even exist)
i hope that might help.
|