PS1/2 Program to keep LBA from PSX .bin image after edited

[DarthMotzkus]

Hi everyone.
Can anyone point me a good ".bin image psx file editor" which won't mess up the LBA after save/export the edited .bin or .iso?
I was editing the .exe entrys via HeX Editor, inside Legend of Dragoon modded image (Blood color correction, expanded inventory, XP Share and bugfixes mods), inside the .bin file, aiming get rid of the Anti-mod splash screen wich freezes the game on my PSX consoles, even with mod-chip or un-modded console using FreePSXBoot+Tonyhax to play backups.
I found the hex line wich responsible for the anti-mod screen, edit them, save the .exe and overwrite the original .exe inside the .bin image, but when i save the image, UltraISO mess up the LBA and i get a game with no sound in FMVs, no matter how i export it, or convert, i've tried every option on it. I've already uses PowerISO, MagicIso, WinISO etc. All of them change the LBA. Anyone knows a good utility to edit the .bin image preserving the LBA structure?

 

[FAST6191]

Didn't know Legend of Dragoon was one of these games. Normally just Square Enix efforts, though given my general apathy towards this game then yeah.

"I found the hex line wich responsible for the anti-mod screen, edit them, save the .exe and overwrite the original .exe inside the .bin image"

Assuming it is in place and you are just overwriting with NOPs or something then why not find the file with a normal hex editor (for ROM hacking purposes I tended to suggest xvi32 http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm , hexplorer https://sourceforge.net/projects/hexplorer/ , hxd https://mh-nexus.de/en/hxd/ or tiny hexer https://www.softpedia.com/get/Others/Miscellaneous/tiny-hexer.shtml ).


As far as what iso fiddling tool the kids are using to prevent this from happening* I am not sure. Most times I see anything here there is a game specific tool rather than a generalist tool. Depending upon what goes you might be able to rebuild and then slice off the LBA stuff (assuming it is at the end of the disc) and put that back on at the appropriate location.


*for those not familiar. 99% of PS1 games (and PS2, not sure what goes for PS3 after its encryption) use the standard iso file format of the day (iso9660, not sure what further restrictions offhand) which is why you can plop the disc into a PC and read files from it quite happily or use basic off the shelf iso editors where you fail and need specialist tools with many other consoles. However some games go one further and do reads to areas of the disc off their own back (LBA = logical block address, basically how things are found on discs which differs slightly to the pointers you might be used to from most ROM hacking and file fiddling) that is outside what the basic iso9660 thing says it knows about. "Some games" include several Square Enix titles, and somewhat popular for game players and ROM hackers, and includes a lot of their music and video which even more people are interested in ripping.

 

[DarthMotzkus]

Didn't know Legend of Dragoon was one of these games. Normally just Square Enix efforts, though given my general apathy towards this game then yeah.

"I found the hex line wich responsible for the anti-mod screen, edit them, save the .exe and overwrite the original .exe inside the .bin image"

Assuming it is in place and you are just overwriting with NOPs or something then why not find the file with a normal hex editor (for ROM hacking purposes I tended to suggest xvi32 http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm , hexplorer https://sourceforge.net/projects/hexplorer/ , hxd https://mh-nexus.de/en/hxd/ or tiny hexer https://www.softpedia.com/get/Others/Miscellaneous/tiny-hexer.shtml ).


As far as what iso fiddling tool the kids are using to prevent this from happening* I am not sure. Most times I see anything here there is a game specific tool rather than a generalist tool. Depending upon what goes you might be able to rebuild and then slice off the LBA stuff (assuming it is at the end of the disc) and put that back on at the appropriate location.


*for those not familiar. 99% of PS1 games (and PS2, not sure what goes for PS3 after its encryption) use the standard iso file format of the day (iso9660, not sure what further restrictions offhand) which is why you can plop the disc into a PC and read files from it quite happily or use basic off the shelf iso editors where you fail and need specialist tools with many other consoles. However some games go one further and do reads to areas of the disc off their own back (LBA = logical block address, basically how things are found on discs which differs slightly to the pointers you might be used to from most ROM hacking and file fiddling) that is outside what the basic iso9660 thing says it knows about. "Some games" include several Square Enix titles, and somewhat popular for game players and ROM hackers, and includes a lot of their music and video which even more people are interested in ripping.

Thanks for the reply.
Did any of these utilities you mentioned can acess the .exe inside a .bin image of psx title? Can you explain me how to? I need to access the .exe file, search for the "3741C" offset and zero 12 bytes forward and save. Opening the .bin image in a hex editor cannot find the same offset of the .exe, i don't know if it's because is package into a .bin file or something. I need to edit the inside .exe file of it.

 

[FAST6191]

Thanks for the reply.
Did any of these utilities you mentioned can acess the .exe inside a .bin image of psx title? Can you explain me how to? I need to access the .exe file, search for the "3741C" offset and zero 12 bytes forward and save. Opening the .bin image in a hex editor cannot find the same offset of the .exe, i don't know if it's because is package into a .bin file or something. I need to edit the inside .exe file of it.

I doubt any of them are are is9660 aware out of the box, might be some plugins for some though. Your iso editor might also say the location within the file.
All of those editors should have a search option though so if you open the iso the iso editor, browse to the file you want and then look at the data around what you have to edit you should be able to use that as a search* in the normal hex editor to find the location.

*think the equivalent of me giving you a quote from a book, you then having a word document with that in and pressing ctrl f to find the quote and surrounding text. Most things that are not 00 or FF and are more than about 6 bytes long will be unique in most files, and you can also compare it to the iso editor hex viewer/file from the iso editor to see if the data immediately before and after matches what you want.

This sort of thing becomes tricky if you start to edit text which usually makes things longer and shorter than the original but for most edits of a binary to stop it from doing something, change the amount it gives you or similar tend to be what is called "in place" editing where you don't change the length of things and thus you have that as an option here.

 

[DarthMotzkus]

I doubt any of them are are is9660 aware out of the box, might be some plugins for some though. Your iso editor might also say the location within the file.
All of those editors should have a search option though so if you open the iso the iso editor, browse to the file you want and then look at the data around what you have to edit you should be able to use that as a search* in the normal hex editor to find the location.

*think the equivalent of me giving you a quote from a book, you then having a word document with that in and pressing ctrl f to find the quote and surrounding text. Most things that are not 00 or FF and are more than about 6 bytes long will be unique in most files, and you can also compare it to the iso editor hex viewer/file from the iso editor to see if the data immediately before and after matches what you want.

This sort of thing becomes tricky if you start to edit text which usually makes things longer and shorter than the original but for most edits of a binary to stop it from doing something, change the amount it gives you or similar tend to be what is called "in place" editing where you don't change the length of things and thus you have that as an option here.

That's it man, thank you so much. It's more simply than i imagined, i just open the .bin file in hex editor, find the string i have to edit, and replace the values, save it, BANG! No anti-mod screen anymore, neither FMV sound issue.