Skip navigation
M_Boyd
M_Boyd
Currently Being Moderated

ClipboardFormatsPriorities maker.ini setting in Frame 10?

Jan 11, 2012 3:39 PM

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

2392 Views   31 Replies   Latest reply: kmacdowe+brdcom, Jun 6, 2012 11:44 AM
 
Replies
  • M_Boyd
    Currently Being Moderated
    1. M_Boyd,
    Jan 11, 2012 3:40 PM   in reply to M_Boyd
    Report

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

     
    |
    Mark as:
  • Jeff_Coatsworth
    Currently Being Moderated
    2. Jeff_Coatsworth,
    Jan 12, 2012 6:35 AM   in reply to M_Boyd
    Report

    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 Re: ClipboardFormatsPriorities maker.ini setting in Frame 10? section

     
    |
    Mark as:
  • M_Boyd
    Currently Being Moderated
    3. M_Boyd,
    Jan 12, 2012 8:54 AM   in reply to Jeff_Coatsworth
    Report

    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??

     
    |
    Mark as:
  • Jeff_Coatsworth
    Currently Being Moderated
    4. Jeff_Coatsworth,
    Jan 12, 2012 9:10 AM   in reply to M_Boyd
    Report

    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 ;>)

     
    |
    Mark as:
  • M_Boyd
    Currently Being Moderated
    5. M_Boyd,
    Jan 12, 2012 9:38 AM   in reply to Jeff_Coatsworth
    Report

    Windows 7. How do I give myself privileges?

     
    |
    Mark as:
  • Jeff_Coatsworth
    Currently Being Moderated
    6. Jeff_Coatsworth,
    Jan 12, 2012 9:54 AM   in reply to M_Boyd
    Report

    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:\

     
    |
    Mark as:
  • M_Boyd
    Currently Being Moderated
    7. M_Boyd,
    Jan 12, 2012 11:04 AM   in reply to Jeff_Coatsworth
    Report

    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!

     
    |
    Mark as:
  • Jeff_Coatsworth
    Currently Being Moderated
    8. Jeff_Coatsworth,
    Jan 12, 2012 11:15 AM   in reply to M_Boyd
    Report

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

     
    |
    Mark as:
  • M_Boyd
    Currently Being Moderated
    9. M_Boyd,
    Jan 12, 2012 11:22 AM   in reply to Jeff_Coatsworth
    Report

    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.

     
    |
    Mark as:
  • Jeff_Coatsworth
    Currently Being Moderated
    10. Jeff_Coatsworth,
    Jan 12, 2012 11:36 AM   in reply to M_Boyd
    Report

    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 ;>)

     
    |
    Mark as:
  • Error7103
    Currently Being Moderated
    11. Error7103,
    Jan 12, 2012 11:39 AM   in reply to M_Boyd
    Report

    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.

     
    |
    Mark as:
  • M_Boyd
    Currently Being Moderated
    12. M_Boyd,
    Jan 12, 2012 11:47 AM   in reply to Error7103
    Report

    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.

     
    |
    Mark as:
  • M_Boyd
    Currently Being Moderated
    13. M_Boyd,
    Jan 12, 2012 1:28 PM   in reply to Jeff_Coatsworth
    Report

    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.

     
    |
    Mark as:
  • Jeff_Coatsworth
    Currently Being Moderated
    14. Jeff_Coatsworth,
    Jan 12, 2012 1:48 PM   in reply to M_Boyd
    Report

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

     
    |
    Mark as:
  • M_Boyd
    Currently Being Moderated
    15. M_Boyd,
    Jan 13, 2012 1:12 PM   in reply to Jeff_Coatsworth
    Report

    Yes -- thanks!

     
    |
    Mark as:
  • lsk2002
    Currently Being Moderated
    16. lsk2002,
    Jan 13, 2012 1:47 PM   in reply to M_Boyd
    Report

    A topic on an email from framers@lists.frameusers.com was to copy and paste straight from a Word document. Below was the correct answer and it works great.

     

    Although a co-worker of mine told me just to use paste special and select text...didn't know that.

     

     

    Edit the line:

    ClipboardFormatsPriorities=FILE, OLE 2, EMF, META, DIB, BMP, MIFW, MIF,

    RTF, UNICODE TEXT, TEXT

     

    Change the line to:

    ClipboardFormatsPriorities=UNICODE TEXT, FILE, OLE 2, EMF, META, DIB,

    BMP, MIFW, MIF, RTF,  TEXT

     

    ls

     

    Message was edited by: lsk2002

     
    |
    Mark as:
  • kmacdowe+brdcom
    Currently Being Moderated
    17. kmacdowe+brdcom,
    May 1, 2012 3:33 PM   in reply to M_Boyd
    Report

    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?

     
    |
    Mark as:
  • M_Boyd
    Currently Being Moderated
    18. M_Boyd,
    May 1, 2012 3:36 PM   in reply to kmacdowe+brdcom
    Report

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

     
    |
    Mark as:
  • kmacdowe+brdcom
    Currently Being Moderated
    19. kmacdowe+brdcom,
    May 1, 2012 3:51 PM   in reply to M_Boyd
    Report

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

    in usability.

     
    |
    Mark as:
  • Jeff_Coatsworth
    Currently Being Moderated
    20. Jeff_Coatsworth,
    May 2, 2012 7:32 AM   in reply to kmacdowe+brdcom
    Report

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

     
    |
    Mark as:
  • M_Boyd
    Currently Being Moderated
    21. M_Boyd,
    May 2, 2012 8:48 AM   in reply to Jeff_Coatsworth
    Report

    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.

     
    |
    Mark as:
  • Jeff_Coatsworth
    Currently Being Moderated
    22. Jeff_Coatsworth,
    May 2, 2012 9:05 AM   in reply to M_Boyd
    Report

    @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.

     
    |
    Mark as:
  • M_Boyd
    Currently Being Moderated
    23. M_Boyd,
    May 2, 2012 9:10 AM   in reply to Jeff_Coatsworth
    Report

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

     
    |
    Mark as:
  • Van Kurtz
    Currently Being Moderated
    24. Van Kurtz,
    May 2, 2012 10:12 AM   in reply to M_Boyd
    Report

    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.

     
    |
    Mark as:
  • M_Boyd
    Currently Being Moderated
    25. M_Boyd,
    May 2, 2012 11:44 AM   in reply to Van Kurtz
    Report

    Already tried that. See my post from Jan 12.

     
    |
    Mark as:
  • Arnis Gubins
    Currently Being Moderated
    26. Arnis Gubins,
    May 2, 2012 12:32 PM   in reply to M_Boyd
    Report

    Melanie,

     

    Did you have all 11 parameters in the modified entry separated by a comma and a space?

     

    Was the maker.ini file saved as an ascii text file (i.e. what editor did you use)?

     

    It really doesn't matter whether you edit the main maker.ini in the Program Files area or the user specific one, just keep in mind that the user-specific version is read last and the settings there will override the Program Files maker.ini settings.

     
    |
    Mark as:
  • M_Boyd
    Currently Being Moderated
    27. M_Boyd,
    May 2, 2012 12:42 PM   in reply to Arnis Gubins
    Report

    Yes, I tried it with all 11 entries properly formatted.

    I used Notepad++, so yes, it's an ASCII file.

     
    |
    Mark as:
  • Mike Wickham
    Currently Being Moderated
    28. Mike Wickham,
    May 2, 2012 2:16 PM   in reply to Van Kurtz
    Report

    It is my understanding that one should not edit the maker.ini file

    that is in the Programs directory.

     

     

    Unless you want the changes to apply to all users.

     
    |
    Mark as:
  • Arnis Gubins
    Currently Being Moderated
    29. Arnis Gubins,
    May 2, 2012 10:02 PM   in reply to M_Boyd
    Report

    Melanie,

     

    I just re-read your original posting and when you say that editing the user-specific maker.ini has no effect, are you doing this for FM-to-FM or other-app-to-FM pastes? FM-to-FM pastes have always carrried along the formatting (even since FM3 ). You need to test this by copying formatted content from another app like Word or from a browser.

     

    If you want to paste unformatted FM text, then use the "ctrl+shift+v" (paste special) and then "t" (for text) and then "enter" as a shortcut.

     

    Not being able to edit the Program Files area maker.ini in place indicates a configuration issue on your machine that you need to resolve.

     
    |
    Mark as:
  • M_Boyd
    Currently Being Moderated
    30. M_Boyd,
    May 3, 2012 7:57 AM   in reply to Arnis Gubins
    Report

    Arnis, that's it! I was testing within FM. All this fuss because I was being lazy.... Geez!

     

    Yes, the problems with editing the master .ini file are probably environmental. But since I can edit my personal .ini, I'm not so worried about it.

     

    Thanks!

    Melanie

     
    |
    Mark as:
  • kmacdowe+brdcom
    Currently Being Moderated
    31. kmacdowe+brdcom,
    Jun 6, 2012 11:44 AM   in reply to Jeff_Coatsworth
    Report

    June, 6, 2012: - Jeff, sorry for the late response to what Op Sys and FM I am using. I was/am using Windows XP and FM10.

    Today I am able to edit the program-maker.ini file using Notepad (ASCI) without blowing up FM. I am not sure what changed.

    Now I cannot copy and paste tables within FM10. I willl start a new thread about that if I cannot solve it.

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points