>I used two programs, BASE64.EXE and MIME64.EXE.  Both of these are good
>decoders and they both return error messages when they find an encoded file
>to be farkled.  With both decoders the file was decoded without error.  Also
>Arachne has a MIME64 type of encoder either built in to the system somewhere
>or supplied as a separate program.  I talked with my son this afternoon on
>the telephone and I asked him about it.  He said it was just an ordinary JPG
>from his own digital camera and that such image files are readily displayed
>on all popular image viewing utilities having a capability of displaying
>JPGs.  He doesn't know why his email client stamped the attachment with the
>identity of a PJPEG and he doesn't know what a PJPEG is.  He later uploaded
>the image to his web site and I retrieved it from there and was able to
>view it with no problem.  BTW, his web hosting service automatically converts
>all uploaded JPG images to GIFs before they become available for viewing
>at the website.  It had become a GIF before I was able to eventually take
>a look at it.  I still don't know what a PJPEG is and neither does my son.
>
>Does anybody know what a PJPEG is, and why this ordinary JPG was stamped
>as such?
>
>Sam Heywood

Do BASE64.EXE and MIME64.EXE know a good .JPG from a bad one, or would the error
messages be for bad base64 encoding?  MPACK/MUNPACK needs a file name for each
part, which can be put there with a text editor if it isn't in the original
message. I did that once.

A web hosting service automatically converting JPG images to GIF is not a good
idea in view of the copyright problems with JPG.  I have no idea what PJPEG is.
Windows does some things like that, calling JPG PJPEG, without letting the user
know, and Windows email clients often use HTML and quoted-printable without the
user knowing.  Win32 is supposed to be so user-friendly, but I felt nearly lost
in what little I've seen of it.  I need the command prompt.

One friend nearby has a Compaq computer with Win98, and the modem no longer
works.  Now I wonder if the modem went bad or did Windows screw up royally.
Windows control panel finds external USB modem, but they seemed to think the 
modem was internal.  I didn't see any external modem.  This friend and his wife
know practically nothing about computers, daughter knows a little more.  I don't
know whether the modem was real or Winmodem, and they don't either.  That
Windows control panel left me stumped.  I see clearly Windows is not for me!

Reply via email to