Office and Acrobat PDFMaker toolbar in Leopard

Need some guidance ...
- Just upgraded to Leopard 10.5.4
- Photoshop 7 stopped working
- Upgraded to CS3
- PDFMaker Toolbar appears in Excel
- Trying to use toolbar gives error ""PDFMaker could not locate the Adobe PDF printer. Please install the printer on this machine."
- Not sure how to install this printer. Other topics have been specific to Tiger and Jaguar.
Thanks
Tim

Also please note that PDFMaker is a invention created by adobe to work specifically with MS Office. And will work on all version up to Office2004 on Mac.
However, In its infinite wisdom, and not realizing the wrath and backlash they would receive from Office Mac Users, dumped all VBA support in Office2008. Well, PDFMaker is a Casualty of that along with other such goodies as Solver in Excel and many other Macro based commands. MS has received such heat that they absolutely promise it will be back in Office 2010, 11, 12 whatever the next version is, at possible sacrifice of new features.
So if your trying to use with Office 2008 it won't work, you can't get it to work.
Besides, now in Office2008 you can actually create a PDF directly from the Save As command. And has solved a problem or bug Adobe has never figured out how to fix where if you created a PDF from a word document, would break the pdf into chunks depended upon whether you used Page and section Breaks. And would only create a PDF of the first sheet in an Excel spread sheet. A problem Adobe hasn't fixed in 13-14 years at least.
As to quality of the PDF created I have no idea. but they look great for the web.
So I can see why Jon threw in his comment about being removed in 9.

Similar Messages

  • Acrobat PDFMaker toolbar button disparity

    I am printing to PDF an Outlook email message using the Acrobat PDFMaker toolbar button.  The document generates but is displaying the date of the Outlook pst file instead of the date the email was created.  Conversely, if I attempt to print the same email from Outlook (File>Print>AdobePDF) the date listed on the resulting PDF is the actual date the email was generated.  I suspect there is some issue with the PDFMaker toolbar.  Is there an explanation or patch for this issue?  I am using Adobe Acrobat Pro 9.

    Also please note that PDFMaker is a invention created by adobe to work specifically with MS Office. And will work on all version up to Office2004 on Mac.
    However, In its infinite wisdom, and not realizing the wrath and backlash they would receive from Office Mac Users, dumped all VBA support in Office2008. Well, PDFMaker is a Casualty of that along with other such goodies as Solver in Excel and many other Macro based commands. MS has received such heat that they absolutely promise it will be back in Office 2010, 11, 12 whatever the next version is, at possible sacrifice of new features.
    So if your trying to use with Office 2008 it won't work, you can't get it to work.
    Besides, now in Office2008 you can actually create a PDF directly from the Save As command. And has solved a problem or bug Adobe has never figured out how to fix where if you created a PDF from a word document, would break the pdf into chunks depended upon whether you used Page and section Breaks. And would only create a PDF of the first sheet in an Excel spread sheet. A problem Adobe hasn't fixed in 13-14 years at least.
    As to quality of the PDF created I have no idea. but they look great for the web.
    So I can see why Jon threw in his comment about being removed in 9.

  • Leopard: Office and CS2 Flawless

    I loaded Leopard last night with an erase and install because my system never really seemed to run as fast as I expected. Especially, when the systems at work are faster and have slower CPU’s and 2 less gigs of RAM. But I have 2 HD’s and I moved all my files to the slave drive. Installed the OS and then loaded MS Office 04 and Adobe CS2. Went ahead an added all updates to both applications and they run smoothly. I am currently building a catalog in CS2 and it runs flawless. My system is quite faster, but I think that is attributed to never re-installing Tiger in the past for optimization. So for those who wonder, “YES” Office and CS2 run fine in Leopard. Leopard is solid, great job Apple.

    loribwith wrote:
    When I launch the program, it gets to the end and force quits.
    What do you mean by "force quits"?  Force quit is when you force an application to quit.  Programs don't "force quit" on their own.  Do you mean the program crashes?  Any error message(s)?

  • Acrobat PDFMaker serverが

    win XP Acrobat 7.0.9、Office word 2003を使用しています。
    Word文書をPDF化しようとして、Adobe PDFの変換から作成を選んだところ、ある日突然に「Acrobat PDFMaker serverが読み込めませんでした。インストーラーを修復モードで実行しますか？」と出てくるようになりました。指示どうりに進めても何も変化がありません。
    ご存知の方、よろしくお願いいたします。

    ＞ ある日突然に
    問題のなかったときと、問題の出ている現在とのシステムに違いはないのであろうか？
    以下は基本的なサポート文章。
    文書番号 : 224849
    Acrobat PDFMaker の問題のトラブルシューティング（Windows 版 Acrobat 6.0/7.0）
    文書番号 : 225338
    Windows XP でのシステムエラーまたはフリーズ発生時のトラブルシューティング（Acrobat 7.0）
    手動でアンインストールしてから再インストールしてみるとか？
    文書番号 : 231021
    Acrobat 7.0 Professional および Acrobat 3D を手動でアンインストールする方法（Windows）
    海外サイトでも以下のようなメッセージに関する投稿がある。Eudoraが関係しているとか、McAfeeとAcrobatとOfficeの組み合わせ相性が悪いといった投稿もあるが、真偽は 知らず。
    > The Acrobat PDFmaker Server could not be loaded. Do you wnat to run the installer in repair mode.

  • 1.     If I buy Acrobat XI, will it recognize Office 365 and setup PDFMaker automatically?

    Recently bought into MS Office 365, upgrading from Office 2007. I have been running Acrobat X. Come to find the PDFMaker COM Add-in upon which my workflow depends enormously does not support 365.
    http://helpx.adobe.com/acrobat/kb/compatible-web-browsers-pdfmaker-applications.html#main_ PDFMaker_compatible_applications
    I’m sure there is some wonderful explanation…I don’t have time…not sure I have the extra $200 either.
    Anyway, two questions:
    If I buy Acrobat XI, will it recognize Office 365 and setup PDFMaker automatically?
    How long can I count on Acrobat XI to work with Office 365?

    Hi K2karlk,
    Yes! Go here:
      http://forums.adobe.com/community/sendnow
    Hope that helps!
    Regards, Stacy

  • Acrobat PDFMaker Office COM Addin for Microsoft Office 365 does not work. When I check the cox for COM Add-ins, it unchecks it. "A runtime error occurred during the loading of the COM Add-in." I use Adobe X Professional. The Add-in worked fine in Office 2

    I recently upgraded to Microsoft 365 Home and use Outlook 2013. The Acrobat PDFMaker Addin worked fine in Office 2010. Now, I get an error message: Not loaded. A runtime error occurred during the loading of the COM Add-in.
    I use Adobe Acrobat X Professional.
    I have restarted Outlook, restarted my computer, and nothing changes.
    Does anyone have a solution?
    Steve

    I do not think that AA X is compatible with the newest versions of OFFICE and such. Your only choice is to print to the Adobe PDF printer or use the MS plugins to create PDFs.

  • Issues with Office 2010 and Acrobat Pro 8

    Good Day All;
    We are in the middle of upgrading from Windows XP to Windows 7 with Office 2010 and I was wondering if there are any issues with importing Office documents into Acrobat Pro 8. I have found out that there are a couple of issue with Office 201 and LifeCycle Designer.
    Any comments would be helpful
    Regards
    Chomp

    Acrobat 8 is not compatible with Microsoft Office 2010 and the PDFMaker plugins will not install. Only Acrobat X is compatible with Office 2010, and at this time only in 32-bit mode.
    Acrobat 8 is also not officially compatible with Windows 7, again Acrobat X is the first version to carry approval for that OS. It will still install, but Adobe cannot guarantee it will operate perfectly in all cases, and doesn't provide install support for that combination.

  • Word experienced a serious problem with the 'acrobat pdfmaker office com addin' add-in. after Office Updates.

    I cant cant use mail merge feature in Winword in conjunction with Abobe Acrobat 10 (pdfmaker add-in) after the recent Office April Windows and Office Updates.
    Here is a quick note from the event viewer:
    The program WINWORD.EXE version 14.0.7134.5000 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. 
     Process ID: 1138 
     Start Time: 01d07dcede19c458 
     Termination Time: 15 
     Application Path: C:\Program (file:///C:/Program) Files (x86)\Microsoft Office\Office14\WINWORD.EXE 
     Report Id: 
    Microsoft Word: Accepted Safe Mode action : Word experienced a serious problem with the 'acrobat pdfmaker office com addin' add-in. If you have seen this message multiple times, you should disable
    this add-in and check to see if an update is available. Do you want to disable this add-in?.
    I do not wish to disable the pdfmaker add-in as I use it to run mail merge on WORD and send 10s and 1000s of pdfs via email to external users. I am not sure what are my options here and I wish
    someone could help me get to the root cause of the matter.
    My environment is as follows:
    Windows 7 x64 SP1
    Office 2010 v 14.0.7128.5000
    Adobe Reader MUI X and Adobe Acrobat X
    Feroze

    Hi,
    As the event log indicated, this is due to acrobat pdfmaker office com addin doesn't work well with Microsoft Word.
    I would suggest you go ahead and try to upgrade your Adobe product to the latest version and see if issue persists.
    Or contact the support of Adobe and see if there is a known compatibility issue or not.
    Regards,
    Ethan Hua
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Can't reenable "Acrobat PDFMaker Office COM Addin"

    While PDFing a document from Microsoft Word 2007 (using Acrobat 9), the process froze so I killed the Word process.
    Afterwards, I found that the Acrobat menu is now missing when I open a Word document.
    In "Word Options", the Acrobat PDFMaker Office COM Addin is disabled. However, I've tried renabling it with no luck - it remains disabled.
    I've tried also adding the COM to the registry, and running a repair, as described at this web page:
    http://acrobat.timhuff.net/?p=29
    Neither worked for me.
    Does anyone have any other ideas before I have to reinstall Acrobat?
    Thanks,
    P.

    Hi Alice,
    Unfortunately that didn't fix it for me, but I finally found a solution courtesy of a comment by "Joel" at this blog - I've rewritten it slightly here:
    http://acrobat.timhuff.net/?p=29#comment-8787
    Open Word 2007.
    Click on the Word icon. Go to the bottom of the window that is opened.
    Click Word Options.
    In the window opened, click “Add-ins”.
    On the body of this window, choose the Adobe string that appear under “disabled application add-in”.
    This is the crucial part: go to the bottom of this window, instead of "COM add-ins", Choose "Disabled Items". (This is where I was going wrong.)
    Click Go.
    In the Disabled Items dialog box displayed, select the Adobe addin and click Enable, then Close, then OK.
    Regards,
    P.

  • I have Word 13 and Acrobat XI. Pdfmaker.officeaddin do work but closes down Word. What to do?

    I have Word 13 and Acrobat XI. Pdfmaker.officeaddin do work but closes down Word. What to do?

    Hi Lars ,
    Please refer to the following link to curb issues related to PDF maker .
    https://helpx.adobe.com/acrobat/kb/troubleshoot-acrobat-pdfmaker-problems-office.html
    Regards
    Sukrit Dhingra

  • Upgrade 10 10.6.5 - Office 2004 and Acrobat not working

    Using OSX 10.6.5 2 users, MS Office 2004, Acrobat 8 Pro. installed all updates. After Upgrade to OSX, MSOffice now has database daemon hang problems (quit daemon Word then loads), messages = Microsoft Framework cannot load. Adobe Acrobat cannot read or print any word documents. I am dead in the water here.
    Any help appreciated.
    ss

    Welcome to Apple Support Discussions.
    I'm not using either but so far I haven't seen any issues with this forum on either on 10.6.5. You can also cross post to the Snow Leopard Installation and Setup forum at:
    http://discussions.apple.com/forum.jspa?forumID=1337
    Finally I'd recommend posting to MS Office for Mac Forum located at:
    http://www.officeformac.com/productforums/
    I'm sure Adobe has similar forums however I'm not an Adobe customer so I can't recommend a forum, but I'm sure you can locate one at Adobe's web site.
    Good luck,
    Roger

  • Problem with Acrobat PDFMaker Office COM Addin

    I have recently installed MS Office 2010 on my W7 system but find that the Acrobat addin for MS Word 2010 is not working -- it gives errors messages and recommends that I disable the addin.
    This all used to work fine with MS Word 2007.
    Is there anything that can be done about this problem. Is there an upgrade for the Acrobat PDFMaker Office COM Addin ?
    Gerry

    Kelly,
    Whilst the main reason for 64 bit Office is large and complex Excel files, significant performance gains have been found in other usage scenarios, such as with lengthy and complex Word documents (especially when using complex plugins such as EndNote). It is in users' interests to use 64 bit Office if they can - but this is only possible if all their plug-ins support 64 bit Office.
    I see Microsoft's document as a classic support driven response (or should I call it a cop-out) - there are compatibility issues with non-Microsoft software, so, to eliminate the support burden, we will steer you towards the lowest common denominator of installing 32 bit Office even if you have an x64 OS. Whilst this makes a great deal of sense, in that many users will see no advantage in 64 bit Office, there are plenty of users, including myself, who would see advantages from 64 bit Office but are being prevented from moving to 64 bit Office because third party plug-in providers have yet to make 64 bit versions available.
    The situation with 64 bit Office plug-ins mirrors the situation with 64 bit Photoshop plug-ins, but with one key difference. Photoshop CS4, CS5 and CS5.1 (same as CS5; the apparent version bump indicates it was installed as part of Creative Suite 5.5) default to installing both 32 bit and 64 bit versions on x64 versions of Windows. You can therefore pick and choose which version of Photoshop you use according to which plug-ins you need. I'm now in the fortunate position of having 64 bit versions of all but two of the plug-ins I use regularly. I start the 32 bit version of Photoshop CS5.1 if I need those plug-ins, but my default is the 64 bit version.
    Office 2010 requires you to choose between 32 bit and 64 bit; you cannot install both at the same time, and you cannot mix and match between different Office applications (so, for example, installing 64 bit Project 2010 alongside 32 bit Office Professional Plus 2010 is not supported and may cause problems - indeed, I'm not sure if the Project installer would allow you to install the 64 bit version if you had 32 bit Office applications already installed). This makes the unavailability of 64 bit versions of a single plugin that you require for one Office application a total bar to moving to 64 bit Office.
    Unfortunately, this creates a 'chicken and egg' effect - the apparent demand for 64 bit versions of Office plugins is reduced because the unavailability of 64 bit versions of a crucial plugin prevents a move to 64 bit Office. I, for one, have a clear intention to switch to 64 bit Office, and will not buy new products or pay to upgrade existing ones unless they support 64 bit Office. Many products that can hardly be said to be aimed at the Office power user have supported 64 bit Office for some while, including Dragon NaturallySpeaking 11.5 and 11.0.
    I wholeheartedly welcome the support for some 64 bit Office applications in Acrobat 10.1, but urge Adobe to provide complete support for 64 bit Office 2010. Currently, 64 bit versions of Visio 2010, Project 2010, Access 2010 and Publisher 2010 are not yet supported in PDFMaker. Hopefully this support will be forthcoming in a future quarterly update.
    There is a mistake in your post - 64 bit Outlook 2010 is supported in Acrobat 10.1's PDFMaker. The issue with Outlook in the blog post you linked to is that Outlook 2010 doesn't have Microsoft's Save as PDF functionality - but if you have PDFMaker, using PDFMaker is the best option anyway.

  • Photoshop CS and Acrobat 6.0 stopped working in Snow Leopard

    Hello.  "Photoshop CS" and "Acrobat 6.0 Standard" suddenly stopped working in my iMac, apparently after I upgraded it to MacOS 10.6.8 (the latest version of Snow Leopard).  Both programs had worked normally until that OS upgrade.  I deleted Photoshop CS and tried to re-install it from the original CD, but the installation never proceeds because I get an error message entitled: "Install Adobe Photoshop CS quit unexpectedly".  This is the full error message:
    Process:         LaunchCFMApp [1516]
    Path:            /Volumes/Adobe(R) Photoshop(R) CS/Adobe(R) Photoshop(R) CS/Install Adobe Photoshop CS.app/Contents/MacOS/Install Adobe Photoshop CS
    Identifier:      com.MindVision.InstallerVISE
    Version:         8.2.1 (Installer VISE 8.2.1
    © MindVision Software 1991-2003)
    Code Type:       PPC (Translated)
    Parent Process:  launchd [131]
    Date/Time:       2012-03-25 19:18:43.187 -0300
    OS Version:      Mac OS X 10.6.8 (10K549)
    Report Version:  6
    Interval Since Last Report:          -476987 sec
    Crashes Since Last Report:           19
    Per-App Crashes Since Last Report:   2
    Anonymous UUID:                      D6C8A490-616B-48C6-A9E4-424A6399E390
    Exception Type:  EXC_CRASH (SIGTRAP)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   libSystem.B.dylib                       0x80239236 __pthread_kill + 10
    1   libSystem.B.dylib                       0x80238ad7 pthread_kill + 95
    2   LaunchCFMApp                            0xb80bfb30 0xb8000000 + 785200
    3   LaunchCFMApp                            0xb80c0037 0xb8000000 + 786487
    4   LaunchCFMApp                            0xb80dd8e8 0xb8000000 + 907496
    5   LaunchCFMApp                            0xb8145397 spin_lock_wrapper + 1791
    6   LaunchCFMApp                            0xb801ceb7 0xb8000000 + 118455
    Thread 1:
    0   libSystem.B.dylib                       0x80142afa mach_msg_trap + 10
    1   libSystem.B.dylib                       0x80143267 mach_msg + 68
    2   LaunchCFMApp                            0xb819440f CallPPCFunctionAtAddressInt + 206231
    3   libSystem.B.dylib                       0x80170259 _pthread_start + 345
    4   libSystem.B.dylib                       0x801700de thread_start + 34
    Thread 0 crashed with X86 Thread State (32-bit):
      eax: 0x00000000  ebx: 0x802fc540  ecx: 0xb7fff9ac  edx: 0x80239236
      edi: 0xb8211640  esi: 0x00000005  ebp: 0xb7fff9d8  esp: 0xb7fff9ac
       ss: 0x0000001f  efl: 0x00000286  eip: 0x80239236   cs: 0x00000007
       ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
      cr2: 0x8023922c
    Binary Images:
    0x80000000 - 0x8005dff7  com.apple.framework.IOKit 2.0 (???) <3DABAB9C-4949-F441-B077-0498F8E47A35> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x8007d000 - 0x800e7fe7  libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
    0x80142000 - 0x802e9ff7  libSystem.B.dylib 125.2.11 (compatibility 1.0.0) <2DCD13E3-1BD1-6F25-119A-3863A3848B90> /usr/lib/libSystem.B.dylib
    0x8036b000 - 0x804e6fe7  com.apple.CoreFoundation 6.6.5 (550.43) <10B8470A-88B7-FC74-1C2F-E5CBD966C051> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x805de000 - 0x805ecfe7  libz.1.dylib 1.2.3 (compatibility 1.0.0) <33C1B260-ED05-945D-FC33-EF56EC791E2E> /usr/lib/libz.1.dylib
    0x805f1000 - 0x805fdff7  libkxld.dylib ??? (???) <9A441C48-2D18-E716-5F38-CBEAE6A0BB3E> /usr/lib/system/libkxld.dylib
    0x80601000 - 0x80647ff7  libauto.dylib ??? (???) <29422A70-87CF-10E2-CE59-FEE1234CFAAE> /usr/lib/libauto.dylib
    0x80654000 - 0x807d6fe7  libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <D5980817-6D19-9636-51C3-E82BAE26776B> /usr/lib/libicucore.A.dylib
    0x80838000 - 0x808e5fe7  libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <9F8413A6-736D-37D9-8EB3-7986D4699957> /usr/lib/libobjc.A.dylib
    0x808f9000 - 0x808fcfe7  libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
    0x8fe00000 - 0x8fe4163b  dyld 132.1 (???) <4CDE4F04-0DD6-224E-ACE5-3C06E169A801> /usr/lib/dyld
    0xb8000000 - 0xb81defff  LaunchCFMApp ??? (???) <F24FBFDD-E694-6F38-BFFB-293613CEF2DE> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp
    0xffff0000 - 0xffff1fff  libSystem.B.dylib ??? (???) <2DCD13E3-1BD1-6F25-119A-3863A3848B90> /usr/lib/libSystem.B.dylib
    Translated Code Information:
    objc[1516]: garbage collection is ON
    NO CRASH REPORT
    Model: iMac9,1, BootROM IM91.008D.B08, 2 processors, Intel Core 2 Duo, 2.26 GHz, 4 GB, SMC 1.44f0
    Graphics: NVIDIA GeForce 9400, NVIDIA GeForce 9400, PCI, 256 MB
    Memory Module: global_name
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.10.131.42.4)
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: WDC WD3200AAJS-40H3A0, 298.09 GB
    Serial ATA Device: OPTIARC DVD RW AD-5670S, 351.5 MB
    USB Device: Built-in iSight, 0x05ac  (Apple Inc.), 0x8502, 0x24400000 / 2
    USB Device: Keyboard Hub, 0x05ac  (Apple Inc.), 0x1006, 0x26400000 / 2
    USB Device: Apple Optical USB Mouse, 0x05ac  (Apple Inc.), 0x0304, 0x26430000 / 4
    USB Device: Apple Keyboard, 0x05ac  (Apple Inc.), 0x0220, 0x26420000 / 3
    The error message that I repeatedly get when trying (unsuccessfully) to open Acrobat 6.0 Standard is:
    Process:         LaunchCFMApp [1501]
    Path:            /Applications/Adobe Acrobat 6.0 Standard/Acrobat 6.0 Standard.app/Contents/MacOS/Acrobat
    Identifier:      com.adobe.Acrobat
    Version:         ??? (???)
    Code Type:       PPC (Translated)
    Parent Process:  launchd [131]
    Date/Time:       2012-03-25 19:14:53.555 -0300
    OS Version:      Mac OS X 10.6.8 (10K549)
    Report Version:  6
    Interval Since Last Report:          -477219 sec
    Crashes Since Last Report:           18
    Per-App Crashes Since Last Report:   12
    Anonymous UUID:                      D6C8A490-616B-48C6-A9E4-424A6399E390
    Exception Type:  EXC_CRASH (SIGTRAP)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   libSystem.B.dylib                       0x80239236 __pthread_kill + 10
    1   libSystem.B.dylib                       0x80238ad7 pthread_kill + 95
    2   LaunchCFMApp                            0xb80bfb30 0xb8000000 + 785200
    3   LaunchCFMApp                            0xb80c0037 0xb8000000 + 786487
    4   LaunchCFMApp                            0xb80dd8e8 0xb8000000 + 907496
    5   LaunchCFMApp                            0xb8145397 spin_lock_wrapper + 1791
    6   LaunchCFMApp                            0xb801ceb7 0xb8000000 + 118455
    Thread 1:
    0   libSystem.B.dylib                       0x80142afa mach_msg_trap + 10
    1   libSystem.B.dylib                       0x80143267 mach_msg + 68
    2   LaunchCFMApp                            0xb819440f CallPPCFunctionAtAddressInt + 206231
    3   libSystem.B.dylib                       0x80170259 _pthread_start + 345
    4   libSystem.B.dylib                       0x801700de thread_start + 34
    Thread 0 crashed with X86 Thread State (32-bit):
      eax: 0x00000000  ebx: 0x802fc540  ecx: 0xb7fff9ac  edx: 0x80239236
      edi: 0xb8211640  esi: 0x00000005  ebp: 0xb7fff9d8  esp: 0xb7fff9ac
       ss: 0x0000001f  efl: 0x00000286  eip: 0x80239236   cs: 0x00000007
       ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
      cr2: 0x8023922c
    Binary Images:
    0x80000000 - 0x8005dff7  com.apple.framework.IOKit 2.0 (???) <3DABAB9C-4949-F441-B077-0498F8E47A35> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x8007d000 - 0x800e7fe7  libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
    0x80142000 - 0x802e9ff7  libSystem.B.dylib 125.2.11 (compatibility 1.0.0) <2DCD13E3-1BD1-6F25-119A-3863A3848B90> /usr/lib/libSystem.B.dylib
    0x8036b000 - 0x804e6fe7  com.apple.CoreFoundation 6.6.5 (550.43) <10B8470A-88B7-FC74-1C2F-E5CBD966C051> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x805de000 - 0x805ecfe7  libz.1.dylib 1.2.3 (compatibility 1.0.0) <33C1B260-ED05-945D-FC33-EF56EC791E2E> /usr/lib/libz.1.dylib
    0x805f1000 - 0x805fdff7  libkxld.dylib ??? (???) <9A441C48-2D18-E716-5F38-CBEAE6A0BB3E> /usr/lib/system/libkxld.dylib
    0x80601000 - 0x80647ff7  libauto.dylib ??? (???) <29422A70-87CF-10E2-CE59-FEE1234CFAAE> /usr/lib/libauto.dylib
    0x80654000 - 0x807d6fe7  libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <D5980817-6D19-9636-51C3-E82BAE26776B> /usr/lib/libicucore.A.dylib
    0x80838000 - 0x808e5fe7  libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <9F8413A6-736D-37D9-8EB3-7986D4699957> /usr/lib/libobjc.A.dylib
    0x808f9000 - 0x808fcfe7  libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
    0x8fe00000 - 0x8fe4163b  dyld 132.1 (???) <4CDE4F04-0DD6-224E-ACE5-3C06E169A801> /usr/lib/dyld
    0xb8000000 - 0xb81defff  LaunchCFMApp ??? (???) <F24FBFDD-E694-6F38-BFFB-293613CEF2DE> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp
    0xffff0000 - 0xffff1fff  libSystem.B.dylib ??? (???) <2DCD13E3-1BD1-6F25-119A-3863A3848B90> /usr/lib/libSystem.B.dylib
    Translated Code Information:
    objc[1501]: garbage collection is ON
    NO CRASH REPORT
    Model: iMac9,1, BootROM IM91.008D.B08, 2 processors, Intel Core 2 Duo, 2.26 GHz, 4 GB, SMC 1.44f0
    Graphics: NVIDIA GeForce 9400, NVIDIA GeForce 9400, PCI, 256 MB
    Memory Module: global_name
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.10.131.42.4)
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: WDC WD3200AAJS-40H3A0, 298.09 GB
    Serial ATA Device: OPTIARC DVD RW AD-5670S
    USB Device: Built-in iSight, 0x05ac  (Apple Inc.), 0x8502, 0x24400000 / 2
    USB Device: Keyboard Hub, 0x05ac  (Apple Inc.), 0x1006, 0x26400000 / 2
    USB Device: Apple Optical USB Mouse, 0x05ac  (Apple Inc.), 0x0304, 0x26430000 / 4
    USB Device: Apple Keyboard, 0x05ac  (Apple Inc.), 0x0220, 0x26420000 / 3
    **  Why can't I re-install Photoshop CS or open Acrobat 6.0 Standard in my MacOS 10.6.8 iMac?  **
    Please reply to [removed]
    Thank you,
    Richard

    You need to fix your Rosetta emulation. (Re-)install it from your OSX install DVD or download it from Apple.
    Mylenium

  • PC Windows, Office 2010, Acrobat X Standard - how to configure Acrobat that PDF documents are generated in PDF version 1.4 by default for word and excel (already tried to change the pre-adjustment for word and excel)

    PC Windows 7 Pro
    Office 2010
    Acrobat X Standard
    Ich habe bereits in den Voreinstellungen von Acrobat X Standard für Word und Excel die Einstellungen dahingehend geändert, dass PDF Dateien mit der PDF Version 1.4 generiert werden - jedoch funktioniert dies nicht.

    Edit:
    The description above was erroneously written in german - sorry for that - please find the english description below:
    PC Windows 7 Pro
    Office 2010
    Acrobat X Standard
    I alrady tried to change the pre-adjustment in Acrobat X Standard for Word and Excel, that PDF files should be generated in PDF Version 1.4 out of these applications - but it did not work.

  • OFFICE 2007 and Acrobat

    I had reported on some issues of using OFFICE 2007 with Acrobat 7 and 8. I suspect there was a problem with AA9 also. Typically the result would be graphics with lines through them, at least when expanded. This would often appear that your graphic had been split into parts and pieced together in Acrobat. SP2 for OFFICE 2007 was released recently and I went back to test this issue with the new release. At this point it appears that everything is working great. This follow up is to suggest updates to BOTH OFFICE 2007 and Acrobat if you are having some problems. On this machine I am running VISTA business, OFFICE 2007 (SP2), and AA8. Bill

    Thanks for the update.

Maybe you are looking for