"reference count underflow" printing NSDocument using "Save as PDF"

Hello, I'm getting a "reference count underflow" error trying to do a "Save as PDF" in a NSDocument class using the printOperationWithSettings method. There are no errors sending to the printer or viewing the output in preview. I found the post http://discussions.apple.com/thread.jspa?messageID=8708986&tstart=0 which was posted a year ago showing a 10 line program with the same error. I've got garbage collection turned on.
Is this still a know problem?
Thanks

Oh I do get the "reference count underflow" when compiling and running the above 10-line program.
If I create a new "Document-based" project and setting "Garbage Collection" to required, add an IBOutlet variable to reference the NSTextField generated, and add the following required method for printing:
- (NSPrintOperation *)printOperationWithSettings:(NSDictionary *)printSettings error:(NSError **)outError
NSPrintInfo *tempPrintInfo = [self printInfo];
if ([printSettings count]) {
tempPrintInfo = [[tempPrintInfo copy] autorelease];
[[tempPrintInfo dictionary] addEntriesFromDictionary:printSettings];
// textField is an IBOutlet variable
NSPrintOperation *op = [NSPrintOperation printOperationWithView:textField printInfo:tempPrintInfo];
return op;
I can print and "Open PDF in Preview" without errors, but get the "reference count underflow" with the "Save as PDF".
The sample application "SimpleStickies" created in 2009-10-14 and has by default Garbage Collection required, gets the same errors.
Is there a simple solution to creating a document-based project that allows "Save as PDF" to work.
This is a common function. I know I'm missing something obvious.
Thanks!

Similar Messages

Firefox 11 closes unexpectedly when I try to either 'print' or use 'save as'

Firefox 11 closes immediately when I either try to 'print' or use 'save as'

Hey sckrat,
Have you tried starting Firefox in Safe Mode? Hold down "shift" while Firefox is starting up. If the crash doesn't happen in Safe Mode, you should read [[Troubleshooting extensions and themes]].
There is also a lot of useful stuff in the [[Firefox crashes]] Knowledge Base article. If you've recently upgraded, you might want to check out [https://support.mozilla.org/en-US/kb/latest-firefox-issues this article] as well.
Hopefully this helps!

FAQ: Creating PDF Files from FrameMaker v.6 & earlier Documents -- Why you should not use "save as PDF"! -- Windows & MacOS Only!

An issue that has come up over and over again on several FrameMaker and Acrobat/PDF email lists as well on the corresponding Adobe User-to-User forums is that of creation of PDF files. FrameMaker 5.5.6 and 6 have what looks like a convenient feature that is supposed to allow you to create PDF files via simply saving the document as a PDF file. I have gone on record as advising end-users not to use this approach for reliable creation of PDF files from FrameMaker documents under Windows and MacOS with FrameMaker 6 and earlier. Why do I most vociferously offer this advice and why doesn't the problem get fixed? And how SHOULD you create PDF files from FrameMaker?
GOOD NEWS
I will start with the good news. The "next major version" of FrameMaker will indeed have "save as PDF" re-implemented in a manner that it will be as reliable as printing to the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS. I am personally working with the FrameMaker development organization to make sure this really happens and is fully and properly tested and debugged! Furthermore, this next major revision of FrameMaker, unlike FrameMaker 6, will come with a Distiller installer that will properly install the "Acrobat Distiller" printer instance under Windows and the "Create Adobe PDF" desktop printer on the Macintosh (of course assuring that the latest PostScript driver is also automatically and correctly installed).
DON'T USE "SAVE AS PDF"
But what's wrong with "save as PDF" as currently implemented?
The following are some of the SYMPTOMS reported over the last few years by FrameMaker users that were traced back to use of "save as PDF" under FrameMaker:
(1) No PDF file is produced at all, possibly with a log file showing not-readily apparent PostScript errors during distillation.
(2) The PDF file "loses" color in images. All or some images (raster, bitmap images, NOT vector artwork) appear in the PDF file in grayscale.
(3) The resultant PDF file is on the wrong paper size, i.e., the document's logical page size does not match the output page size as seen in Acrobat or Acrobat Reader.
(4) Some or all text in the resultant PDF file is blotchy looking or overly bold.
(5) Some or all text in the resultant PDF file cannot be searched or indexed.
(6) Some or all text in the resultant PDF file appears in Courier or in some other substitution font.
(7) Interword or intercharacter spacing is a bit irregular in the resultant PDF file.
(8) Content is missing in the margin areas of the page, i.e. you cannot do full-page bleeds.
(9) Some or all page content is missing (other than margin areas).
(10) Relatively inefficient PDF is generated.
If this list by itself isn't enough for you, please note that some of these symptoms are very subtle and may escape attention when the PDF is first viewed or printed. Oftimes, it is when one attempts to manipulate the PDF file in Acrobat or repurpose its content or even view or print on a system other than the one on which the PDF file was created, that some of these symptoms make themselves obnoxiously visible (or invisible in some cases I won't make any bad jokes here about graphic examples!).
It is important to understand that FrameMaker does NOT have its own native ability to create PDF. Any and all PDF created from FrameMaker documents is actually done by creating PostScript via the PostScript driver and having the Acrobat Distiller create PDF from that PostScript. The only exception to this is creation of PDF via the Acrobat PDFWriter driver, which is likewise not recommended (see below).
In order for "save as PDF" to work correctly, FrameMaker must do the equivalent of calling Printer Setup and selecting the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS followed by setting the driver's options correctly for paper size, page range, etc., followed by sending the proper commands to the driver to create PostScript.
Contrary to popular belief, PostScript as generated by the Windows and MacOS PostScript drivers is VERY device-dependent. The information in the PPD file associated with a printer driver instance provides critical parameters for generation of PostScript including:
Whether the printer supports color (Acrobat Distiller does)
What PostScript language level is supported (Acrobat Distiller 4.x and Acrobat Distiller 5.x are both PostScript language level 3)
Whether native TrueType support is available (Acrobat supports native TrueType as Type 42 fonts)
Available binary communications (Acrobat Distiller supports pure binary and ASCII, but NOT TCP, TBCP, or PJL)
Resident fonts (Acrobat Distiller doesn't really have resident fonts)
Available paper sizes and custom paper size availability (Acrobat Distiller supports a wide range of predefined sizes and continually variable "custom" sizes up to 200" by 200")
Margins / printable areas (for PDF and the Acrobat Distiller, there are no margins in which imaging is not permitted)
Device resolution (Acrobat Distiller can be set to any value from 72 to 4000 dpi; as a convenience, the Acrobat Distiller PPD provides a series of values for use by the driver. Since there is no inherent "resolution" of a PDF file, this parameter is used only for purposes of allowing PostScript programs that query for such a value to be satisfied and for the driver to be able to communicate this value to the operating system and/or application as required.)
Paper handling (totally irrelevant to Acrobat Distiller if input or output tray selection via "setpagedevice" is found in the PostScript stream, it is ignored by Acrobat Distiller)
Thus, if the wrong printer driver instance is selected (i.e., it isn't associated with the Acrobat Distiller PPD file) or that driver instance is improperly configured, improper PostScript will result and one or more of the symptoms described above can occur. As currently implemented, FrameMaker depending upon version will not necessarily choose the correct printer driver instance and/or correctly parameterize the print job via driver setup options. In fact, FrameMaker 5,5,6 might even try to generate PDF via calling a PCL driver, FAX driver, or even a non-PostScript inkjet printer!
DON'T USE PDFWRITER
The Acrobat PDFWriter is a relic of older versions of Acrobat. In fact, it is no longer installed by default in the "easy install" or the "typical install" of Acrobat 5. It hasn't really be updated since Acrobat 3 and only supports PDF 1.2. It is a GDI (Windows) / QuickDraw (MacOS) driver that directly generates PDF without any intermediary PostScript. Since it is not a PostScript printer driver, applications cannot pass through EPS graphics and/or PDFMark information (used for a wide variety of purposes by FrameMaker). For EPS graphics, most applications will send the low resolution TIFF (or PICT) EPS header in lieu of the PostScript text, if they send anything at all, to the driver. Forget about links, structure, or any other PDF "goodies." Expect that PDFWriter will fully "bite the dust" in the next major version of Acrobat.
SO HOW DO I GENERATE PDF FILES FROM FRAMEMAKER 6 & EARLIER?
The ONLY method that is really reliable for producing PDF files with FrameMaker 6 and earlier requires the generation of PostScript via a properly set printer driver instance associated with the Acrobat Distiller PPD and distillation of the resultant PostScript by Acrobat Distiller.
Case 1: FrameMaker and the Full Acrobat 4.05 or Acrobat 5.0x Products
PDF file from a "chapter" -- print directly to the Acrobat Distiller printer instance (Windows) or the Create Adobe PDF desktop printer (MacOS) already installed by Acrobat. If you check the "Acrobat data" option, then make sure to UNcheck the "print to file" option that gets set at the same time. As a result, the driver will automatically send the generated PostScript to the Distiller for you and delete the intermediate PostScript when done.
PDF file from a "book" -- print directly to the Acrobat Distiller printer instance with the "print to file" option checked (Windows) or the Virtual Printer desktop printer (MacOS) associated with the Distiller PPD (see details below under Case 2/MacOS). You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
In both the above sub-cases, the default driver options generally will be OK, but check on paper size and communication protocol (Use pure binary, not ASCII, for optimal performance AND no CTRL-D characters under Windows. Make sure to set Level 3 only and Binary under MacOS. Font inclusion "All" for Acrobat 4.05 and "None" for Acrobat 5 under MacOS.). With Acrobat 4.05, make sure you preset the Distiller to use the joboptions you want. With Acrobat 5, you can set this on a job-by-job basis via the driver printer setup interface (or print dialog on MacOS).
Case 2: FrameMaker 6 and the Bundled Acrobat 4.05 Distiller
Windows -- Create a new printer driver instance using the latest version of the Adobe Universal PostScript Driver Installer, downloadable from Adobe's web site AND the Acrobat Distiller PPD file (located in the XTRAS subdirectory of the Distiller directory). This driver instance should be set to print to the local port named "FILE:". Name this driver instance as "Acrobat Distiller". The default driver options generally will be OK, but check on paper size and communication protocol (use pure binary, not ASCII, for optimal performance AND no CTRL-D characters). Make sure you preset the Distiller to use the joboptions you want. Print directly to this Acrobat Distiller printer instance. Make sure that the "print to file" option is checked. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
MacOS -- Install the latest version of AdobePS 8.7.x, downloadable from Adobe's web site. In FrameMaker, go to Page Setup and select the "Virtual Printer" and go to the "Virtual Printer" window pane. Select the Acrobat Distiller PPD file (located in the XTRAS subfolder of the Distiller folder). Print directly to the "Virtual Printer" (Make sure to set Level 3 only, Binary, and font inclusion "All".). Make sure you preset the Distiller to use the joboptions you want. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
Case 3: Acrobat 3
Acrobat 3 is not officially supported for the latest OS versions and I personally would no longer recommend its use for generation of PDF files given that Acrobat 5.0.5 is the current version of Acrobat.
- Dov

You're asking a lot of ancient Acrobat to work with an Office that never existed when it was made. "Just updated my office suite" is a massive change, and Window 8 didn't exist at that time either...

Using "Save as PDF" changes fonts

I have some documents in czech in FrameMaker 12. When I print to pdf the documents converts all right, but when using "save as pdf" all arial fonts are replaced with Times New Roman and the entire process seems to use a lot of time and computer memory. The Save as PDF always have been buggy, but some of my customers apparently seems to need this feature. How does one troubleshoot the strange behaviour of font replacement ?
Best regards
Bjørn

Usual suspects:
AdobePDF printer instance is not set as the default (use SetPrint utility available from http://sundorne.com/FrameMaker/Freeware/setPrint.htm).
Printer vs. soft fonts (i.e. installed fonts)
Are you using a codepage Arial font for Czech or a unicode enabled version?
Distiller joboptions - embed & subset all fonts; Cancel if embedding fails
Avoid CMYK option with OTF Pro and WGL-TT fonts unless you specifically are creating output for colour press work

IPhoto 7.1.1 Under Leopard 10.5.1 Will not print photo under "save as PDF"

iPhoto 7.1.1 Under Leopard 10.5.1.
Select a photo, choose "print" icon at bottom of iPhoto window.
Choose "print".
Choose "Save as PDF".
Result: Unknown error message appears with white space (no text) in message box, but with "OK" button.
Hit "OK button".
RESULT: iPhoto prints a screen shot of the iPhoto window and renders it to a PDF file.
In other words, *the print function under iPhoto does not work*. It yields an error every time that does not have a message, then *instead of printing the selected photo, takes a PDF screen shot of the iPhoto window*.
This is an example of poor programming. And of course, there is no way to fix it, or to get help.
Is anyone else having this problem?

This is an example of poor programming.
How do you come to this conclusion. It's working fine for me. You're the first to report such an issue.
First repair disk permissions with Disk Utility and delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your User/Library/Preferences folder. A corrupted pref file can cause all sorts of unusual performance problems. If that doesn't help, log into another account and try from there. If it still doesn't work a reinstall of iPhoto seems warranted. To reinstall iPhoto you'll have to delete the current application and all files with "iPhoto" in the file name that reside in the HD/Library/Receipts folder.
It iPhoto performs correctly in the other account then your primary account is the culprit and may be a preference file other than iPhoto's that's at fault. To determine if that's the case try the following;
Trouble Shooting Preferences
Go to HD/Users/Your_name/Library. Move the Preferences folder (in its entirety) to the Desktop and make a second copy of it so you have Copy A and B. Now try the the process again and determine if problem is fixed.
If the problem IS fixed, then go to the new Prefs folder that the OS will have created and open it up.
Open Copy B on the Desktop and select all of the items inside. Drag them into the open new library folder. When the Copy window comes up check the Apply to All check box and then click on the Don't Replace button as seen here. That will keep the new files created and bring back all of the others.
If the problem is NOT fixed, trash the new Prefs folder and move the intact Copy A folder back to the Library folder .
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Office X bulleted copy won't print; can't save as PDF

This is an odd problem. I've printed a document several times now in different fonts using Word X. Every time, it prints until it gets to bulleted text. Then it stops printing - including any non-bulleted text following the bulleted text. Weirder yet, it won't allow you to save the file as a PDF. It says it will but the PDF never shows up. If I un-bullet the copy (using formatting), everything is just fine.
Any ideas? Thanks.

Okay, upon further review, there were still more Arial and Arial Black fonts in another folder. Once I got rid of those, everything is fine. But what a mess! The average Mac user who runs into this problem from installing SL will have no idea how to fix it. I'm a big Apple fan, but this is something that should only happy to PC people. I'm sure Apple could have found a way to get rid of duplicate fonts automatically.

Can I edit with Smart Print the same way I could with Smartweb Printing and then save as PDF files.

With Vista basic and SmartWeb Printing you had the option to edit your pages and then to save or print them in the PDF format. This way you could customise various pages pages, save them to a file and then reopen the whole file to see if you wanted to make any further changes before printing the final copy.
sharjor

Steve M. wrote:
I installed the full suite of Canon printing, scanning, faxing and whatever else software they provide for this all-in-one.
Maybe you don't need that. I prefer using Apple's Image Capture for scanning.
Right now I am working on scanning documents into PDFs. The Canon software lets me create multipage PDFs which is something I've been wanting to do. My question is, is it best to scan images as JPEGs and then save them as a multipage PDF or is it best to scan into PDF directly (which the scanner seems to offer as well) and then save as a multipage PDF? I'm thinking in terms of the best optimization of file size vs. image quality and things like that.
Let the software do it for you. That will be fewer steps for you. Image-based PDFs are going to be large. There is no way around that. If they are too large, you can use Preview's Save As feature and play around with the Quartz Filter.
Is the scanner actually doing anything differently when scanning into JPEG vs. PDF? Or is the scanning all the same and it's just the saving of the file that is different?
Scans are scans. The JPEG file format is lossly and will look worse than other types. If you are scanning in photographs, the JPEGs will look good. If you are scanning in crisp text, JPEGS will have lots of artifacts and look bad.
In general what dpi setting is usually sufficient to use to scan a basic text document without taking up too much file space?
I pretty much always keep it at 300 unless I need something special or when the original is really small and I intend to blow it up.

SOS please -- How do I Print a page, Save as PDF, and retain the live links? Mac 10.6.7 / FF 4.0.1 / never had problem b4, now have looked everywhere, what's changed? thanks thanks

got it all into the question - i think!

Found it.
The restore password is not the same as the passcode to access the iPad. (After putting 6-digit codes in all day, I think I'd been conditioned to continue using those codes.) I found the backup password in the Keychain.

Print - save as pdf with Aplescript

Hello,
I would like to know how to script : "Print" with a "save as pdf" on application.
ie: I would like to print a web page from Safari, and select save as pdf to save the page in a pdf format document.
(I don't want to use Adobe...)
Thanks a lot.

I realized that it still might be a little confusing to figure out how to use that Automator action. So I will give you a step-by-step of mine.
Get Specified URLs->Download URL as PDFs(this is the action I linked before)(Note: I set the where to a temporary folder where no other file will ever be)->Pause for 5 seconds->Move Finder Items(Select a destination folder where you want to have your PDF in permanently)->Run Applescript (A)-> Run Applescript (B) -> Run Applescript (C)
Applescript (A)
--For whatever strange reason when you create the PDF it names it some random name so I rename the PDF after the current date in the YYYYMMDD format so that you can easily find the PDF on a later date.
on run {input}
repeat with i from 1 to (count of items in input)
tell application "Finder"
set thisItem to (item i of input as string)
set thisName to (the name of (file thisItem))
set newName to (do shell script "date '+%Y%m%d'" & ".pdf") as string
set the name of the file thisItem to newName
end tell
end repeat
return input
end run
Applescript (B)
--This script deletes the file from the original downloaded location. You have to do this because the previous applescript renamed the PDF and copied it to a new location.
do shell script "rm /path/to/file/that/was/set/in/the/DownloadURLsasPDF/action/*.pdf"
Applescript (C)
--Prints the PDF
set theLocation to ("path:to:new:location")
set fileName to (do shell script "date '+%Y%m%d'" & ".pdf")
set theFile to theLocation & fileName as text
tell application "Finder"
print file theFile
end tell
I hope this works for you. I use it every day to save a PDF of stock reports. If you have any questions feel free to ask.

Aio remote only allows save to pdf when trying to print picture

brand new HPm MFP M127 fw. have web services enabled and all the other stuff noted in the printer installation. Installed aio remote on galaxy s3 with droid 4.4.2. went ahead and installed HP print services from GP as well.
Browse to a photo in the gallery, select print and the print setting dialog appears, but no option to print. only save to PDF. When I try to go ahead and let it save, to see if it will let me print after, it fails. What am I missing here?

Hi,
The HP Laserjet Pro M127 is not supported by the HP All-In-One Remote app, therefore it won't allow printing to the printer, as you may find listed within the HP Consumer LaserJet printers section:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02814760&lc=en&cc=us&dlc=en&product=3204788#N39...
You may print using the HP ePrint app or Print Solution for Android as listed below:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c03722645&tmp_task=setupCategory&cc=us&dlc=en&lc...
Say thanks by clicking the Kudos thumb up in the post.
If my post resolve your problem please mark it as an Accepted Solution

Root Account - No 'save as pdf' print option

The root account doesn't have the print option to 'save as PDF'. My other user accounts do have that option.
Any suggestions on how to enable the 'save as PDF' option for an account or if something special is needed for the root account?
-tjw

I log in as root because I don't like having to fiddle with permissions. For example I installed wireshark and it wasn't allowed to capture packets from the network interface because it needed special permissions. Even though the account I was using was a sys admin account I still needed log in as root; change permissions somewhere.
I decided that I would just log in as root. Yeah yeah its so very dangerous...no its not.
But; now that there are these little goofy things like so 'save as pdf' button forcing me to click 5 times to to the save as a pdf option under the preview button I may go back to a vanilla sys admin account.

? left out past name ability in Print dialog " save as PDF "

i , like many use the print dialog to save as PDF. In the interest of minimizing steps I would clik on a file, highlight the name, copy it with command C with my left, and hit print, command P with my right. quick track ball over to save as PDF and left hand paste in the name with command V. Now with the most advanced iteration of Mac os ican sync my pictures with everything else owned Apple but don't have the time because I can no longer do a time saving, world famous Mac originated "cut and paste" that i"ve been able to use since OS 4.3 to get done my work. What is going on ? By itself this wouldn't be such a big deal to fix, but this is just one of the truly cool tools no longer available for work. Is the mac finally the toy that Apple spent years making sure it would never become. Why not slown down and do it right and maybe not so often.
Tom

What do you mean you can't Cut and Paste, it is still the same as it has always been. Cut= cmd+x Paste= cmd+v

PDF printer no longer an option? Need a better choice than "save as pdf"

We ungraded our work computer to snow leopard. Since then the pdf printer no longer works. In leopard to make a high quality pdf of our ad we would hit command print and select acrobat 7.0 as our printer. That no longer works in snow leopard so now we have to use "save as pdf" the problem with this is it doesn't compress the file and saves it as lower quality than the newspaper companies like. What's the best way to go about this now that snow leopard screwed things up?

Adobe has a Knowledge Base article, "Can't Print PDFs - Mac OS X 10.6" which explains that changes in Snow Leopard caused the old and well-loved PDF printer to disappear, or at least stop working.
Specifically for InDesign, I've read that the best alternative in Snow Leopard is to go the old-school route and print to a .ps file, then run that through Acrobat Distiller. Others have had success with exporting to PDF (as opposed to going through the Print dialog and using the Save As Adobe PDF).

Fm9p237, probs with Save As PDF, turns *some* anchored frames blue

I am using Save As PDF because have to create CMYK PDF. I know how to do that. The issue now is that FrameMaker is sticking blue boxes around only *some* of the graphics.
They are all EPS graphics imported by reference into anchored frames. These boxes do not appear in the FM file.
The boxes clearly are the anchored frame bounding boxes.
Any ideas? Any switch I should set? Any ritual incantations that will appease the FM Postscript generator?
Thanks for your help, Becky

Hi Bernd and Art,
Yes, I am using spot colors. I did some more testing and here is what I found:
Use Save As PDF in FM-->all colors except for spots are correctly converted to CMYK. Bitmap screenshots are also converted to CMYK. If I convert the spot colors to CMYK SWOP in Acrobat 9, using its preflight tool, the spots are all converted to the same CMYK values that they were assigned in Frame. BUT there are random blue boxes in the doc, clearly where FM for some reason colored the bounding box of an anchored frame or a table cell.
Print to Adobe Printer instance in FM with the Press Quality job options-->All colors come out CMYK, including spot colors and bitmapped
and there are no random blue boxes BUT the CMYK conversions of the spot colors are wrong.
My choice: Save As PDF. I will just remove the blue boxes with Acrobat.
I considered PitStop Pro and downloaded the trial copy, but its userdoc is terrible and I can't figure out how to batch-convert the incorrect CMYK colors t. Can't find any good help on line either. Too much bother.
Sigh. Adobe, are you listening? It's ridiculous that the company that produces Photoshop can't make CMYK color conversion work in Frame.
TThank you, Bernd and Art. I appreciate your feedback very much.
--becky

Why won't Save as PDF work?

iPhoto hangs up on the first photo book page with an image containing a warning triangle if I try to use Save as PDF. Has anyone else had this happen? I presume it means that the image won't send to the printer, either? Yet, The Missing Manual says you can send photos with warning triangles and let them be printed blurry. Who knows about this? I'd appreciate real experience. Thanks.

Try previewing (and saving the PDF) using this method - http://support.apple.com/kb/HT1040
LN

"reference count underflow" printing NSDocument using "Save as PDF"

Similar Messages

Maybe you are looking for