I think I've found several bytes in the rom that aren't used, but I want to be absolutely sure.  I was wondering two things:

1.  I thought there was a way to track a range of bytes in fceuxdsp v1.07, but I can't remember how.  Does anyone else know?

2.  What would you say is the quickest and easiest way to look for unused bytes would be?

Are you looking for stuff in the rom file or for stuff in ram?

If the latter...you really have to play and take your chances. However, many games will initialize all ram they ever use, so you might get lucky when you take a look at the boot-up routine.
Also, if you look for stuff in roms, you could try to understand the assembly insomuch that you know how the game reads data.

• (if the game uses banking) from another bank
• in its own bank

[(if the game doesn't use banking) from far reads of data. these will most likely be aligned so the game can use speedier reads compared to single-byte reads.[/li][/list].

Also, in games that don't use banking, you will usually find unused space all in the same corner and only here and there to fill space for aligning data.

I think your game will most likely be using banking, so you might want to read up on asm and specific adressing modes if you haven't already.

cYa,

Tauwasser

If it's in the ROM, try looking for an extremely long series of $00s or $FFs.  That's what unused bytes usually look like on the NES.

Another way to track bytes is to open the debugger and set a READ breakpoint over a range of bytes.  Then play through the game.  If those bytes are ever used(ie, read) the game will stop.