Is FrameMaker 11 compatible with Windows 10?

[fredg_techwrite]

Our business is changing operating systems.

We are currently on Windows 7 and use FrameMaker 11 to generate PDFs.

Will FrameMaker 11 run on Windows 10?

Will FrameMaker 11 have experience issues with Windows 10?

Kind regards,

[Ian Proudfoot]

I've been using FrameMaker 11 on Windows 10 for well over a year with no problems. This includes heavy-duty, large-scale automated publishing jobs. Yes it's very stable for me.

Ian

[fredg_techwrite]

My thanks to everyone who took the time to answer my question.

I appreciate it.

Fred

[upasnad81657369]

One of the major issue I am experiencing is, every time I use short-cut to conditionilize the content the main window size decreases to half of the screen and it doesn't become normal until you restart the program.

It is annoying when you are working on multiple files/book level.

[Jeff_Coatsworth]

upasnad81657369​ - is your FM11 version fully patched up? Are you running it on a super large monitor or resolution? If you use the Conditional Tags pod to apply conditions to text does it misbehave in the same way as the shortcut?

[upasnad81657369]

I am using licensed software. It misbehaves only while using shortcuts. Basically the context menu gets open only out of the program window and window becomes small. I am using 11.0.0.380 and using extended monitor too.

[Matt S - Tech Comm Tools]

What's the shortcut you are using?

[upasnad81657369]

Esc q+U

[Matt S - Tech Comm Tools]

I'm not familiar with that shortcut.

Have you tried using Ctrl+4, Ctrl+5, and Ctrl+6 for conditionalizing content instead? Do they do the same odd thing to your monitor resolution?

[upasnad81657369]

it does same thing..it is just about opening a new context menu.

[Matt S - Tech Comm Tools]

That's the first I've ever heard of this issue, and not what happens to me.

Please report it at adobe.com/go/wish so that tech support can weigh in on what's happening.

Also, because Fm 11 significantly predates Win 10, you might want to download the Fm 2017 trial to see if the same thing happens with the current version on your system.

-Matt

[upasnad81657369]

well, this is the version for which we have bought licenses!

[Jeff_Coatsworth]

FM11 yes, but that includes any fixes that were issued after the initial release of the software - so try Help > Updates or go to the downloads section directly (Adobe - FrameMaker : For Windows) & grab the patches - I forget if FM11 still had sequential patches (must apply one at a time, increasing as you go) or if cumulative ones had started...

[Matt S - Tech Comm Tools]

Are you saying that you bought FrameMaker after purchasing WIndows 10?

Fm11 came out in 2012, and Fm 12 came out in 2014, while Win10 didn't come out til July 2015.

Historically, you won't see much in the way of patch releases (for Fm11 for example) once the new version of the software (Fm 12, 13, and 14 in this case) have been released. So if there's a solution, it's not likely to come from Adobe.

Have you tried downloading the Fm 2017 (v.14) trial + patch releases to see if this still happens on your system? If it does, it's unrelated to the Fm and Win10 environment.

[Matt S - Tech Comm Tools]

Also, you're on the initial release of Fm 11. Use the Help menu to update to the latest release of Fm11 (IIRC, it's 11.0.3)