Binhack - What changes does it make?

[darklegion]

Just wondering what binhack does so I can modify the files manually without having to use binhack (I use linux).I am pretty sure that as far as the bootfiles go it just changes the lba to the msinfo value,but are there any changes to the ip.bin? I would think that there would be since it asks for an ip.bin,but what are these changes exactly? Also I am just wondering what certain booting problems indicate such as:
1.Constanly resetting dc after sega logo
2.Jump back to dashboard
3.Wierd laser noises

Knowing what these mean could help figure out where mistakes are being made

Oh and 1 more question,I have come to assume that isofix does not do any binhacking it just pads the data up to the same lba that it originally used when it was originally in audio/data form....is this correct?

Thanks

[darklegion]

Figured it out myself Binhack only seems to hexedit 1st_read.bin,no changes are made to the ip.bin file from what I can tell.Also ipins is no longer needed with newer versions of mkisofs....you can just use the '-G ip.bin' when building the iso.

[hrb2k]

thanx for that info about mkisofs. i dont have the latest version, so what version do you use?

as for your questions about resets.

1. it means an lba is wrong in one of the bootbins. some games have multiple files you have to binhack, not just 1st_read.bin. do a search for files containing text, CD001. 2 bins have this if the game has a web browser. maigo and sg_dpldr.bin, dont bin hack those.

2. no ip.bin, or unhacked ip.bin. ppl say that you dont have to binhack . but just to be safe, always binhack.

3. bad media? hot DC?

[darklegion]

I use the latest version of cdrtools(mkisofs,cdrecord,readcd etc ) compiled from source on debian linux.I think this option has been around a while however..the version that comes with the echelon kit and similar tools is badly outdated.There are a few things to look out for when using newer cdrecord though,since there has been some changes..i.e use -xa instead of -xa1.Also I noticed that people around here input -C 0,0 when doing a data/data disc ...it is not needed since it is the first session and will start at lba 0 by default

1.Yes I worked that one out
2.The reason I would rather avoid binhack is that it requires me to boot into vmware(a virtual machine prog),which is somewhat annoying and I don't want to have to rely on vmware.From what I can tell only utopia and original ip.bins are needed to be hacked and that the lba is not important here either.I could just use a pre-hacked ip.bin in any case.
3.Laser works fine,but tends to make certain sounds which indicate a badly created discs at times..hard to figure out really as I haven't been able to replicate it recently(must be doing something right then : ) )

Also where can I get hold of dahack,hack2,hack3 etc ? I might be able to use those instead,if they can be run under wine(windows compatability layer)..

Thanks

[Megalexxx]

Binhack changes LBA value in 1st_read.bin.
But it also rewrites a part of ip.bin.
Don't trust me ?
Try to insert a logo and then binhack ip.bin...

[darklegion]

Okay then...what exactly does it change? As I would like to know And does this relate to the chosen LBA or is it just something selfbooting related that is no required when re-selfbooting?

Also megalexxx,any chance of support for non-cdi based images in pal patcher? Just plain iso images or the ability to search a directory of files would be enough.

[hrb2k]

i think binhack creates its own ip.bin with header info from the ip.bin you hack with. try to hack a bootbin without an ip.bin. if i recall, binhack makes one for you, and if it exists, will overwrite your ip.bin. thats why inserted images are gone.

just use upx.exe to unpack it and open that in a hex editor. you'll see the whole ip.bin structure in the unpacked exe.

[darklegion]

Okay makes sense and proves its not necessary : ) I also did a file compare between a LBA 11700 binhacked ip.bin and a lba 11702 binhacked ip.bin and there was no difference between the two.

[DrEaMpLaY]

Originally Posted by darklegion

Okay makes sense and proves its not necessary : ) I also did a file compare between a LBA 11700 binhacked ip.bin and a lba 11702 binhacked ip.bin and there was no difference between the two.

Yes, its true. I tried to reselfboot game that uses bins hacked on 11700 with new LBA at 11702 - an it working perfectly. This 2 points of LBA are differences between burners (one makes LBA at 11700 other at 11702. BTW: I used about 50 my fried new burners from store and always I had 11702 - I never started at LBA = 11700.

Originally Posted by hrb2k

i think binhack creates its own ip.bin with header info from the ip.bin you hack with. try to hack a bootbin without an ip.bin. if i recall, binhack makes one for you, and if it exists, will overwrite your ip.bin. thats why inserted images are gone.

I agree with You hrb2k (ps. Its me - Leclerk ugh.. Pavlik

But binhack is changing more than olny LBA points in our bootbin. Tool also scramble bins - I tried run binhacked bins (with LBA=0) form games on web browser or dream passport / key. Binhacked binaries (I talking about normal katana games) resets the browser to bios menu. Note that I used non-selfboot method (Mode 1) and unscrambled bin working great. Do You know how can I convert scrambled bins to run with non-selfboot game collection?

Next. Some bins are different and they cant be properly binhacked (e.g. Border Down - You must manually hack bins with hex editor), and I founded some some selfboot images with unscrambled bootbins!! (e.g Action Replay).

For the end I have question for You hrb2k about selfbooting/reselfbooting WinCE Games. I cant binhack the bootbins - I have right?