If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
What exactly did he disable all the checks are still their in little endian
And...? lh/lhu and lw are supposed to read data in little endian order, that's how the r3000 works. When you represent a number there's no endianness, it's just a number, no matter the way it's stored.
Wes67's 1.5 rebuilder also re-calculate checksums, but when I was testing it months ago, I noticed that this was not sufficient to mod some files like CDEMD0.EMS, CDEMD1.EMS and ITPS.ITP, so only way was to disable the checksums, otherwise the game just crash...
Hey Mark, I just notice Disc Smasher don't update correctly some values in the table of the files of the 1.5 EXE, I discover this because I try to rebuild 1.5 with all my hacked files I have and the game crash in Character Select Screen. Obviously is not problem of checksums because they are deactivated.
I just want to report it, so you can fix it when you have the time.
It'll also include files which aren't listed in the filelist.txt, it doesn't restrict to the specified files it'll include all files within a folder, I noticed this when I had a .rar backup of some files in stage4 it included the .rar an messed up the following stage5 & 6 file positions. Dark Biohazard was it room302 onwards that had messed up positions?
Can you also add support so it adds autocalculated filesize values rather than
real filesizes, so we can reinsert slightly bigger files later with cdmage without having to rebuild the whole image again.
Can you also add support so it adds autocalculated filesize values rather than
real filesizes, so we can reinsert slightly bigger files later with cdmage without having to rebuild the whole image again.
If a file/size is changed, the ISO has to be rebuilt again. There's simply no way around it, it's just the way CAPCOM's fpos structure is read to work properly.
If I padded the values, it could cause data within RAM to be overwritten, and will likely crash the game on real hardware.
It's a nice idea, and I've thought of it before, myself... I'm sorry, but no cigar.
Comment