Since we don't have any hard facts it's kind of an aimless searching.JGZinv wrote:
If I'm looking at the exe (presumeably in hex) what should I be looking for?
Look for something like:
'fKIB'
'gKIB'
'hKIB'
'iKIB'
without quotes; since it's an early version the marker might look a bit different
from there bink data are stored; dunno about the details of the data.
If there are visible separation those should have values of 0x00 or 0xFF or you see equally spaced section on the righthand-text-side-display.
Sometimes looking around the end of the exe should give you some clue about program parameters or other designated names used. Anything in plain view.
Other than that well, disassembling the exe would help in other words reverse engineering. Well, reading direct raw binary command code is something only a handful people can do on the fly. Evenso it's not worth it for any complex programs bigger than say 30kbytes.
Another way could be to find out something about the audio file format.
What's stored, what's possible, possible stream format design etc. You could use recordings to get data that's close to the original and work from there. You probably know if it's 8 or 16 bit audio already. And then write your own reader/player. Modify around until it works...
lol