Help With Xbox V1.0 And Spidergx Needed Options

[G3CSGnetwork]

I have a V1.0 and am trying to add in the SpiderGX. I have it in place with the pogo pins, as the xbox dash comes up, but I can't get the LED to light up on the SpiderWire PCB. Also, the kit came with an extra red/black 2-pin cable which is seemingly unused. The D0 wire seems to be firmly in the via it belongs (going by the pictures from spiderGX.com and Hack's website), but I never see the SpiderOS screen. Any suggestions would be welcome advice. Also, should anything else be connected to the switch PCB besides the black-bunched header cable? Thanks. =)

Gene3

[Bmx_rider]

i am in the same boat as u. i dont kno if we need the red and black 2 pin wires and my dashboard wont come on. my xbox reboots 3 times and i cant seem to get it goin. i cut all the wires but one like the tutorial said to do and it still dont work. and i got a version 1.2 or 1.3 xbox which sucks cuz im not 100% sure where the D0 pin goes. but i followed the tutorial, and i think i got it in right, but it still doesnt work. so i dont kno what else to do.

[smdtherock]

i cut all the wires but one like the tutorial said to do

it says cut one wire not all but one.

[HackDaBox]

Forget the Red and Black cable ... its not needed at all , it's for adding leds to light up your xbox !

You only need one leg ( d0 ) for old consoles , cut off all the others !

V1.6 consoles need all the legs don't cut off any !

It sounds like your chips are not aligned properly on the LPC bus !

HackDaBox !

[nohbudi]

Forget the Red and Black cable ... its not needed at all , it's for adding leds to light up your xbox !

You only need one leg ( d0 ) for old consoles , cut off all the others !

V1.6 consoles need all the legs don't cut off any !

It sounds like your chips are not aligned properly on the LPC bus !

HackDaBox !

I've been on this for the past day now, and I went from nothing, going straight to the m$ dashboard, to finally getting it to power up. However, I'm getting the 3 boot frag. I even went as far as to re-flow the solder points in my LPC. I have a v1.0 box just like the original poster. I have verified that the box still works properly with the chip set to off. Unfortunately, It would seem as if the board itself is so poorly designed that I am physically incapable of getting the pogos to actually line up correctly with the LPC....

Any input would be greatly appreciated.... should have just ponied up the extra 10 bux for the xecuter.... grrr

[Bmx_rider]

ive lined my chip up properly, but i still get the 3 times reboot error. even when i press on the chip, it still gets the error. could it be that i'm pluging it in the wrong hole? or is my motherboard just not accepting the chip?how could i fix this probem?

[smdtherock]

don't you cut the green one like it says in the spidergx tutorial/> if not thats my problem

[HackDaBox]

it says cut one wire not all but one.

No you are wrong ! the original poster and other guys in here have a xbox motherboard V1.0 on that model only one wire ( d0 ) is needed !

HackDaBox !

don't you cut the green one like it says in the spidergx tutorial/> if not thats my problem

What xbox motherboard do you have ?

If you have a V1.0 - V1.5 then you only need one spider wire leg !

If you have a V1.6 - V1.6b then you need all the spider wire legs !

check out my Spider GX install guide it's much easier to understand than the orginal manual !

HackDaBox !

[orlandu]

What xbox motherboard do you have ?

If you have a V1.0 - V1.5 then you only need one spider wire leg !

If you have a V1.6 - V1.6b then you need all the spider wire legs !

The Spider PCB comes with 6 wires, one of which should be cut for 1.6-1.6b (the "green" D0). Unless they've redesigned!

BTW I seem to be able to load apps fine now I've modified those values in xconfig.ini, I will try to test the various combinations of 1s and 0s this weekend to see which makes the difference.

Incidentally, one retail game which shows the loading problem is the original Halo. If you boot with the chip enabled (and the xconfig.ini unmodified), on my console it won't launch the demo videos of the other games that are on the disk - it freezes on a black screen. The problem is fixed by modifying xconfig.ini (or disabling the chip and booting through the original BIOS and dash). So it's not just homebrew etc. on the HD that can be affected.

[HackDaBox]

Orlandu good to hear from you !

No they haven't changed anything and thats what i am saying cut the green wire for V1.6 or just keep the green and cut all the red if you have a V1.0 - V1.5 - This isn't really that hard to understand !

Thanks for the info on the original HALO game , Please try changing different values and let us know which value really needs to be changed. Its proberly just one value like live blocking or IGR that really needs to be a 0 and not all of them !

HackDaBox !

[orlandu]

Thanks for the info on the original HALO game , Please try changing different values and let us know which value really needs to be changed. Its proberly just one value like live blocking or IGR that really needs to be a 0 and not all of them !

I've tried a lot of combinations, and the value that seems to make the difference is:

; display flubber anim
doStartupAnimation = N

If N=1, XBEs don't boot. If N=0, they run fine. IGR and live blocking values don't make any difference.

This seems a bit odd, but remember when I was playing with the EvoX BIOS? XBEs would run from the dash only if I rebooted from the menu first - which didn't display the flubber animation on the subsequent boot.

Quite why the flubber animation would prevent XBEs from running is well beyond me, that's for more knowledgeable folk such as you to explain

One final note - none of these adjustments will allow me to access the demo videos in Halo (original release, PAL version). Only booting with the chip disabled makes the vids work.

[HackDaBox]

Great stuff,

Thanks for the info ... Have you tried running the demos in halo with all the IGR and ANIMATION off ? if not please give it a try !

HackDaBox !

This post has been edited by HackDaBox: Dec 12 2005, 12:45 AM

[orlandu]

Great stuff,

Thanks for the info ... Have you tried running the demos in halo with all the IGR and ANIMATION off ? if not please give it a try !

HackDaBox !

I haven't been able to get the Halo demos running with any combination of settings, including the IGR and animation disabled. Also, no combination of settings will allow me to get back to the dashboard from an application (for example, the Xport emulators), and no applications will launch from XBMC if I've played any music/video before trying to launch them.

The Halo demos I can run if I disable the chip. I can always power cycle the machine to get back to the dash from an application, so I don't have anything I can't run at all!

[HackDaBox]

What dashboard are you using ? Evox ? XBMC ?

If your using Evox then please try XBMC or UnleashX and see if that helps as this sounds like a memory resident ( TSR ) problem !

HackDaBox !

This post has been edited by HackDaBox: Dec 15 2005, 10:01 PM