most mapper 256 roms now outright rejected and wont play.

[negativeExponent]

Describe the bug Mapper 256, although has limited and incomplete to emulated all known variants, should be able to run some of the earlier roms, specifically those that are converted from the xxx-OneBus to NES format. Due to the strict implementation of NES 2.0's console-type header info, most of these rom now rejected and wont run (most of them are VT02)

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

(please complete the following information):

• OS and Version: [e.g. Windows 10]
• Version of FCEUX used (QT or non-QT)

Additional context Request to fallback and try to emulate said affected roms as a standar NES roms.

[frgt-srnm]

I am currently having this issue and assume it should be an easy fix... the VT02 ROMs still work if the game's NES 2.0 header is set incorrectly (i.e. the VT02 byte is changed to "normal" NES/Famicom), and the newer builds can still run VT02 images as UNIF etc. This issue should definitely be addressed in a future FCEUX version, as it's both illogical and a bit ridiculous to have to mark headers incorrectly and/or use the long-superseded UNIF format.