[Technical] Fantasy Craft and Adobe 9.1.3 for Windows 7 64bit - Crash

[naturaltwenty]

Not that this will affect too many folks but the Fantasy Craft PDF (I note that it's this pdf because I've been using Windows 7 RC1 64bit for about a month for my home PC for all of my work) seems to have a conflict causing Adobe to crash.

Description
Faulting Application Path:   C:\Program Files (x86)\Adobe\Reader 9.0\Reader\AcroRd32.exe

Problem signature
Problem Event Name:   APPCRASH
Application Name:   AcroRd32.exe
Application Version:   9.1.0.163
Application Timestamp:   49a88f00
Fault Module Name:   MakeAccessible.api
Fault Module Version:   9.1.0.163
Fault Module Timestamp:   49a885c9
Exception Code:   c0000005
Exception Offset:   0004cbed
OS Version:   6.1.7100.2.0.0.256.1
Locale ID:   1033
Additional Information 1:   0a9e
Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
Additional Information 3:   0a9e
Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

Extra information about the problem
Bucket ID:   1179334943


Later,

Greg Volz
Natural Twenty Games
www.naturaltwenty.com

[naturaltwenty]

Appears to be an issue between the Reader reading function (assistive technology) and the pdf.  Cancelling the tagging (which is used to process the document) let's the user page through the pdf without crashing so that's the workaround (for anyone with 9.1.3 and Windows 7).

[MugMug]

Foxit is reading it just fine. I prefer to think of it as an "upgrade" rather than "workaround."

Walter

[Krensky]

The issue probably has far more to do with using the RC of Win 7 rather then the Gold version.

[TheTSKoala]

The issue probably has far more to do with using the RC of Win 7 rather then the Gold version.

I'm going to toss this out there.. not to be a 'know it all' or 'that nay-sayer marsupial'... however... Adobe hasn't gone gold for Win7 yet.  The crash could be caused by any number of features inproperly accessing the 'newer' system resources.  My bet would be that whatever 'it' is... would happen in any pdf that shared the same quality.  Release Clients are funny like that.  Windows may be ready for the release... ...most of the other companies aren't.

[Krensky]

True, Adobe Reader doesn't list Windows 7.

It might be Adobe Reader doesn't work right on Windows 7, or that it doesn't work right on Windows 7 RC, or both.

[Crafty_Pat]

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.

[TheTSKoala]

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.   )

[Krensky]

Kolala, read the topic.

And FoxIt says it's PDF 1.4

[TheTSKoala]

Kolala, read the topic.

And FoxIt says it's PDF 1.4

Call me well brainwashed, but I never believe something from a computer that a person can tell me.  ...unless I'm trying to prove the person wrong.  ...which I'm not.

Oh.. and.. P.S.  I DID read the topic.  I just normally ask things in a stream of conscientiousness, not exactly unknown vs. known.  ...drives my superiors nuts sometimes...

[Crafty_Pat]

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.

We used CS2 on this project, so I'm guessing 1.6. We haven't quite made the transition to CS4 yet.

EDIT: Turns out we are compiling with 1.4, which is compatible with Acrobat 5.0. We do this because back in the day we "upgraded" by compiling a copy of Spycraft 2.0 to the most current version of Acrobat at the time and suddenly a ton of people couldn't even open the file.

As always, we're open to suggestions - within reason, of course.

[naturaltwenty]

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.   )

[naturaltwenty]

And of course - FoxIT has no problem with it

Later,

Greg Volz
Natural Twenty Games
www.naturaltwenty.com

[Crafty_Pat]

Thanks for your help identifying the issue, gentlemen.

[TheTSKoala]

And of course - FoxIT has no problem with it

Later,

Greg Volz
Natural Twenty Games
www.naturaltwenty.com

I've re-created the issue in one of our labs.  (Jet lag kills my ability to sleep.)  Incoming private messages.  

(You'd be amazed what fits under either OSHA / American Disability Compliance)