Image moves when printed from SAP queue versus Adobe Reader.

I've got a form with a image embedded into it that serves as a background watermark.
This document is usually printed from Adobe Reader, however some users have requested the ability to print directly to a SAP printer without using Adobe Reader to print using windows drivers.
When the form is sent to a SAP printer the image watermark is for some reason moved about 3mm to the right which causes the watermark not to align with the Text Fields that also print on the form.  The text fields do not move, they print in exactly the same spot with either print method.  Only the image seems to be affected.
Has anyone run into this?  The image is an embeded .png file that is set to Scale Image Poportionally in the sizing options.
Thanks for any input!

Thank you for your replies.
I looked at the notes you suggested and it does seem related to the extra margin added to documents printed to PCL-5.
If I use LiveCycle to set an image field .5mm from the left edge of the page, and then print it from SAP directly and then from Adobe Reader I see two different things.
Adobe Reader (with page scaling option turned off) will simply omit anything that falls outside the printable range. 
SAP  will move the omitted content into the printable area.  This is what is causing my image watermark not to align properly with the text in front of it.  The image field was too close to the left margin and so in the process of printing, SAP has moved it over to fit in the printable area.
It seems I can fix this issue for my particular requirement by creating a new image field that has the extra white space removed so that I can keep the image field farther away from the left edge of the page.
Not sure if there is some way to change the way the drivers for device type HPLJ4 are handling these margins, but it will likely just be easier to change the images to move them further from the edge which seems to fix it.
Edited by: Clay Robinson on Feb 15, 2011 9:59 PM

Similar Messages

  • When printing a signed document with Adobe Reader, the comment icons appear.  How do I prevent this

    When printing a signed document with Adobe Reader, the comment icons appear.  How do I prevent this ?

    When printing from Reader, select Document instead of Document and Markups:

  • Using Preview when printing from SAP

    Just starting to use SAP Java GUI on the Mac and one of the 1st items I discovered was the inflexibility for printing. I would need to define the printer in the preferences of the SAP Java GUI and then anytime I would print it would just go to that printer.
    Problem with this is that sometimes I work from within the office, and sometimes from home with as a result that my printer changes.
    When on Windows, I also often performed a print from within SAP but then selected the Adobe PDF printer instead so that I had a resulting PDF file.
    What I thus really wanted was for anytime I print from SAPGUI to the local printer to get a print dialog just like it does on Windows. I checked around but could not find anything to replace the lp command with on Mac that would then provide this. As a work-around I developed the following small script instead. Now instead of just printing, the print-out will be shown in Preview as a PDF. From here I can then save it as a PDF, print it, mail it, .... anything else one can do with Preview.
    This is not the exact solution I wanted as I wanted to just get a print dialog; but this gets me a lot closer to it.
    See next post (hopefully as I am having issues posting) for script & steps.

    Instructions:
    First, make sure that printing is setup for SAP Java GUI. There is sufficient information out there but main items are that the printer within SAP is defined with method G and that the device type os POST2 (for postscript). Also ensure that under output attributes Color printer is checked.
    Next create the script. I put it in the /Applications/SAP Clients folder but it can be put anywhere you like. You can name the script however you like, I named it SAPLPD.
    First thing the script does is converting the postscript file to PDF and storing it in the user's temporary directory. It adds the timestamp to the filename just to ensure there are no duplicated. It then opens the PDF file using Preview. It will wait for 1 second after which it will remove the file created.
    It also looks that all the files in this temporary directory are automatically removed by OSX, so even should the file not have been removed; on next logout (I think) the file will be removed anyhow.
    Script:
    The script is:
    #!/bin/bash
    timestmp=`date +%Y%m%d%H%M%S`
    /usr/bin/pstopdf -i -o $TMPDIR/sap_print_$timestmp_$$.pdf
    open -a /Applications/Preview.app $TMPDIR/sap_print_$timestmp_$$.pdf
    sleep 1
    rm $TMPDIR/sap_print_$timestmp_$$.pdf
    Once you have created the script it needs to be made executable. Do this by open the Terminal, changing to the location where you saved the script and entering the command:
    chmod a+x (script name)
    So in my case I would have entered the following 2 commands in Terminal:
    cd "/Application/SAP Clients"
    chmod a+x SAPLPD
    Last but not least is changing the command the SAP Java GUI uses for printing. Go into preferences for the SAP Java GUI and go to the Printing section (under Desktop). There for the Print Spooler entry which is currently set to /usr/bin/lp you change that to the script. So for me I have:
    /Applications/SAP Clients/SAPLPD
    Easiest way to do this is by using the Browse button and then going to where the script is. No parameters are passed to the script so everything else can be removed. What I have is exactly what I show a few lines above.
    And that is it, when now printing from SAP it opens the print-out in Preview and from there I can select my printer options etc.
    Use of the script is on your own risk. It works for me but there is no guarantee that it will work for you.
    Would love to hear about any other options.

  • Print jobs goes to HOLD mode in IBM system i when printing from SAP NW 7.0

    Hi friends,
       Whenever I send the jobs from SAP environment(NW 7.0) to the IBM printers on the network.  The jobs acts like it's going to print  but then goes to HOLD mode.
    I have changing the FORMS TYPE but that didn't help nor trying to releasing them again.
    We are running SAP NW 7.0 in IBM system i V5R4 and using
    IBM infoprt1580 printers.
    HELP !     Any tips are well apprieciated !
    Thanks.
    F. Y.

    Hi Frank,
    assuming that the spooled file goes into "hold" in the output queue on i5/OS (not in the SAP spooling system), I would suggest that you check the settings in the reply list and spool job for message CPA3394 "Load form type '...' device ... writer ... .". When this message is sent, the default reply is 'H' (= hold), but you probably want to reply 'I' (= ignore). You can use the command ADDRPYLE (or WRKRPYLE) to add an automatic reply of 'I' to this message. Make sure that job description QGPL/QSPLPRTW is set to INQMSGRPY(*SYSRPYL).
    If this does not help, another message than CPA3394 might cause the problem. You need to check the QSYSOPR message queue and the joblog of the writer job to find out which message is causing the hold status.
    Kind regards,
    Christian Bartels.

  • Issues with image centering when printing from CS5

    I contacted EPSON tech support about this issue, they are putting the blame on the application used - in my case Photoshop CS5 printing with an EPSON R2880.
    I am trying to figure out exact print tray margins to take into account when printing horizontal 13x19 images on EPSON's Hot Press 13x19 paper on the R2880 (via manual roll single feeder).
    These are not borderless full frame images, 13x19 image files set on white with exact white frames around the image, so the shift in centering becomes quite obvious on the print.
    Here are the two print settings I have tried, both do not center the image correctly:
    Selected Scale to Fit Media & Center Image Top:0 Left 0.105
    Selected Center Image: Top: -10,152 Left -0.118
    (margin values are entered in the print window automatically)

    u are probably not getting much help on this unless you post screenshot of your process (starting with File> Print window)
    remember, Photoshop can print a document correct regardless of how it looks on the monitor (and vice versa: Photoshop can display a document correct regardless of how it prints)
    i recommend getting a known target like the WhackedRGB.jpg and see where the problem is occuring (in Photoshop color management settings, on the monitor, on the printer or both)...

  • Highlighter colors look muddy when printed from Acrobat 8, X, and Reader XI to Xerox WC7775, 7665

    Highlighter colors look muddy when printed to Xerox WC7775, 7665(applies to Acrobat 8 Std, Acrobat X Std, Reader XI).  I tried the latest PS and PCL6 drivers from xerox.com.  How can I troubleshoot / fix this so highlighter colors look bright when printed? 
    When printing highlighted text from other applications (like Word) from the same computers to the same printers, the highlighter color is bright.  Users print PDFs for distribution to clients so they would like the printed documents to look good.
    Thanks

    I have tried the WCS sRGB, scRGB and ICC U.S. Web Coated (SWOP) v2 color profiles.  sRGB and scRGB are very slightly brighter than the default and SWOP but still much more muddy than the bright yellow from a Word document.  I just started digging in to this today so any helpful hints would be greatly appreciated. 

  • Printing from LCD-Form in Adobe Reader 9 - Fonts-Problem

    hey there, I posted this in Adobe Reader forum, but probab. its better here...
    HELP PLS!
    I have a strange problem.I created a form in Adobe Live Cycle Designer and use this in an Adobe-PDF-package.
    By printing it on another PC (Windows) the fonts did not come out right - u can C this in the other thread, as I can't upload the attachement here ....
    http://forums.adobe.com/thread/540352?tstart=0
    Anybody of u had a similar problem or a solution for that?
    THX a lot,
    Maria

    See:  http://forums.adobe.com/message/1903852#1903852
    Look at Bill @VT's response

  • Poor Image Quality when Printing PDF from Office 07 using Acrobat 9 Pro Ext

    Hi there,
    Hoping to figure out why my images (jpegs, gifs, pngs, etc) seem to print in very poor quality when printing from Powerpoint and Word 2007?
    When I actually print out the pdf onto paper, the images seem fine. The image quality is also good in Word and Excel
    I did not have this problem using Office 2003 products.
    Is this a common problem? I realize that the problem maybe Office related but any help or information appreciated.
    Thanks

    If the images' file format is PNG or TIFF you could play with the compression settings available in Acrobat's Preferences.
    Edit > Preferences > select the Category "Convert to PDF".
    In the"Converting To PDF" pane, select PNG or TIFF.
    Then, click on the Edit Settings" button.
    For either image format you could try one of the Lossless compression routines.
    Be well...

  • Lines in images when printing from anything but iphoto

    When I print on my computer from anything but iphoto the quality is horrible and the print has very noticeable lines in it across everything. I recently did a layout in Adobe Illustrator and when I went to print it on regular 4x6 satin photo paper there are lines everywhere. This also happens when printing from powerpoint, photoshop, word, and whatever else that is not iphoto. I cant send out things that are printed at such horrible quality. Everything comes out fine when i print text in black but photos look pixelated and have lines in them no matter what paper I use if printed from anything but iphoto.
    HELP DR.

    Check the printer manual about calibrating. There is a solution in most drivers for inkjet printers which may call like paper forwarding or so. It seems, that your printer forwords the paper a bit to much before the line is printed.

  • How can i choose a lower quality print density when printing from firefox on my Mac. I cant move the slider along the scale ( I can when printing from the computer).

    I can't change the print density when printing from Firefox. It is set at standard and although there is a "slider button" to use for choosing less or more density, it can't be moved. I can tick "grayscale". I can choose the density when printing from the computer. I have a Mac

    I also have this problem where I used to be able to shrink a 2 page doc to a single page. Since upgrade to FF4 it no longer works - but you can choose say 60% and it will work. All used to work fine in FF3

  • When printing from v10.1.3 or v9 from OSX Lion get Adobe Reader quit unexpectedly

    When printing from v10.1.3 or v9 from OSX Lion get Adobe Reader quit unexpectedly
    Click on the print button
    get the Print screen
    Click Print then get the error
    Am able to print fine from other applications
    Have tried uninstalling and restalling Adobe 10.1.3, downgrading to v9. reinstalling the printer driver.
    Process:         AdobeReader [2372]
    Path:            /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
    Identifier:      com.adobe.Reader
    Version:         9.4.0 (9.4.0)
    Code Type:       X86 (Native)
    Parent Process:  launchd [220]
    Date/Time:       2012-07-22 18:19:40.579 +1000
    OS Version:      Mac OS X 10.7.4 (11E53)
    Report Version:  9
    Interval Since Last Report:          265926 sec
    Crashes Since Last Report:           23
    Per-App Interval Since Last Report:  30 sec
    Per-App Crashes Since Last Report:   2
    Anonymous UUID:                      6710821A-4F63-46E6-AD7A-75FB91C7B394
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000014
    VM Regions Near 0x14:
    --> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL  /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
        __TEXT                 0000000000001000-0000000000003000 [    8K] r-x/rwx SM=COW  /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
    Application Specific Information:
    objc[2372]: garbage collection is OFF
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   AdobeAGM                                0x7e5f1824 PrintInstance::BuildEndPrintEvent() const + 84
    1   AdobeAGM                                0x7e5fa503 PrintInstance::NextPrintEvent() + 8157
    2   AdobeAGM                                0x7e5291f3 PrintSession::GetNextPrintEvent() + 151
    3   AdobeAGM                                0x7e529c60 _AGMPrintSessionGetNextPrintEventProc_GetNextPrintEvent(AGMPrintSession*) + 40
    4   com.adobe.Acrobat.framework             0x8077def8 0x7fe0a000 + 9912056
    5   com.adobe.Acrobat.framework             0x801d0749 AcroSecurityBailOutImpl + 2003525
    6   com.adobe.Acrobat.framework             0x801d08eb AcroSecurityBailOutImpl + 2003943
    7   com.adobe.Acrobat.framework             0x8004ffe0 AcroSecurityBailOutImpl + 428764
    8   com.adobe.Acrobat.framework             0x800511fd AcroSecurityBailOutImpl + 433401
    9   com.adobe.Acrobat.framework             0x7ffbaa3b CopiesPagesPDE_Prologue + 9523
    10  com.adobe.Acrobat.framework             0x7ffbadce CopiesPagesPDE_Prologue + 10438
    11  com.adobe.Acrobat.framework             0x7ffbb298 CopiesPagesPDE_Prologue + 11664
    12  com.adobe.Acrobat.framework             0x7ffcc2ca CopiesPagesPDE_Open + 50672
    13  com.adobe.Acrobat.framework             0x7ffcc495 CopiesPagesPDE_Open + 51131
    14  com.adobe.Acrobat.framework             0x800066c5 AcroSecurityBailOutImpl + 127425
    15  com.adobe.Acrobat.framework             0x80006852 AcroSecurityBailOutImpl + 127822
    16  com.adobe.Acrobat.framework             0x80006a9b AcroSecurityBailOutImpl + 128407
    17  com.adobe.Acrobat.framework             0x8018fe6e AcroSecurityBailOutImpl + 1739114
    18  com.adobe.Acrobat.framework             0x801ffb92 AcroSecurityBailOutImpl + 2197134
    19  com.adobe.Acrobat.framework             0x801ff925 AcroSecurityBailOutImpl + 2196513
    20  com.adobe.Acrobat.framework             0x802e19ac AcroSecurityBailOutImpl + 3122344
    21  com.adobe.Acrobat.framework             0x8001fa66 AcroSecurityBailOutImpl + 230754
    22  com.adobe.Acrobat.framework             0x80020e3a AcroSecurityBailOutImpl + 235830
    23  com.adobe.Acrobat.framework             0x80165925 AcroSecurityBailOutImpl + 1565729
    24  com.adobe.Acrobat.framework             0x8016346a AcroSecurityBailOutImpl + 1556326
    25  com.apple.AppKit                        0x93d05fc5 -[NSWindow sendEvent:] + 7533
    26  com.apple.AppKit                        0x93c9f163 -[NSApplication sendEvent:] + 4788
    27  com.apple.AppKit                        0x93c30d11 -[NSApplication run] + 1007
    28  com.adobe.Acrobat.framework             0x7fe0d28d RunAcrobat + 2557
    29  com.adobe.Acrobat.framework             0x7fe0c9ce RunAcrobat + 318
    30  com.adobe.Reader                        0x00002e8b start + 2371
    31  com.adobe.Reader                        0x0000264a start + 258
    32  com.adobe.Reader                        0x00002571 start + 41
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib                  0x9b0ac90a kevent + 10
    1   libdispatch.dylib                       0x98338e10 _dispatch_mgr_invoke + 969
    2   libdispatch.dylib                       0x9833785f _dispatch_mgr_thread + 53
    Thread 2:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 3:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 4:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 5:: WebCore: LocalStorage
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.JavaScriptCore                0x9c9a7e81 WTF::ThreadCondition::timedWait(WTF::Mutex&, double) + 81
    4   com.apple.WebCore                       0x91b97501 WTF::MessageQueue<WebCore::LocalStorageTask>::waitForMessage() + 135
    5   com.apple.WebCore                       0x91b97454 WebCore::LocalStorageThread::threadEntryPoint() + 74
    6   com.apple.WebCore                       0x91b973b1 WebCore::LocalStorageThread::threadEntryPointCallback(void*) + 17
    7   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    8   libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 6:: com.apple.NSURLConnectionLoader
    0   libsystem_kernel.dylib                  0x9b0a9c22 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x9b0a91f6 mach_msg + 70
    2   com.apple.CoreFoundation                0x95c619da __CFRunLoopServiceMachPort + 170
    3   com.apple.CoreFoundation                0x95c6ab04 __CFRunLoopRun + 1428
    4   com.apple.CoreFoundation                0x95c6a1dc CFRunLoopRunSpecific + 332
    5   com.apple.CoreFoundation                0x95c6a088 CFRunLoopRunInMode + 120
    6   com.apple.Foundation                    0x9c5d80c4 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 378
    7   com.apple.Foundation                    0x9c5cbe25 -[NSThread main] + 45
    8   com.apple.Foundation                    0x9c5cbdd5 __NSThread__main__ + 1582
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 7:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 8:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 9:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 10:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 11:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 12:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 13:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be21 _pthread_cond_wait + 827
    2   libsystem_c.dylib                       0x97b4c42c pthread_cond_wait$UNIX2003 + 71
    3   com.apple.CoreServices.CarbonCore          0x9cd3de62 TSWaitOnCondition + 124
    4   com.apple.CoreServices.CarbonCore          0x9ccaf37d TSWaitOnConditionTimedRelative + 136
    5   com.apple.CoreServices.CarbonCore          0x9cd1167f MPWaitOnQueue + 200
    6   AdobeACE                                0x020310bd 0x2000000 + 200893
    7   AdobeACE                                0x02030ab5 0x2000000 + 199349
    8   com.apple.CoreServices.CarbonCore          0x9cd125e0 PrivateMPEntryPoint + 68
    9   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    10  libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 14:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be78 _pthread_cond_wait + 914
    2   libsystem_c.dylib                       0x97b4382a pthread_cond_wait + 48
    3   AdobeAGM                                0x7e4b0bc4 pthread_condition_base::Wait(pthread_scoped_lock_base&) + 26
    4   AdobeAGM                                0x7e4b0b1d AGMMessageQueueImpl::Pull() + 65
    5   AdobeAGM                                0x7e8a2b94 AGMWorkQueueTask::operator()() + 84
    6   AdobeAGM                                0x7e8a3e1f boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 75
    7   AdobeAGM                                0x7e4b09e1 thread_proxy + 45
    8   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    9   libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 15:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be78 _pthread_cond_wait + 914
    2   libsystem_c.dylib                       0x97b4382a pthread_cond_wait + 48
    3   AdobeAGM                                0x7e4b0bc4 pthread_condition_base::Wait(pthread_scoped_lock_base&) + 26
    4   AdobeAGM                                0x7e4b0b1d AGMMessageQueueImpl::Pull() + 65
    5   AdobeAGM                                0x7e8a2b94 AGMWorkQueueTask::operator()() + 84
    6   AdobeAGM                                0x7e8a3e1f boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 75
    7   AdobeAGM                                0x7e4b09e1 thread_proxy + 45
    8   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    9   libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 16:
    0   libsystem_kernel.dylib                  0x9b0ab83e __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x97b9be78 _pthread_cond_wait + 914
    2   libsystem_c.dylib                       0x97b4382a pthread_cond_wait + 48
    3   AdobeAGM                                0x7e4b0bc4 pthread_condition_base::Wait(pthread_scoped_lock_base&) + 26
    4   AdobeAGM                                0x7e4b0b1d AGMMessageQueueImpl::Pull() + 65
    5   AdobeAGM                                0x7e8a2b94 AGMWorkQueueTask::operator()() + 84
    6   AdobeAGM                                0x7e8a3e1f boost::function0<void, std::allocator<boost::function_base> >::operator()() const + 75
    7   AdobeAGM                                0x7e4b09e1 thread_proxy + 45
    8   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    9   libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 17:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 18:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 19:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 20:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 21:
    0   libsystem_kernel.dylib                  0x9b0ac02e __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x97b99ccf _pthread_wqthread + 773
    2   libsystem_c.dylib                       0x97b9b6fe start_wqthread + 30
    Thread 22:: com.apple.appkit-heartbeat
    0   libsystem_kernel.dylib                  0x9b0abbb2 __semwait_signal + 10
    1   libsystem_c.dylib                       0x97b4c7b9 nanosleep$UNIX2003 + 187
    2   libsystem_c.dylib                       0x97b4c558 usleep$UNIX2003 + 60
    3   com.apple.AppKit                        0x93e79816 -[NSUIHeartBeat _heartBeatThread:] + 2399
    4   com.apple.Foundation                    0x9c5cbe25 -[NSThread main] + 45
    5   com.apple.Foundation                    0x9c5cbdd5 __NSThread__main__ + 1582
    6   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    7   libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 23:
    0   libsystem_kernel.dylib                  0x9b0ac90a kevent + 10
    1   com.adobe.Acrobat.framework             0x804ff1fe AcroSecurityBailOutImpl + 5340410
    2   com.adobe.Acrobat.framework             0x8041adf7 AcroSecurityBailOutImpl + 4405491
    3   libsystem_c.dylib                       0x97b97ed9 _pthread_start + 335
    4   libsystem_c.dylib                       0x97b9b6de thread_start + 34
    Thread 0 crashed with X86 Thread State (32-bit):
      eax: 0x00000000  ebx: 0x7e5f17de  ecx: 0x7e3f96ac  edx: 0x00000001
      edi: 0x7eac1420  esi: 0x01ab4228  ebp: 0xbfffdea8  esp: 0xbfffde60
       ss: 0x00000023  efl: 0x00010286  eip: 0x7e5f1824   cs: 0x0000001b
       ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
      cr2: 0x00000014
    Logical CPU: 0
    Binary Images:
        0x1000 -     0x2fff +com.adobe.Reader (9.4.0 - 9.4.0) <8CEEE461-DF9E-46F5-816E-71DE8564A551> /Applications/Adobe Reader 9/Adobe Reader.app/Contents/MacOS/AdobeReader
       0x60000 -    0x61fff +com.adobe.eulaframework (??? - 1.0) <8AFCE794-4DCF-41B8-9D0F-30311D7BEB92> /Applications/Adobe Reader 9/Adobe Reader.app/Contents/Frameworks/EULA.framework/Versions/A/EULA
    0x2000000 -  0x210dfe7 +AdobeACE (??? - ???) /Applications/Adobe Reader 9/Adobe Reader.app/Contents/Frameworks/AdobeACE.framework/Versions/A/AdobeACE

    Right. After almost a day I finally sorted the problem.
    Adobe Reader worked under the spare Admin account so I deleted that in case it was confusing the installer.  I then rerpaired persmissions.  I then re-installed Reader.  Same problem "Internal Error"!!
    So, I re-created another Admin account and opened Reader.  No problem.  After clicking accept licence it opened up with a question to make default or not.  After this I hunted through every folder and found that Under 'User/Librarary/Application Support/Adobe' there was an Acrobat folder.  When I checked the account I normally use there wasn't, and never was??  So I copied pasted a copy of the Acrobat folder into the same location on the non working account and all is fine.
    Problem for me is, why did this happen?  I wasted almost a day on this. Is it a problem with the installer, the Macbook or Permissions.  I checked permissions and they are identical to those on the spare Admin account.  So why did the installer not create the Acrobat folder on the main account from where it was installed?  Reason it concerns me is with regard to updates.  Will they also screw up?
    I'll try to explore further as times goes on but for now I have to say I've had enough of Acrobat and Lion for one day.  "It just works".  Really???

  • Epson Artisan 810 gives error when prints from 10.6.2

    I know that Epson update 2.2 was released for 10.6.1. But it doesn't seem to help when printing from any application with 10.6.2. Should I downgrade back to 10.6.1? I have an Artisan 810 that won't print from 10.6.1 on a MacBook Pro that came out in September of 2009. It will print a sample page from the utility, and run the print head cleaning utilities, but won't print a document. It makes some indication that it can't deal with a postscript file in the error in the print queue the moment I send a print job from Neo Office or Safari. I'm connected via USB. Eventually I'd like to figure out how to add it to my Time Capsule's 802.11n network if possible. But first let's get it working under USB.

    I just went through this and seriously considered publishing the directions so I reckon this is my chance.
    When all was said and done, I only used the Epson utility to remove all of the installed Epson software, did not use any drivers as provided by them, including the already installed Photo R280 drivers for my other printer, and started over.
    Once done, I used the OSX Print & Fax System Preference to install the 810 as a new printer and let Software Update do its thing. It seems to load and install everything needed to make the thing work. Most of the Epson stuff seems useless and I find that the OSX Image Capture utility does a great job of running the scanner part.
    The most important thing I learned is that the directions and utilities as provided by Epson are not very helpful. The network setup utility they provide doesn't work at all on a Mac and looks exactly like the Windows XP version. I got very frustrated and simply accessed the menus myself on the 810's control panel and joined it with the wireless network manually. It was way easier and less frustrating then trying to get the Epson junkware working.
    As an aside, there are a kajillion little plastic thingies that can break and cause problems in this thing. Make sure to register it and get the free extended warranty
    Other than the installation pains this has turned out to be a pretty incredible little device. I already have a great scanner and an adequate photo printer, but I needed a fax modem, and for about the same price as the modem I ended up with a lot of other functionality as well.
    You can always page me in the lounge if you need any further input.
    -DP

  • Different Colors when printing from Photoshop and InDesign CS3

    Different Colors when printing from Photoshop and InDesign CS3
    I have the following problem:
    When printing from Photoshop or InDesign to a PostScript printer, Adobe recommends to let Photoshop handle the colors (I use the German version, so I don't know the exact term used, it changes slightly in all CS3 apps anyway).
    The manufacturer however told me to let the PostScript printer handle the colors.
    When I chose this option in Ps's print dialog and then choose ISO Coated as the printer pfofile, the results are fine.
    But when I place the exact same image in an InDesign file and print from InDesign or export to PDF and print via Acrobat, again using "Printer handles colors", the results are the exact same as if I had used Ps and chosen to let Ps handle the colors (way too saturated and a bit too red).
    ·Photoshop CS3
    ·InDesign CS3
    ·Test image is a TIFF in CMYK Fogra 27 Coated (which is also the working color space in Ps and ID.
    ·Printer: Xerox Docucolor 3535
    ·Printer profile: ISO Coated
    How can I make sure the printer handles the colors in other CS3 apps than Ps? I tried it with ID's print dialog (translated from the German version: Color Management > Options > Color Handling: PostScript-printer decides colors).
    Thanks a lot!

    RE: "You don't indicate what Xerox printers you have"
    In my first post I named it, is that the information you need?
    Docucolor 3535 using Splash 3535
    That's interesting, so I have to find a way to turn off the printer's Color Management function? I mailed them, hope they can tell me how to do it easily. They usually just tell me to not use any profiles and so on, but that's the general rule in this area, I'm really tired of hearing it. Everybody seems to think profiles and LAB mode are nuclear science and I should stay away from it.
    Anyway, the test image I'm using is a simple photograph (size A3, 300dpi), so no transparencies at all. I'm placing this image into an equally large ID file and print it from ID, then export it to PDF-X/3 and print it from Acrobat. Hope that helps.

  • CUPS Error message when printing from some applications

    Hi. I've got an issue when printing from some apps, but not others. Up to a few months ago everything was fine, then it started when Word would not print direct to my printer (Epson Stylus Pro 3880), not a big deal as I don't use it a lot and could print it through Safari if needed. Then more worryingly as a designer I found that PDFs stopped printing direct too, again I can print through Safari and Preview. Last night I installed a firmware update and now InDesign (CS4) is refusing to print!! Not great as printing via Safari/Preview doesn't give me the same level of control over my prints. Just checked both Illustrator and Photoshop and they both print okay. I get the same error code each time "error: /usr/libexec/cups/filter/pstoraster failed" Does anyone know what could be causing this?
    Thanks in anticipation. D

    cytan,
    As Matt pointed, an application printing to CUPS controls only the format of the input.  It has no direct control over the chain of filters inside the printing pipeline.  Acrobat isn't coded to use pstoraster, it is simpling submitting postscript to the print queue.  In an un-molested Apple supplied CUPS setup, that works fine.
    What is going on is that the CUPS system configuration got mangled by some third party bits.  In the Unix tradition, the configuration is fairly transparent, in the form of plain text files.  In particular, in /usr/share/cups/mime you will find out exactly how the filter pipeline is configured via a table of what filter to use to convert data between two mime types.  So we can inspect how the filters are setup and how a broken pstoraster is getting into the chain.
    I don't have a handy "before mangling" state, but I can clearly see the Apple specified filters to be invoked when the input data is application/postscript (in apple.convs).  I can also see a conflicting filter definition referencing the broken pstopdf (in mime.convs) but with a higher precedence, overriding the apple specified filter.  This is why, in reference to your points #1 and #2, simply removing pstoraster fails, because the filter configuration is what needs fixing.
    On my system, I found the pstoraster filter to be a shell script referencing a MacPorts install of ghostscript. I've since removed MacPorts, but that evidentally left the CUPS configuration in this broken state.  Without knowing exactly how the CUPS system was put into the broken state, fixing it can be a bit tricky.  Another posting suggested replacing the broken pstoraster with the Apple supplied equivalent of pstocupsraster.  That might work, but it would be better to simply remove the conflicting filter specification, which on my system is this bit in /usr/share/cups/mime/mime.convs:
    # pstoraster is part of GPL Ghostscript...
    application/vnd.cups-postscript        application/vnd.cups-raster     100     pstoraster
    Removing that will restore the Apple specified filter chain for postscript input.  With the filter specification gone, you are free to remove the pstoraster filter itself.
    On wating for Adobe to fix this...
    Acrobat provides enough things to scream about without pinning non-Acrobat problems on it as well.  Not only is this problem not the fault of Acrobat, but suggesting that Acrobat should reach into a CUPS system broken by some unknown third party and fix it is only going to complicate the situation by having two third party products trying to un-do each other's configuration of a system resource.   Do you really trust Adobe to fiddle with system components it doesn't own?  No, I didn't think so.  Adobe installers and updaters have enough trouble with the stuff they do own.
    So, why does this problem only seem to affect Acrobat (your point #3)?  I suspect it is simply that Acrobat is in the minority of submitting Postscript to the print queue.  Any print job produced via CoreGraphics APIs is going to enter the system via a different path (namely, PDF), but the Postscript method is completely legitimate and any application that submits Postscript will be affected in the same way as Acrobat.
    I hope this sheds some useful light on what is really going on with this problem.
    -john

  • HP Officejet 4630 Printer....how do change from the default setting when printing from the web?

    HP Officejet 4630.....Windows 8, 64-bit
    When printing from the web I am not able to change the print size.
    1. Click File on Menu bar
    2. Click Print open dialog box
    3. Click Properties open printing shortcuts
    Everything in Printing Shortcuts have a lock on it. Including Factory Default.
    Any and all help with this problem will be appreciated.
    Thank you in advance

    I posted this to the wrong board. Can it be move to the right one?
    thank you

Maybe you are looking for