The odd thing is that the everything works fine in FCEUX, but Nestopia has an issue.
From DvD:
From DvD:
Quote:
I have a problem when I expand the files on the 2nd side of the 2nd disk of BodyConQuest I.
Here's a partial file dump. All addresses and the file are are w/o an FDS header:
------------------------------------------------------------------------------------------------------------------------------------
BLOCK ID NUMBER ID CODE NAME ADDRESS LENGTH TYPE FDS/NES RAM .fds FILE BLOCK ID
**Last 2 Original Files on Disk 2 Side B**
...
03:FILE HEADER 23 37 "BOSSPDAT" DFA0 0007 00 PRAM: Program dfa0-dfa6 3c4c2-3c4c8 04:FILE DATA
03:FILE HEADER 24 37 "BOSSKDAT" DFC0 001C 00 PRAM: Program dfc0-dfdb 3c4da-3c4f5 04:FILE DATA
EMPTY SPACE 00 00 00 00 00 00 00 00 00 00 00 00 3A7A 3c4f6-3ff6f
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
**New 4 Files on Disk 2 Side B**
3C4F6 (Header)
03:FILE HEADER 25 36 "SERI2MSG" BB03 0280 00 PRAM: Program bb03-bd82 3c507-3c786 04:FILE DATA
3c787
03:FILE HEADER 26 33 "KENJ2MSG" BB96 0380 00 PRAM: Program bb96-bf15 3c798-3cb17 04:FILE DATA
3cb18
03:FILE HEADER 28 31 "ROUR2MSG" BBFA 0300 00 PRAM: Program bbfa-bef9 3cb29-3ce28 04:FILE DATA
3ce29
03:FILE HEADER 29 35 "RYUO2MSG" BC06 0300 00 PRAM: Program bc06-bf05 3ce3a-3d139 04:FILE DATA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For some reason it only loads up bytes up to 3ce70, 3ce71, or 3ce72. I can't tell exactly which of these 3 bytes since the last 2
are a line break and a space.
If I make SERI2MSG, KENJ2MSG, or ROUR2MSG 80(hex) bytes longer, then when trying to load RYUO2MSG you get an error 24; it can't
find the header for RYUO2MSG. With the files the size they are, it doesn't error, it just doesn't write over any byte past the
one's I listed above.
I just always seems to not be able to read beyond this byte. It's such a random amount. It doesn't seem to be any power of 2 from
anyhwere.
Here's a partial file dump. All addresses and the file are are w/o an FDS header:
------------------------------------------------------------------------------------------------------------------------------------
BLOCK ID NUMBER ID CODE NAME ADDRESS LENGTH TYPE FDS/NES RAM .fds FILE BLOCK ID
**Last 2 Original Files on Disk 2 Side B**
...
03:FILE HEADER 23 37 "BOSSPDAT" DFA0 0007 00 PRAM: Program dfa0-dfa6 3c4c2-3c4c8 04:FILE DATA
03:FILE HEADER 24 37 "BOSSKDAT" DFC0 001C 00 PRAM: Program dfc0-dfdb 3c4da-3c4f5 04:FILE DATA
EMPTY SPACE 00 00 00 00 00 00 00 00 00 00 00 00 3A7A 3c4f6-3ff6f
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
**New 4 Files on Disk 2 Side B**
3C4F6 (Header)
03:FILE HEADER 25 36 "SERI2MSG" BB03 0280 00 PRAM: Program bb03-bd82 3c507-3c786 04:FILE DATA
3c787
03:FILE HEADER 26 33 "KENJ2MSG" BB96 0380 00 PRAM: Program bb96-bf15 3c798-3cb17 04:FILE DATA
3cb18
03:FILE HEADER 28 31 "ROUR2MSG" BBFA 0300 00 PRAM: Program bbfa-bef9 3cb29-3ce28 04:FILE DATA
3ce29
03:FILE HEADER 29 35 "RYUO2MSG" BC06 0300 00 PRAM: Program bc06-bf05 3ce3a-3d139 04:FILE DATA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For some reason it only loads up bytes up to 3ce70, 3ce71, or 3ce72. I can't tell exactly which of these 3 bytes since the last 2
are a line break and a space.
If I make SERI2MSG, KENJ2MSG, or ROUR2MSG 80(hex) bytes longer, then when trying to load RYUO2MSG you get an error 24; it can't
find the header for RYUO2MSG. With the files the size they are, it doesn't error, it just doesn't write over any byte past the
one's I listed above.
I just always seems to not be able to read beyond this byte. It's such a random amount. It doesn't seem to be any power of 2 from
anyhwere.