Totally unrelated to that other one post, I'm sure... Mr EM3/SS...
It's likely to be a proprietary format, with no reader available. That means you need to figure out the format for yourself, and write your own translator. This takes work and smarts, so if you can't do that, don't bother.
The way to figure out the format is to change a byte in, say, the title screen, repack, and see what happened. Disassembling/debugging can also help. It's probably simple stuff like run-length encoding or copy X pixels from previously written. There should be an header with image width, height (like here, 800x600) and possibly a pallette before the image data.
Not an insurmountable task, it's just you dont have the skills and motivation to do it, or you wouldn't need to ask.
>>1
The internet doesn't know about it. It's most definitely a proprietary format, and it seems no one even cares about it because there's no spec for it anywhere.
Bringing /prog/ back to its people
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy