Exact Howto/tutorial for bin2boot?

[Soldiaz]

Hi all.

I have tried bin2boot. But i cannot handle it.

What i did so far:

- Building up an image one time with cdrecord (with/without ipins) the other time with cdrwin.
- dropping the image into bin2boot gui

Cdrecord:
says i do not have an ip.bin record..asks if i would like to insert one. Yes. Then asks for the bootfile. i typed in 1st_read.bin. Then i saw some wired chars on the screen and the program exits without building an cdi image. i tried both with ipins and without - same problem.

CDrWin:
first everything ok. i got an cdi image. When i open this image with isobuster i can see the data on the first session and on the second session there is a file that is about 600kb. Is this ok????
And of course the cdi image is not an xa/2 image..is this right ?

Does a cd made by bin2boot not contain an audio track?

[Megalexxx]

No audio track with Bin2Boot (if the original image didn't have any). It's a Data / Data format.

Try to burn the 2nd image you built with Bin2Boot, and you'll see if it works !!!

[Soldiaz]

but it seems that the game data is on the first session. Burn though?

[hrb2k]

since i'm on planetweb browser i can post here.

its real easy. you have to binhack the bootbins to lba 0. that would be the 1st_read.bin. then use mkisofs with lba 0 and IPINS the ip.bin into the .iso.

use bin2boot on the iso and it should create a .cdi image for burning with discjuggler or a120.

one downside of bin2boot is you cannot copy the cd again. some or most cd drives can't read bin2booted cd. there is an alternative way to burn stuff the bin2boot way, but this time it will let you copy the cd whenever you want to.

find and download an app called ISOFIX.

-binhack the bootbins with an ip.bin to 11700 or 11702
-mkisofs w/ the lba you used in step one. (0,11700 or 0,11702)
-IPINS the .iso w/ the same ip.bin used in step one.
-use ISOFIX on the .iso. it will ask for the lba, type it in. it will create 2 files. fixed.iso and header.iso.
-use cdrecord to burn the first session, fixed.iso and the second session, header.iso. that's right, the data files go in the first session.

cdrecord -dev=x,x,x -multi -xa1 fixed.iso
cdrecord -dev=x,x,x -eject -xa1 header.iso

substitute dev=x,x,x w/ your device numbers

how this works is that the header.iso contains the ip.bin of the data session. which means the ip.bin points back to every file in the first session. this works great if your burner cannot burn 11700 1st sessions.

hope it works for you.

[Soldiaz]

concerning on your reply the 2nd method only goes with cdrecord right?

[thursday]

i believe it will also work with another program, just burn them with the same options (multisession, xa mode 1 on both sessions)

..i havent tried it, but i will.

[hrb2k]

Originally posted by Soldiaz
concerning on your reply the 2nd method only goes with cdrecord right?

yes, i've only tried cdrecord. it works. idk about other apps.

[trig21]

Two questions:

In the first method do you need to use /nohack on bin2boot?

Won't using isofix in the second method increase the size of the file? This would cause some releases that are on the border of the 80 minutes to go over. Why couldn't you binhack to set the lba to 0 and use 0 from then on?