Post by: Akkr on April 01, 2003, 01:17:00 AM
I am now using Tat Debug 512k only.
On C I replaced the 1.3285 evox dashboard ( which didn't allow the XBox to be on the network with the Tat Bios ) by the 1.2812. I now can ping and use xbcopy with Tat.
On E:, I added xbdm.dll,dashboard.xbx,tdata that comes from the Recovery Disk of the Feb2003 SDK
I put the dir Devkit from the Recovery Disk to E:DevKit
On C:, I didn't put anything that comes from the Recovery Disk.
And I still cannot debug remotely from VC Net, the error message is operation not handled... Am I missing something ?
Thanks for those who gave me some hint by private messages.
Post by: BenJeremy on April 01, 2003, 03:28:00 AM
| QUOTE (Akkr @ Apr 1 2003, 05:17 AM) |
| I made some progress, but I still don't get it. I am now using Tat Debug 512k only. On C I replaced the 1.3285 evox dashboard ( which didn't allow the XBox to be on the network with the Tat Bios ) by the 1.2812. I now can ping and use xbcopy with Tat. On E:, I added xbdm.dll,dashboard.xbx,tdata that comes from the Recovery Disk of the Feb2003 SDK I put the dir Devkit from the Recovery Disk to E:DevKit On C:, I didn't put anything that comes from the Recovery Disk. And I still cannot debug remotely from VC Net, the error message is operation not handled... Am I missing something ? Thanks for those who gave me some hint by private messages. |
Try using the normal M$ Xbox dashboard software.
This is what I use in debugging.
Post by: Akkr on April 02, 2003, 11:19:00 PM
So the only thing I was missing was the Xbox Debug Kit dashboard on the Xbox, which seems to allow Visual .Net to connect correctly to the XBox. In the same time I switch to the latest EvoX dashboard, but it is not used when I boot with TAT.
Thanks to everyone who answered me publicly and privately. I am already in Visual coding, porting some stuffs to XBox
