ClipboardFormatsPriorities maker.ini setting in Frame 10?

[M_Boyd]

I recently installed Frame 10 and I want to change the ClipboardFormatsPriorities setting so that "TEXT" is the first option in the list. I've done this in previous versions. Is this still possible in 10? If so, what did I do wrong?

Here's what I tried:

1. Located the maker.ini file in the following directory: C:\Users\mboyd\AppData\Roaming\Adobe\FrameMaker\10.
2. Made a backup of the original maker.ini file.
3. Opened maker.ini in a text editor and saw that the setting was no longer included.
4. Tried adding it. I added the following line first to the [Preferences] section and then to the [Frame] section:
   
   ClipboardFormatsPriorities=TEXT, UNICODE TEXT, MIF, RTF

Result: Nothing changed. MIF was still the default when I copied and pasted.

Granted -- changing the default from OLE to MIF was definitely an improvement, but I'd still like the default to be TEXT. Let me know what I'm doing wrong.

Thanks!

Melanie

[M_Boyd]

Oh, I forgot to mention that I closed Frame before editing maker.ini and restarted it afterward.

[Jeff_Coatsworth]

Mine reads ClipboardFormatsPriorities=TEXT, FILE, MIFW, MIF, RTF, OLE 2, META, EMF, DIB, BMP, UNICODE TEXT

but it's in the c:\program files\adobe\adobeframemaker10\ folder in the section

[M_Boyd]

A few weeks ago, I tried editing the maker.ini file under the Program Files directory. I had to go though some hoops. Even though I have admin privs on my computer, I cannot edit the file and save it. However, I can save it to a different location and then copy the edited version over the original version. (I realize that makes no sense, but Windows doesn't always make sense.) Anyway, after I did that I couldn't open Frame. I had to uninstall and reinstall it.

But apparently other people are editing the maker.ini file in that location, so I tried it again. Same results. FrameMaker generates a log file when I try to open it that shows a stack trace.

This is annoying. I've been using FrameMaker since version 3, and I've edited the .ini file who knows how many times. What's up with version 10??

[Jeff_Coatsworth]

Hmm, looks like some crap got copied into my last reply.

Are you running Win7 or Vista? In those newer O/S's you have to give yourself (as admin) the rights to mess around with your own C:\ drive - it doesn't automatically follow when being an admin like it used to under WinXP. Mr. Bill's just trying to protect us from ourselves ;>)

[M_Boyd]

Windows 7. How do I give myself privileges?

[Jeff_Coatsworth]

From what I remember, you have to use Explorer to get down to the C:\ drive root, then right-click and select Security (or something like that) and give yourself Full Control. It will take a while as it goes through and applies the change to all files & folders under C:\

[M_Boyd]

Thanks for the info. But I don't think I'll try editing the maker.ini file again. Uninstalling and reinstalling is eating way too much of my time!

[Jeff_Coatsworth]

What are you uninstalling & reinstalling? There's no need to do that as far as I can see from your posts.

[M_Boyd]

Read my third post more carefully. Both times I've made a change to maker.ini under the \Program Files, Frame won't start again until I uninstall and reinstall.

[Jeff_Coatsworth]

You shouldn't have to reinstall it - just restore the backup copy of the maker.ini you made before monkeying with its innards. You did make a copy, didn't you ;>)

[M_Boyd]

Yes, I made a backup, and I did try restoring the backup .ini file before reinstalling. Believe me, I tried several things.

It doesn't make any sense to me, either. It looks like something else is becoming corrupted. If I wanted to spend a lot of quality time with Adobe Support, I might be able to get to the bottom of it. But since it only happens when I try to edit the master maker.ini file, I don't think it's worth pursuing.

My original assumption was that I should be able to make the change in the personal maker.ini under \Users\AppData and that would have an effect. When it didn't have any effect, I thought I was just entering the setting incorrectly, which is why I posted here. But I've tried entering your setting, and:

• Entering it in the personal maker.ini has no effect.
• Entering it (or anything else) in the master maker.ini corrupts something and I have to reinstall.

At this point, I'll just be content to live with the .ini file as it is.

Thanks for the responses.

[Jeff_Coatsworth]

Were you able to give yourself "full rights" as a local admin?

[M_Boyd]

Yes -- thanks!

[Bob_Niland]

Both times I've made a change to maker.ini under the \Program Files, Frame won't start again until I uninstall and reinstall.

When you did that, were you doing anything about the custom copy under /Users//AppData ?

Frame is obviously checking both locations, and I'm wondering if having a newer mod timestamp on the "master" file vs. the "user" file is what's causing it to enter self-destruct-enable mode.

[M_Boyd]

Since I tried editing the file under /Users/AppData first, then it's true that the master copy would have had a later time stamp.

[kmacdowe+brdcom]

M Boyd I am having the same problems with FM10 now. The ini changes do not work and if I modify the Program Files instance FM blows up and I have to reinstall. Did anyone solve this mystery?

[M_Boyd]

No. Nothing I tried worked, and I got tired of reinstalling the product. Sorry I can't be more help.

[kmacdowe+brdcom]

Thanks for letting me know. Very frustrating for a product to go backwards

in usability.

[Jeff_Coatsworth]

Are you running Win7? Editing the maker.ini's shouldn't cause FM to fail to launch - are you getting an actual error message?

[M_Boyd]

Jeff, you asked about Win7 back in Feb. 🙂

As I explained before, whenever I edit the .ini file under \Program Files, Frame won't open and generates a log that shows a stack trace.Uninstalling and reinstalling is the only way to resolve the problem.

[Jeff_Coatsworth]

@M_Boyd - Sorry, I was replying to @kmacdowe+brdcom to see if they were running the same o/s as you. My suspicion in your case is something to do with rights. If you're getting a hard error, I hope you've sent it into the FM tech guys and reported it to Adobe Support.

I've just installed a copy of TCS3 on a Win7 laptop, so I'll have a chance to see if I can reproduce what you've reported, as I use the TEXT paste quite often while hauling material in from Word.

[M_Boyd]

Sorry Jeff! Yes, I did send the log to Adobe support.

[Van Kurtz]

It is my understanding that one should not edit the maker.ini file that is in the Programs directory. Each user has a personal copy located in:

C:\Documents and Settings\user_name\Application Data\Adobe\FrameMaker\9(or 10)

This maker.ini file is not a full copy of the one in Programs but it contains your personal changes. So try adding or editing the line in that file. When FrameMaker opens it first reads the file in the Programs folder and then the one in your Documents and Settings folder.

[M_Boyd]

Already tried that. See my post from Jan 12.