NidaMAP — Modular Aggregation of Principles for Bible Translation
EnglishGeneral

Scrolling Logos with Paratext - Registration difficulties

SPStephen Pattemore · Sep 22, 2016, 12:58 PM · Last modified: Sep 28, 2026, 11:38 AM
♡ 0

Over many installations of both Paratext and Logos I have had intermittent difficulties getting them to interact as they should - both scrolling and accessing Logos resources through SLT. I recently found this fix on a PT site somewhere - thank you to whoever wrote it - the arcane rituals described here seem to do the trick!


Extracted text from ScrollingwithLogos.docx:

Synchronized Scrolling between Paratext and Logos

Normal Operations Synchronized scrolling between Paratext and Logos requires specific actions within each of the two applications. Here you will see how to setup each application properly, starting with Paratext.

Paratext setup The first step is to open a Scripture resource or project within Paratext. Then from the Tools menu make sure that the Scroll Scripture with any compatible applications is ticked.

Be sure to take notice of which scroll group the Scripture text is associated with. In the screen shot below, the text is a part of Group A.

Logos setup Start up Logos and open a Bible. In the upper left of the text window there is a pull down menu. In the screenshot below, the pull down menu is accessed through the large yellow icon used to identify the NLT Bible.

Near the top of the menu is an item called Link set: This is how you associate a Bible text with a link set. In this case the NLT is associated with Link set A. The link sets in Logos and the scroll groups in Paratext are both named A through F and there is a direct correlation between them.

Once the scroll groups and link sets are assigned, and scrolling is enabled in Paratext, your Scripture texts should scroll together.

Troubleshooting If this does not work for you here are some things to consider. Paratext 7.6 Beta 2 bug We have a known problem with synchronized scrolling in Paratext 7.6 Beta 2. This bug will be fixed in Beta 3. If you are currently running Beta 2, synched scrolling will not work.

Paratext 7.6 Beta 3 changes The processes described below for registering the Logos COM API have been included in the most recent Paratext code base. With these changes, when Paratext attempts to access a Logos object and fails, it then attempts to register the Logos COM API and retry the operation. The Logos 6 registration process was included into the Paratext 7.6 Beta 3 codebase on June 15, 2015. If you dont yet have access to the most recent Paratext code, you can register the COM API manually.

Manual Logos COM API Registration for Logos5 Logos ships with a COM API that needs to be registered with Windows. Some versions of Logos do not register the COM object automatically when installed. There is a way to manually register the Logos COM object. Heres how:

Open a Command Prompt as Administrator. From the Windows Start Menu click All Programs-

Accessories->Command Prompt->(right click)->Run as administrator.

In the command prompt window type cd C:\Users. Then change to your user directory cd [Username]. Then cd AppData\Local\Logos5.

In the Logos5 directory run this command logos.exe /register. You should see a message from Logos indicating that it was successfully registered.

Manual Logos COM API Registration for Logos6 Run PowerShell as Administrator (Windows key, type PowerShell, right-click on Windows PowerShell in the list and choose Run as administrator, click Yes on the User Account Control dialog). In the PowerShell window, type Set-ExecutionPolicy RemoteSigned . Hit Y to make the change. Close PowerShell.

  1. Download the RegisterSmartTags.ps1 script from http://downloads.logoscdn.com/LBS6/Support/RegisterSmartTags.ps12
  2. In Windows Explorer, find the script, right-click and choose Run with PowerShell. Since the script is signed by Logos Bible Software, choose Open from the Open File - Security Warning dialog, if displayed.
  3. The script calls RegSvr32.exe to register the Logos Smart Tags dll, 4. L4SmrtTg.dll, which should display a RegSvr32 dialog message similar to,
  4. "DllRegisterServer in C:\Users\Bryan\AppData\Local\Logos\6.3.0.0074\L4SmrtTg.dll succeeded.", click OK.
  5. The PowerShell window should list details about registering, ending with the message "Finished
  6. successfully. Hit a key to exit..." Logos COM and Logos Smart Tags for 32 bit Office should now be registered.

Attachments

1 comment

Sign in to join the conversation.

DSDaud SoesiloSep 26, 2016, 4:51 AM

Brilliant, Stephen! It's great that you finally found the fix for your intermittent problems. Most of us have no problems, but there will be a few who encounter a similar challenge like yours. I suppose you had to register the COM API manually. It will be nice when you can link ParaTExt 8 to Logos 7.

♡ 0