Note I'm just posting this for knowledge sake - I've got no beef with Crafty
I'm an IT professional who likes to add to the knowledge base !
This is a brand new system - my old one died - http://www.naturaltwenty.com/?p=170
so I downloaded adobe reader fresh from adobe.com.
New system specs are as follows:
Base score 5.9
Processor Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz / 6.5
Memory (RAM) 4.00 GB / 6.5
Graphics NVIDIA GeForce GTS 250 / 6.1
Gaming graphics 2815 MB Total available graphics memory / 6.1
Primary hard disk 839GB Free (931GB Total) / 5.9
Windows 7 Ultimate
The error can be avoided by clicking cancel when the following box pops up -
Regardless of which option is selected it appears that the assistive technology chokes on the file. I've checked against other large pdf (Artesia which was also compiled using 1.4) and that appears to work fine.
Google isn't spitting out anything so the problem's either not widespread or is only just starting to exhibit. Unfortunately, we're at a loss as to how to "fix" it. Is anyone else experiencing this issue?
EDIT: Or, naturaltwenty, if you know more about dodging this issue, please drop me an IM.
Secondary question (my techy brain is curiours now..). Nat20, is Adobe a fresh install or older version updated to the current? How much RAM are you running? Have you bumped into an error creating a PDF with Adobe? Have you tried running OpenOffice / Foxit / Ghostscript? I haven't hit your EXACT problem, however, I have hit some issues with other programs that are extremely similar.
Crafty. Quick q. What PDF version did you compile with? I'm going to assume 1.7... but I've seen people *coughsCommandscoughs* still compiling with 1.6. I doubt that's the problem, but a piece of the puzzle none the less.
It could very much be Crafty is using a PS command (resident in Adobe used during the build of the PDF) that Windows 7 just can't handle. Probably be addressed in Adobe10...
Oh.. and.. um.. I know nothing of computers.
..I swear. ..I'm leaning towards a PostScript driving the new Windows nuts....
(To appease Krensky, I took out the 32-bit vs. 64-bit question.