Quote:
Originally Posted by mscott161
Nick,
My email is michaels@ebizsoft.com. The problem I have is on the encoding bit. I read a offset then the length, but the numbers are pointing to bytes that have nothing in them. I am also using a byte array to hold the compressed data and using it as the incoming file and output is to a string that at the end I write to a file to check. I have parsed the PNG files, !!sw, confused on the values for !!cm. I am assuming the default 64 resource. I have been working on the style and extended style data to parse. All is in objects so I can hopefully at the end put together other formats.
Michael |
Michael:
I just sent you my source for deimp.exe and imp_dump.pl which parses a .imp into it's component filetype records and extracts the images and text.
I have not yet parsed !!cm (didn't need to just yet as deimp is used), but have parsed !!sw (which I think is useless/nonfunctional?). I have a lot of "notes" on this, but have not yet coded (in Perl) all of the .RES filetypes.
If you are interested in further reverse-engineering of the .imp format, then I think a new thread is in order. I know quite of few will join in! The main information on .imp reverse-engineering comes from the Jeffrey Kraus-yao's excellent website
http://krausyaoj.tripod.com/reb1200.htm (or on the REB1200 for Dummies website
http://www.chromakinetics.com/REB1200/imp_format.htm) .