Everything you need to know is included in the .fds file. The registers used and whatnot aren't as important.
FDS images are a collection of "files". Each file has a header which tells where it gets loaded to and how big it is.
For Side A, files start at offset 0x0004A, and for Side B they start at offset 0x10026.
Files are layed out like so:
Code:
--------------------
03 <-- value to identify section as file header
xx <-- file number (largely unimportant)
xx <-- I forget, but again, unimportant
8-character ASCII string <-- name of file
xx xx <-- 2 byte address that file gets placed
xx xx <-- 2 byte size of file
xx <-- value to indicate whether file is PRG/CHR/NT data (unimportant, since that can be inferred from the target address)
04 <-- value to identify start of file data
... <-- file data
-------------------
If you have DDP handy... you can look at its Side A for an example. It has these files:
Code:
0-00.bin: dst: 2800 siz: 00E0 name: KYODAKU-
0-01.bin: dst: 6000 siz: 0600 name: EN-SND-D
0-02.bin: dst: 6000 siz: 8000 name: MAIN-PRO
0-03.bin: dst: B800 siz: 1900 name: ENDING-2
0-04.bin: dst: 0000 siz: 1FF0 name: TITLE-C
0-05.bin: dst: 0E00 siz: 0C00 name: ENDING-C
0-06.bin: dst: 6600 siz: 0006 name: SAVE-DAT
I just happened to have this info handy since I'm currently working on something DDP related ^^