Hi All, OK, I thought it would be helpful to add the final note to this whole saga just in case other users experience this. Here's the summary again:
I have a Win 10, 64 bit system running Build 1709 and a Win 7 64 bit system. Both systems have FM 10 and 12 loaded. For years, and I do mean years, I have successfully printed to postscript files and then distilled the files to PDFs. My setup actually was in response to the long forgotten and improperly worded issue about relying on system fonts and not using document fonts: When you create a PS file, you must rely on system fonts and use document fonts. Please go to printer properties, "Adobe PDF Settings" page and turn OFF the option "Rely on system fonts only; do not use document fonts." Years ago, when I first encountered this error, I actually initially followed these instructions and did not check this option in two key places, and my systems lost the ability to print to PS. When I went and checked this option instead in two key places, voila, print to PS was just fine. (Remember Roger Shuttlesworth and Richard Combs from this list?? Yep, they assisted in trying to understand this issue.) About two days ago, my Win 10 system took updates. The updates did NOT change the build number, but nonetheless, updates were taken. As a result, all of a sudden, I started getting that long forgotten Fonts warning message and I could not print to PS. I could still Save as PDF, and I could print to a PDF, but I could not print to PS. I went in to Printers and Scanners, and selected the Adobe PDF printer, and checked both places where this option had always been checked and found that it was still indeed selected, so that did not make sense. (Adobe PDF Printing Preferences and Adobe PDF Printer Properties > Advanced > Printing Default.) In frustration, not understanding why my apparent years old fix was now not working, I not only went in and deselected the options in both places, and still no joy, but thanks to Matt Sullivan and his blog, I also cleared the option in a yet a third place - through the Print Setup dialog box in FM > Properties >Adobe PDF Document Properties. Now, voila, I can print to PS files again. I cannot fathom why an update would break this function, but still allow Save as PDF and Print to PDF work as they both require a PS file first, but. . . . I did some googling (and wailing and crying about Windows updates and PDF functions being hijacked) and although MS is supposedly not publicly rolling out 1803 right now because of this issue, some, but NOT all of the updates contained in Build 1083 did still make it silently into 1709, which could explain the issue. Also, MS is also still releasing security updates to address vulnerabilities in Windows 7 x64, and yesterday, my Win 7 took updates, and yep, drumroll . . . the same problem rose it's ugly head on my Win 7 system after years of no issues printing to PS, so I just implemented the same fix and all appears to be OK. I could rant about MS not giving a rat's patootie, etc., but we all have been down that road and know the feeling. All I can say is that the function and my sanity have been restored implementing this solution, so if any others run in to this issue on Build 1709 (despite everything that MS claims about the build and PDF functions), hopefully, this will help. Thank to this list and the users on this list and a special thanks to Matt Sullivan. Having access to resources and gurus like this is the only way survival is possible sometimes. TVB Tammy Van Boening Tammy dot vanboening at spectrumwritingllc dot com www.spectrumwritingllc.com _______________________________________________ This message is from the Framers mailing list Send messages to framers@lists.frameusers.com Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to listad...@frameusers.com
