et al, I reported that problem with the XPDF APM, and it was giving me "Command or filename not recognized" error, when I clicked on a .PDF file. I cured it..but my cure doesn't answer the question, "Why..?"
1. I went to the XPDF home page, and downloaded the latest XPDF which is version 2.01 for DOS. 2. I unzipped the XPDF201.ZIP in a spare directory, and renamed the (now) PDFTEXT.EXE to PDFTOTEX.EXE. 3. I again installed the XPDF091.APM into my working \ARACHNE directory. 4. I copied the version2.01 (now renamed) PDFTOTEX.EXE from my spare directory into my working \ARACHNE directory. 5. I went thru the procedure of ALT-F2 and drill down to a .PDF file, then clicked on it, and waited, while I watch intermittant HDD drive-light activity, for a reasonable time, then....voila..!!! There was my PDF2text file displayed in Arachne1.71....then I found that to really save it, I had to "P" to get a PTR.TXT file, then save that...otherwise it saved the original .PDF file... but... ...while it works....the workaround doesn't answer the question of why that XPDF091.APM worked a month ago, and won't work now, and the substitute PDFTOTEX.EXE from v.2.01 copied in, makes it work again.... ...I still say, that the v.091 ....EXE looks like all it is missing is is can't find it's DPMI support file...but....hey...maybe I'm wrong....(of course, that's never happened before...<g g g>...) ....gregy -- This mail was sent by a user of Arachne - The Ultimate Internet Client
