Distiller Error: ioerror; OffendingCommand: readstring

Question

Far too often I get an error log like this:
%%[ ProductName: Distiller ]%%
%%[ Error: ioerror; OffendingCommand: readstring ]%%
Stack:
(ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿýûðÖ²U/
@kÉè÷ýþÿÿÿþþþþþþþÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿþþþþþÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿþÿþþÿþÿþÿÿþÿÿÿÿÿÿÿÿÿÿþþþþþþþþÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿþþþþþþþÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ...)
-file-
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
TextText
I wildly guess about why, and have simply Ctrl-P again to print to Adobe PDF, and maybe half the time it works, without any changing, for example, the Photoshop image that I want converted to PDF. Sometimes, superstitiously, I reduce the res/file size and it goes through, but not always. The diagnostic tells me next to nothing, although I was a programmer for 20 years. There seems to be an Acrobat component named "Distiller," and "readstring" is failing for some reason that only one of the product programmers, or someone with similar knowledge, can understand, and the programmer does not tell me the user what to do about it.
What is the cause of the "ioerror"
The product I am using is Acrobat 6.

Answer 1

I do not know anything about Distiller, which I presume is a component of Acrobat 6 Professional. I would know nothing about "opening a file in Distiller." The ioerror occurs when I try to print, via ordinary means, a JPG file while in Photoshop to the printer listed as "Adobe PDF." Usually this works perfectly. When it does fail with the error log inserted into my original post, I just ctrl P again, and about half the time this works. When it does not, I make the totally uninformed guess that the JPG file may be too big, so I resize it smaller. Sometimes it then gets converted to PDF correctly, but sometimes it fails with the same "readstring" error message log. The success and failures appear haphazard, but as a former professional programmer I know that there are deterministic reasons, even if nobody ever discovers them. Debugging programs is very hard work.
Perhaps someone can suggest a means of forwarding the error message to someone in Adobe programming, who already knows what the error message should mean to me, the user.