xboxscene.org forums

Author Topic: Homebrew Mod Concerns  (Read 29 times)

=ByTcHS|AppA=

  • Archived User
  • Newbie
  • *
  • Posts: 23
Homebrew Mod Concerns
« on: November 16, 2002, 03:52:00 AM »
Stop thinking so hard and just do it...
Logged

Scan-C

  • Archived User
  • Hero Member
  • *
  • Posts: 616
Homebrew Mod Concerns
« Reply #1 on: November 16, 2002, 07:08:00 AM »
the chip doesn't disable the tsop it overrides it.the chip overtakes anything and no "request" will ever reach the tsop so it works perfectly.but why do you think about a thing that many people already did?
Logged

svideo_man

  • Archived User
  • Newbie
  • *
  • Posts: 3
Homebrew Mod Concerns
« Reply #2 on: November 16, 2002, 10:45:00 AM »

Actually I already did the mod, and it wasn't reliable until I flash the internal TSOP and use that only.  I wouldn't boot everytime and would boot only if I press the eject buttom after power on maybe 50% of the time.  My mod has the special cap. that's mention.  So that's why I am asking this question.

If there is such a problem, then even if it works 100% it will greatly reduce the life of the mod chip, the TSOP bios and the Xbox.

Scan-C, do you know what you said for a fact in the Evox bios code or are you guessing?  I don't see how this can be done.
Logged

Scan-C

  • Archived User
  • Hero Member
  • *
  • Posts: 616
Homebrew Mod Concerns
« Reply #3 on: November 16, 2002, 10:50:00 AM »
that has nothing to do with the bios.the xbox uses the chip that it "finds" first.if the wires are to long it'll use the tsop if not the homebrew.it's just logical.
the xbox "thinks" there is only one bios and if one is found it will be used.i don't know how to explain what i mean because i'm from germany and my english is very bad.hope you understand it
Logged

svideo_man

  • Archived User
  • Newbie
  • *
  • Posts: 3
Homebrew Mod Concerns
« Reply #4 on: November 16, 2002, 11:52:00 AM »
ohmy.gif

The xbox will take a definite time period to read a byte from the bios.  Even if the trace from the mod chip is shorter, the TSOP will also be driving the bus because the xbox wait for the data to be read back;  it is design to work with the TSOP.  Therefore, there will be two active drivers on the bios bus, and that's a no no...

I am thinking the reason why it works some of the time for me, when I press the eject button, is that for some reason the TSOP won't get initialized yet and the xbox can successfully upload the whole bios into RAM from the mod chip first.

Give me some feed back people!!!
Logged

svideo_man

  • Archived User
  • Newbie
  • *
  • Posts: 3
Homebrew Mod Concerns
« Reply #5 on: November 18, 2002, 08:03:00 PM »
bumb.

So no one cares about this?!?!?
Logged

Hammy

  • Archived User
  • Hero Member
  • *
  • Posts: 1140
Homebrew Mod Concerns
« Reply #6 on: November 19, 2002, 03:05:00 AM »
jester.gif
Logged

LemmyFill

  • Archived User
  • Newbie
  • *
  • Posts: 4
Homebrew Mod Concerns
« Reply #7 on: November 19, 2002, 02:08:00 PM »
QUOTE (Hammy @ Nov 19 2002, 10:05 AM)
I have had my homebrew chip for about 12 months and i have never had a problem...

Since i did my homebrew mod about a year ago i have never had a problem with the mod...


Ummm... I'm going to guess that for about the first five months you had nothing but problems with your homebrew chip, given that the first Xbox mod chips didn't appear until May - less than seven months ago.
Logged