xboxscene.org forums
OG Xbox Forums => No-Modchip Hacks (exploits) => XBE Exploits => Topic started by: K-Naledge on July 04, 2003, 09:16:00 PM
-
Sorry if I appear not to be reading into this as much as other dedicated folks... X-Box isn't my thing. I jsut keep up on the "scene" (cross-consoles) as my thing was/is Dreamcast (I was pretty up there in the DC hacking days..)
So, here is my thought. Simple:
So if the Free-X compilation forces an integer underflow (as people constantly mis-label it an OVERflow.... it isn't overflowing... it's creating MASSIVE headroom. If it OVERflowed, the box would either crash or disallow even more occupancy...as what's there left for room to OVERflow? Thus.. it underflows.. this is clearly stated in the Free-X docs...but I digress...)
Again... forces underflow...cut to now... it leaves approxiamtely (as stated..) ~4.0xGB of headroom for multiple/single XBE load-ins... So... wouldn't it be just as easy for MS to make the standard for game development (as they hold all publishing rights) to "bloat" title tracks,etc to be OVER 4.0xGB ? This is very similar to the Dreamcast GD-ROM methods employed by Sega as a hack-job tactic to relinquish copying of games straight up (that and the fact you had to polar-reverse the cd spindle for reading... etc.)
So... any thoughts on this? I'd like to see this topic expand on any down falls to the Free-X system. Not to bash it... but to cover any ground that may not have been covered already. This is simply a stepping stone. None one said (which I think a lot of the scene is missing right now...) that this is a CLOSED source file we're working with... And I don't mean "DUH we just build off the existing Free-X sources and such LOLxroz!" I'm saying everyone should realize we can BETTER he EXISTING code from scratch... like as a guide to what is happening.. *I smell boot disk*
Peace, K-Naledge.
-
I'm being serious... I mean come on.. somebody SOMEWHERE has to have some insight on this issue hehe.... PLEASE?!
-
I'm very impressed that you can restate what's already been said.
-
My thought is you should have some patience like everyone else or start tinkering & share your findings.
-
Yeah. You all as in you? Why not post a link to the thread that you claim has already been started. It's a pretty obvious topic, but if you noticed, I also stated this should become a topic for possible downfalls. Everyone seems to be focusing on what CAN we do with this exploit. Anyone knows the bext way to hack an exploit is to figure out how it can be defeated. Then... figure out WHY and WHAT... and bingo.... you have a stable way to kee this project up and running. Asshat.
/rant
Oh and BE PATIENT WITH WHAT??? lol
All I said was that a possible DEFEAT to this is the bloating of certain files.... ffs. Did I even ASK about backups? WHEN WHERE? HOW??? no.
Ah thank you.
-
No, thank you.