same problem. so many theories. no solutions.
more of me thinking on the problem.
are we digging to deep. what if they are just scanning the eeprom itself. granted, this theory and the popular opinion are very similiar. but what if they are scanning the eeprom, and looking for ANY changes. after taking a look at config magic and even learning what an eeprom is, i found it stores this info as most already know.
kernal version
ram
xbox serial
xbox mac
online key
video mode
xbe region
hdd key
confounder (whatever that is, if someone knows, fill me. i'm trying to learn here)
hdd model
hdd serial
hdd password
dvd model.
so if they are basically looking for hardware changes, and they did a previous scan of the eeprom, couldnt they just look for a change in the hdd model and serial there, as well as the dvd model (since some have claimed thats all they changed). this seems like it would be easier than scanning harddrives. and still supports the "marrying" of hdd and eeprom.
my next worry is, say they skip storing the database info on the hdd itself. all they would really need to do is store the last eeprom data it received on particulcar xbox serial number. then if that xbox serial signed on again, it could then cross reference the stored eeprom data on that serial, and then issue the ban since the eeproms wouldnt match.
just a matter of when the intial scan was.
i know some of this is redundant, but a different way at looking at HOW they got the info.
Author
Topic: Maybe Thinking Too Complicated? (Read 73 times)