Hacking Will Wii dumps always be over 4 GB?

[sabinraijin]

So has anyone found a way to decrypt the ISO so that the file is only the data needed for the game? Or are we always going to be stuck with 4+ GB files, no matter how much data the game actually uses? Maybe there already is and I'm just missing something, but I've yet to see a Wii game under 4 gigs, so it got me wondering.

 

[Athlon-pv]

Early GameCube had the same problems until people ripped garbage from dumps , some dumps were smaller in size after being ripped...

 

[jaxxster]

Untill we can run unsigned code they'll always be over 4gig, If we rip stuff from the wii games im pretty sure we'll break the encryption and the wii wont reconigize the disk, Gamecube games wernt encrypted is why we can rip the garbage data from them.

 

[kristijan08]

yep jaxxster is right, if you alter the current images in anyway they wont play on current modchips!

maybe one day that will change, but yeah its annoying when you think garbage data could realistically be 3+ gigs

 

[pandas0nic]

Untill we can run unsigned code they'll always be over 4gig

Well not necasarily, being able to run unsigned code will allow booting of shrunken isos sure, but that doesent stop the distrubtion of smaller sized isos which will be possible once the actual disc fomat of a wii disk is broken and understood, taking out the padding from these images will result in the smaller sizes which can be distributed and then rebuilt with an appropiate tool which would result from the understanding of the disc structure and then just burnt back to disk. Hopefuly this will happen sometime soon.

 

[sabinraijin]

Ah, I see, so the Wii looks for all the data to be there, even garbage data that's just there to fill the DVD. Weak.

Well, as long as there's even a small chance it will be amended in the future, I'm happy. Pain in the ass to do this stuff with 768k DSL >_

 

[drz]

Here are my ignorant thoughts:

If ripping out data really doesn't work, the Wii must be looking in a few places and expecting a certain bit of data. So the size of the game must be written somewhere. To get around this, I guess you could:[*] Find out how much game data there is, rip out the padding, then write a program to recreate the padding before burning.[*] Change the size field to take up nearly the whole disc, pad the ISO with zeros (or something easily compressible), and leave the last 512KB of original padding at the end. Then you'd have a modified game disc, but you wouldn't have to break the padding encoding. Maybe.Anyone want to try either of these?

 

[ssj4android]

So, even if you change one bit in the ISO, say at 3.5 GB, the game won't work? That doesn't make any sense.

 

[ozzyzak]

So, even if you change one bit in the ISO, say at 3.5 GB, the game won't work? That doesn't make any sense.

Funny...makes sense to me.

 

[rkenshin]

Hey at least it's not bad when compared to downloading 360 isos..

DVD9 sized FTW!

 

[ssj4android]

So, even if you change one bit in the ISO, say at 3.5 GB, the game won't work? That doesn't make any sense.


Funny...makes sense to me.

The Wii can't be reading the whole disc all the time, can it? That would take forever.

 

[ozzyzak]

So, even if you change one bit in the ISO, say at 3.5 GB, the game won't work? That doesn't make any sense.


Funny...makes sense to me.

The Wii can't be reading the whole disc all the time, can it? That would take forever.

My best guess would be that changing something in the game image (ISO) would change a checksum, and if it isn't what it should be, then it won't work.

 

[Pikachu025]

It would still need to actually read the whole disk to check the checksum, if you're following me.