Skip to main content
SchweineKarl
Inspiring
November 28, 2015
Question

Has anybody seen this? Doers anybody know what it does?

  • November 28, 2015
  • 2 replies
  • 911 views

Hello everybody,

When I start FM 2015 (part of TCS 2015), I get a dialog box saying:

Adding information can unintentionally change or delete values and cause components to stop working correctly. If you do not trust the source of this information in

C:\Users\Carel\AppData\Local\Temp\frmreg.reg, do not add it to the registry.

Are you sure you want to continue?

 

Can anybody tell me what this registry entry is for?

Thank you in advance for any feedback.

Regards,

Carl

    This topic has been closed for replies.

    2 replies

    Participating Frequently
    December 1, 2015

    The FrameMaker application has a top-level file named fmreg.txt. This contains registry settings used to setup the application, with a placeholder for the actual install directory. FrameMaker checks for these registry settings at startup, and applies them if missing - including immediately post-install. To do so, creates a temporary file, replacing the placeholder for the install directory with the actual value.

    The file you are seeing is almost certainly this temporary file. Compare it with the fmreg.txt file to verify.

    SchweineKarl
    Inspiring
    December 1, 2015

    Hello Mike,

    Since I posted my question, I managed to check the contents of the file and it consists of a whole series of registry settings,

    so you're right on the mark.

    Thank you for your feedback.

    Regards,

    Carl.

    -


    Origineel Bericht----

    Van : forums_noreply@adobe.com

    Datum : 01/12/2015 14:30

    Aan : scansite@planet.nl

    Onderwerp : Has anybody seen this? Doers anybody know what it does?

    Has anybody seen this? Doers anybody know what it does?

    created by Mike-Hardy in FrameMaker - View the full discussion

    The FrameMaker application has a top-level file named fmreg.txt. This contains registry settings used to setup the application, with a placeholder for the actual install directory. FrameMaker checks for these registry settings at startup, and applies them if missing - including immediately post-install. To do so, creates a temporary file, replacing the placeholder for the install directory with the actual value.

    The file you are seeing is almost certainly this temporary file. Compare it with the fmreg.txt file to verify.

    If the reply above answers your question, please take a moment to mark this answer as correct by visiting: https://forums.adobe.com/message/8234478#8234478 and clicking ‘Correct’ below the answer

    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:

    Please note that the Adobe Forums do not accept email attachments. If you want to embed an image in your message please visit the thread in the forum and click the camera icon: https://forums.adobe.com/message/8234478#8234478

    To unsubscribe from this thread, please visit the message page at , click "Following" at the top right, & "Stop Following"

    Start a new discussion in FrameMaker by email or at Adobe Community

    For more information about maintaining your forum email notifications please go to https://forums.adobe.com/thread/1516624.

    Bob_Niland
    Community Expert
    Community Expert
    November 29, 2015

    What Windows operating system are you running FM13 on, and is the OS native or virtualized, and 32- or 64-bit?

    Searching the greater web on "frmreg.reg" (with quotes) gets some hits, some related to WINE, and one suggesting a corrupt FM install.

    SchweineKarl
    Inspiring
    November 29, 2015

    Hi Bob,

    I'm running Frame on Windows 7 Ultimate 64-bit locally on a PC, so not

    virtualized.

    I also did a search and this is what I found (see attachment).

    Thx for your input.

    Regards,

    Carl.

    Bob_Niland
    Community Expert
    Community Expert
    November 29, 2015

    re: see attachment

    No attachment visible to me.