still seems that besides printing to file, or screen capturing, there
is no way (without the paperport software) to convert the scanned .max
image files into any other format. Has anyone come up with anything?
If you choose to save images in a format that isn't an open standard
(TIFF, JPEG, GIF, and PNG are all open, BMP isn't really open but it's
very well-understood) then you will get ****ed over. I don't understand
why anyone would archive images in a proprietary format, but hey, you
made your bed, you've now gotta lie in it.
Whatever you do, archive your images (and your other documents, if you
care about them) in open formats from now on. TIFF, JPEG, GIF, PNG, and
BMP images; ASCII, HTML, Unicode, and XML text; MP3 and WAV sound files;
MPEG and MPEG2 movies; TAR, GZIP, ZIP, and BZIP2 archive formats; and
just about any format used by open-source programs (like OpenOffice's
XML format used for word-processing/presentation/spreadsheet files) are
essentially future-proof. Other formats may or may not be--look
carefully before you commit to using them, and you could save yourself a
lot of pain later on.
It's annoying because paperport came with an old scanner, and wont
install on my new computer -- the paperport support people say i have
to purchase the upgrade -- forget that....
Paying money for a new version of this commercial software product is
the easiest and quickest way out of your dilemma[0]. If you have some
programming skill, a compiler, and a hex editor, you might be able to
decipher enough of this proprietary .MAX format to be able to read the
data. Run /usr/bin/file on one of these .MAX files; if it identifies
the file as anything other than "data", that'll give you a good place to
start your investigations.
I've deciphered an undocumented binary file format and written code to
parse/extract/rewrite it for work. This takes a while. If you decide to
do that, make sure you publish what you find (blog, freshmeat.net,
Sourceforge, whatever) so other people can build on your efforts. HTH
anyway,
[0] You're still left with using code you don't own, can't look at, and
might not be able to use effectively later on to access *your* data.
You may be OK with that. Refer to paragraphs 1 and 2 for the potential
disadvantages.