I'm having the same problem. Windows 7 64-bit, 12 GB RAM and a fast processor.  TCS3 10.0.338. Updated Acrobat Pro X to 10.0.1, then 10.0.2.  I cannot print to PDF, but can print to a PostScript file, whiich distills successfully. I cannot save to PDF.

I tried this on Server 2008 R2 just to see what would happen, and got the same results (I know FM 10 is not supported there). I have also uninstalled and re-installed TCS3 on Windows 7.

I have a trial download of TCS3 on my work machine, a laptop with 4 MB of RAM running XP Pro SP3. It works fine there. I have used the same printer settings as this machine on my 64-bit system; no go. I have also tried updating the printer driver, adding a printer instance, changing ports, etc. I don't want to have to print to file, I just want it to work.

Anyone?

I get the "printing book" dialog box but nothing happens....the PDF is not created and no errors are reported.

Is there any chance that the filename, or any of the directory names above it, contain a comma?

If so, change the commas to underscores and try again.

Sounds like this is a now-known Win7 64bit issue that Adobe is working on.

Quite likely. But until the comma-in-the-Windows-filepath problem is fixed (and it doesn't appear to be fixed in FM9), it's going to continue to pop up, and can easily be mistaken for some other problem, and cause substantial time wasting. It can also prevent you from confirming that some other problem IS fixed or worked around.

As I recall from years ago, it took me quite a while to figure out that what had changed between "can print" and "can't" was a trivial change of a single otherwise legal filename character. There are complaints on the old newsgroup comp.text.frame about this, dated 2003, and claiming that the problem was at least 2 years old then. So this probably has been there since FM6 if not earlier.

I've never used a comma in a file name or path in my life; I'm curious as to why anyone would do so.

Multiple versions and archival copies of the same document.

We routinely generate two versions of the .ps output:

12345M_web.ps

and

12345M_print.ps (visible navs in doc suppressed)

Because the platform is Solaris, we'd gotten into the habit of using:

12345M,web.ps

We'll eventually have to migrate to Windows, and unless the comma bug is fixed by then, we'll have problems doing this.

When we release a new version of a manual, we make a second copy with a time-stamped filename, for archival purposes.

"12345M.pdf" is always the current version (of the web version).

The document source directory might also contain:

12345M_1999-03-17_jfk.pdf

12345M_2002-04-03_gwb.pdf

12345M_2010-07-23_ati.pdf

where "ati" are the Author's Three Initials.

Memorializing the vintage in the file name matters because we have multiple versions of the same document, and the directory timestamp isn't necessarily preserved in network copying. The author info is for knowing who to blame.

There are well-known characters [e.g. /\:;] that need to be avoided because they are legal on some OS'es and not on others. But I'd expect commas to work [now] because they apparently haven't been "illegal" since NetWare on DOS.

_______

Frame does work fine with spaces in filepath. Personally, I consider spaces in filepath to be extremely unwise.

I am having these issues too, and more.  I am migrating a large FrameMaker 8 legacy to FM10 on new 64-bit Mobile Workstations running Windows 7.  FM10 displays files OK but when I "Save as PDF", Console complains Tahoma font family is possibly corrupt.  The resulting PDF diplays in Acrobat with square symbols in place of Tahoma text.  I tried replacing Tahoma with old WinXP-Tahoma.  No luck.  I replace Tahoma with another font; same problem wi the other font.  In Acrobat, you cannot scroll past the square-symbol areas without crashing the NVIDIA display driver, which eventually recovers itself.

On top of that, FM10 frequently does not refresh when performing an operation (as above), rendering it inaccessible.  Using Windows Task Manager to alternately minimize, then mazimize restores the screen and functionality.

What is happening at Adobe?  Was FM10 not tested against Windows 7 in both 32/64-bit modes?  How can Adobe leave paying customers hanging?  The thread elsewhere in this forum is mostly dated in April; it is now past mid-May and I cannot find any signs of life at Adobe as to a quick and immediate resolution.

This is a show stopper!  Does FM10 support Windows 7?  Does FM10 support 64-bit O/S?

We're seeing this behavior in FM10 on Vista 64 bit also.

Rajat Bansal wrote:

 

This is a Win 7, 64-bit specific issue in "Print To PDF" route. We are actively looking at it.

 

There are couple of ways to workaround the problem.

 

• Use "File --> Save As PDF" option to directly create PDF from the source.
• Use "Print to PS" followed by Distiller

Regards,

Rajat Bansal

Sr Engineering Manager,

Adobe FrameMaker

With 10.0.1 update, this issue has been resolved for all 64-bit versions (Vista / Win7 / XP).

Regards,

Rajat Bansal

> There may be all sorts of neat DITA/XML improvements and other frills, but this FM10 seems poorly done.

> Any other horror stories out there?

I have to agree with Mike on this one. I have had more crashes with FM10 in the two weeks since installing it than I have had in several years of using FM8.

Right now, I have two books that have been consistently crashing when I save after an update. I "think" I may have solved the problem by saving the books as FM10 MIF and then back into book format. I've had other crashes that seem to be related to inserting a cross-reference. And a couple of other crashes that just seem based on general ornerieness.

This does not inspire confidence in a product, that up until this release, was almost bulletproof.

Regards

Keith

I'm running the 10.0.1 update.

I just had several crashes this morning. They all seem to be related to updating a book and then saving. I've been working with track text edits on. I may try disabling that feature to see if it makes any difference.

Regards

Keith

Thanks for the fix interpretation.  However, the Adobe updater installed 10.0.1 when it was available a few weeks ago and a recent patch too (10.0.1.402).  So, I am still getting the Save As PDF problem, along with crashing.

Regards,

Mike

Rajat,

Thanks for the reply and offer.  Regrettably, I cannot share company source files.  I am in the midst of some testing: I am finding some text tagged with certain character tags show up as gibberish in files but seem to work OK in other cases; it is affecting different char-tags, different fonts.  I'll try the CMYK/RGB suggestion and get back to you.

I am using FM 10, experiencing problems in creating a pdf of a  book. I use Adobe PDF as my print driver. The error said that a font,

HelveticaNeueCond, was not available, and could not be embedded. I had never heard of this font as being in my book, but I downloaded it and installed it on my C drive in my WINDOWS/Fonts folder. Still got the same error!

Also a pdf was made up to a certain page and then it failed. When I tried pdf ing that failed page, it worked. Then I tried to pdf the pages in between and it failed in a different spot.

This failure makes no sense.

I need help!

I have exactly the same problem. "Save As" works for individual files, but large books with multiple files take FOREVER. With Frame10 on WinXP a 100 page book took less than a minute, now I can't make a PDF at all. If I print to the PDF printer nothing happens. If I print to PS it also takes forever.

Adobe has to fix this!!!!!

Thanks for the feedback. I am on Windows 7, 64 bit, with FrameMaker 10 and Acrobat X Standard. I just installed the FM 10.0.2 patch. Now when I start to print a book, it seems to start normally, but takes an interminable amount of time, on the order of 5 minutes per page, even for simple text pages. This is a major hindrance to my work. Thanks

Clint Owen | Sr. Technical Writer | Crane Aerospace & Electronics | +1 425 743 8674 | Fax: +1 425 743 8113

I have tried it both ways and every combination that I can think of. I am printing the book, to end up with one PDF that combines all of the component files, as I have been doing for 11 years. For a small book with two files “Save As” seems to work OK, but for a large manual with 20 files it just crawls, whether I “Print To” or “Save As”.

Clint Owen | Sr. Technical Writer | Crane Aerospace & Electronics | +1 425 743 8674 | Fax: +1 425 743 8113