xboxscene.org forums

OG Xbox Forums => Xbox Online Gaming (Xbox Live, Xlink, and others) => Xbox Live - Online Gaming Service => Topic started by: indotoonster on January 17, 2003, 04:16:00 AM

Title: Xbl & All Possibly Detected Traces Of Modding...
Post by: indotoonster on January 17, 2003, 04:16:00 AM
OK, here's a question that really is one grounded in paranoia: I've checked out a whole lot of posts on the separate issues involved, but I'm thinking of a more general issue of: given a particular Xbox setup, is there possibly any sort of detectable giveaway signal to Xbox Live that there is something simply not kosher about it? From what I can gather, if one did the following steps:

1) turned off their modchip (i.e. load original BIOS),
2) locked their custom HD, and
3) never touched C:\xboxdash.xbe,
then for all intents and purposes the Xbox should be ''legit'' right?

This is what the consensus seems to be, but being my paranoid self, here is a list of possible signs that I can think of, relating to the 3 steps above:

1) When a modchip is installed but disabled, e.g. using an external switch or in the case of Matrix possibly using Mode 3, is it still technically possible to detect its presence? I read rumours of detecting that it still draws electrical current and whatnot -- how much truth is in this?

2) When installing a bigger HD, the new HD key to lock it is generated based on region/serial no./HD hardware - could MS possibly run a check on this key to see that, although it's a valid one, it was generated for a HD that wasn't a retail one? Perhaps through some factorization?

3) OK this is perhaps the most solvable one -- we use a yboxdash/evoxdash solution -- but surely MS can detect the presence of *any* foreign looking files on C:. So I suppose the truly paranoid among us can choose to never put any file on C: -- set the BIOS to boot from F: instead.

Does anyone have any other paranoid possibilities to add to this list? Or solid technical info that dispels any of the above?

cheers,
indotoonster