HaloMods "Classic" Read-only Archive

Okay while grabbing for the first time , Thanks to Eaton, the con files off my hdd i noticed that while i had xsata plugged, the update wasn't loaded, my idea was simply this and once again an idea:

What if somehow the update could be edited (i believe it is a game addon con file) with very advanced and probably unheard off amounts of editing to make another update, that would let unsigned con files be run. I know what i am saying here and how much of a strech this sounds but i thought i might a least put my two cents in with the modding since i am at least a member on the forums.

quoting the human torch "Flame on"

Impossible... We couldn't even Sign the Updates, Since they are in an PIRS container.

CompKronos wrote:Okay while grabbing for the first time , Thanks to Eaton, the con files off my hdd i noticed that while i had xsata plugged, the update wasn't loaded, my idea was simply this and once again an idea:

What if somehow the update could be edited (i believe it is a game addon con file) with very advanced and probably unheard off amounts of editing to make another update, that would let unsigned con files be run. I know what i am saying here and how much of a strech this sounds but i thought i might a least put my two cents in with the modding since i am at least a member on the forums.

quoting the human torch "Flame on"

The update wasn't loaded because when the xsata is in the hdd, it won't work on the 360. Only one device can have control of a hard-drive because if two devices were trying to control a hdd, then it could cause read/write errors.

which would be my point because first off it owuld make sure that no one could try to use mods online (of course we still can't mod those yet) and then if we could develope a PIRS resigner then maybe it would be possible to change some of the functions of halo 3.

the idea in action would be computer connected to xbox to prevent XBL, memory card with h4ck3d update on it. Halo 3 runs the memory card as storage media which then fnds the update runs that which enables the unsigned CON files mmmh? (as i type i am hex editing a PIRS file)

Plus Im fairly certain *99.9999%* that the Halo 3 update doesnt control what can and cannot load in Halo 3, especially CON files, thats an Xbox thing, not 360 thing

And a PIRS resigner is near impossible, the key(s) arent stored on your xbox, they are stored on microsoft servers

Well ill keep thinking but if anyone else has any ideas based on any shred of reality (look at mine) feel free to post. Who knows maybe one might work oh and thanks for the comments they were quite informative

I'm glad the Xplorer I posted worked for you. Good idea, but it would probably be hard to implement.

To be honest, CompKronos, this idea is ridiculous and far-fetched. It is not going to happen.

VenomousFire wrote:the key(s) arent stored on your xbox, they are stored on microsoft servers

Lol.

If they're microsoft, they're obtainable

VenomousFire wrote:they are stored on microsoft servers

I'm 99.9% sure it's not even on a M$ server. I'm pretty sure that it's on a computer which has no network connections.

haxalot88 wrote:

VenomousFire wrote:they are stored on microsoft servers

I'm 99.9% sure it's not even on a M$ server. I'm pretty sure that it's on a computer which has no network connections.

And you base this on what, exactly?

Map file private keys are stored on a computer(that anyone at Bungie has access to) that is on the Bungie network, that is simply protected by a firewall.
I know that for a fact.

hmm this is actually intresting, shadow_lag was able to use xsata while his xbox was on... so he could edit things on his hdd...

I doubt halo 3 has cache files though

VenomousFire wrote:And a PIRS resigner is near impossible, the key(s) arent stored on your xbox, they are stored on microsoft servers

Right, and even if you could resign the container that the update was in, you would then have to resign the XEX file of the update (I'm assuming 360 title autoupdates work like xbox1 title autoupdates).

VenomousFire wrote:Plus Im fairly certain *99.9999%* that the Halo 3 update doesnt control what can and cannot load in Halo 3, especially CON files, thats an Xbox thing, not 360 thing

And a PIRS resigner is near impossible, the key(s) arent stored on your xbox, they are stored on microsoft servers

Actually they appear to be in some computer inside microsoft, the authoring method for xbox 360 games is the following.

You submit the game/update/dlc with XLAST, it basically sends them build information and I think a game build, if MS approves it creates the file locally and then sends it (kind of like an iso) to the manufacturing plant where games are burned. Or if its an update its sent to xbox live servers..

This is mostly assumption but is some what sustained by facts..

latinomodder wrote:I doubt halo 3 has cache files though

On the contrary; Halo 3 stores recent gametypes, map variants, and films in a cache.

At least, that's how I remember it. Correct me if I'm wrong, but I'm pretty sure Halo 3 has cache files.

Yes I believe it does, you just can't edit it, because it checks the map signature before you start the game, aswell as after... So when you tried to start the map you were just playing, it wouldn't load.

And editting the cache while your playing it wouldn't work in Real Time ;x...