[ACK] Smart Tags broken in 6.3 SR1

Page 9 of 10 (191 items) « First ... < Previous 6 7 8 9 10 Next >
This post has 190 Replies | 16 Followers

Posts 24698
Forum MVP
Dave Hooton | Forum Activity | Replied: Sat, Nov 14 2015 12:27 AM

Bryan Albert:
I've updated the Windows PowerShell script to register Logos COM and Logos Smart Tags for Logos 6.7 and newer.

Thanks Bryan

I also updated the wiki for Smart Tag and 64-bit Logos to reflect use of the updated PowerShell script

Dave
===

Windows & Android

Posts 76
Paul Grieve | Forum Activity | Replied: Sat, Nov 14 2015 10:54 AM

I've tried the 64-bit option using the PowerShell but I got the error message: "Failed to find System folder at: C:\Users...\Logos4\6.7.0.0036. I checked the folder and find a sub-folder 6.6.0.0069, so I assume this is the problem. 

How can I correct this? Be glad of help.

Paul.

Posts 24698
Forum MVP
Dave Hooton | Forum Activity | Replied: Sat, Nov 14 2015 12:18 PM

Paul Grieve:
I've tried the 64-bit option using the PowerShell but I got the error message: "Failed to find System folder at: C:\Users...\Logos4\6.7.0.0036.

You're using the wrong version of the script. Download it from http://downloads.logoscdn.com/LBS6/Support/RegisterSmartTags.ps1

Dave
===

Windows & Android

Posts 76
Paul Grieve | Forum Activity | Replied: Sun, Nov 15 2015 8:01 AM

Thanks, Dave, for the help. I downloaded the version for which you gave the link and it seemed to load correctly with no error message. However, when I tried to use the Smart Tag,  I got the message "You're using the wrong version of the script"!

Seems like I'm stymied again!

Appreciate your input.

Paul

Posts 24698
Forum MVP
Dave Hooton | Forum Activity | Replied: Sun, Nov 15 2015 11:04 AM

Paul Grieve:
However, when I tried to use the Smart Tag,  I got the message "You're using the wrong version of the script"!

Please explain "tried to use" (the message is a repeat of what I said in my previous post!). Were you following instructions at https://community.logos.com/forums/p/105737/780081.aspx#780081 ?

Dave
===

Windows & Android

Posts 76
Paul Grieve | Forum Activity | Replied: Sun, Nov 15 2015 11:37 AM

I used the instructions given by Bryan Albert: I right-clicked the downloaded file and chose 'Run with PowerShell'. It seemed to execute correctly—at least there was no failure notice. When I said I tried to use the Smart Tag, I mean that in Word I typed in a verse reference and right-clicked it. As soon as I tried to choose a paste option, I got the "You're using the wrong version of the script" notification.

Paul.

Posts 24698
Forum MVP
Dave Hooton | Forum Activity | Replied: Sun, Nov 15 2015 4:04 PM

Paul Grieve:
I used the instructions given by Bryan Albert

OK?? Let's check what you are using:-

  • Logos 6.7?
  • Operating System and whether it is 32-bit or 64-bit (check Control Panel >> System)
  • Which version of Word  e.g. 2013?
  • Is it 32-bit Word (Task Manager will state that it is 32 bit, else it is 64 bit)?

Dave
===

Windows & Android

Posts 76
Paul Grieve | Forum Activity | Replied: Sun, Nov 15 2015 11:34 PM

Dave Hooton:

OK?? Let's check what you are using:-

  • Logos 6.7?
  • Operating System and whether it is 32-bit or 64-bit (check Control Panel >> System)
  • Which version of Word  e.g. 2013?
  • Is it 32-bit Word (Task Manager will state that it is 32 bit, else it is 64 bit)?

I'm using Logos 6.7 as shown here:

  

Operating System is 64-bit as shown here:

Word 2013—Task Manager does not state that it is 32-bit as shown here:

Hope this will somehow reveal my problem! Thanks, Dave.

Posts 76
Paul Grieve | Forum Activity | Replied: Mon, Nov 16 2015 12:30 AM

Since writing the above, I have tried again to use the Smart Tags but now, when I right-click a verse reference in Word, there is no paste option available—it's grayed out.

I also noted that Word was working in Compatibility Mode, but turning this off made no difference.

Posts 24698
Forum MVP
Dave Hooton | Forum Activity | Replied: Mon, Nov 16 2015 5:36 AM

Paul Grieve:
Word 2013—Task Manager does not state that it is 32-bit as shown here:

It is shown on the Processes tab

Dave
===

Windows & Android

Posts 146
Joe Mayden | Forum Activity | Replied: Mon, Nov 16 2015 5:41 AM

Dave, it worked and then it quick working.  When I attempt to run Smart Tag and 64-bit Logos with PowerShell script, the black dos screen flashes open quickly I see red letters and it closes before I can read it.  

Like I said it work at one time.  Any thoughts?

Thanks 

Posts 76
Paul Grieve | Forum Activity | Replied: Mon, Nov 16 2015 5:50 AM

Thanks, Dave. It is 32 bit:

Is this the problem? What should I do about it? 

Posts 24698
Forum MVP
Dave Hooton | Forum Activity | Replied: Mon, Nov 16 2015 11:58 AM

Paul Grieve:
Thanks, Dave. It is 32 bit:

The script should work, then. Rather than right click to run it, open a Powershell window and run it as described by Bryan.

Dave
===

Windows & Android

Posts 24698
Forum MVP
Dave Hooton | Forum Activity | Replied: Mon, Nov 16 2015 12:00 PM

Joe Mayden:
When I attempt to run Smart Tag and 64-bit Logos with PowerShell script, the black dos screen flashes open quickly I see red letters and it closes before I can read it.

Run it from a Powershell window as described by Bryan

Dave
===

Windows & Android

Posts 146
Joe Mayden | Forum Activity | Replied: Mon, Nov 16 2015 1:50 PM

Dave I have been running it from the powershell window but it takes it to a black dos screen quickly and disappears.  Could I have messed something up with the RegEdit?

I did what the Forum suggest.

Posts 24698
Forum MVP
Dave Hooton | Forum Activity | Replied: Mon, Nov 16 2015 4:28 PM

Joe Mayden:

Dave I have been running it from the powershell window but it takes it to a black dos screen quickly and disappears.  Could I have messed something up with the RegEdit?

I did what the Forum suggest.

Show me a screen shot of your input before pressing <Enter>

Dave
===

Windows & Android

Posts 76
Paul Grieve | Forum Activity | Replied: Mon, Nov 16 2015 11:41 PM

Thank you, Dave, for your time and expertise. I have tried running the script from the PowerShell window with no joy. I think I'll abandon the whole thing and not waste any more of my time or yours. I'll just use cut and paste!

I appreciate your patience with folks like me who just don't know what they're doing!

Paul.

Posts 146
Joe Mayden | Forum Activity | Replied: Tue, Nov 17 2015 3:27 AM

Posts 149
Timothy Brown | Forum Activity | Replied: Tue, Nov 17 2015 6:40 AM

Paul Grieve:

Thank you, Dave, for your time and expertise. I have tried running the script from the PowerShell window with no joy. I think I'll abandon the whole thing and not waste any more of my time or yours. I'll just use cut and paste!

I appreciate your patience with folks like me who just don't know what they're doing!

Paul.

You don't have to use PowerShell. You can also do it manually, following these instructions from the wiki:

Logos 6 is 64-bit so you will experience problems if you recently upgraded from Logos 4 or Logos 5, but you may also experience problems after updating Logos 6 e.g. from v6.6 to v6.7.
Most users should use the PowerShell script below but if you are confident to do it manually start by running these commands in a Command Prompt:

    1. “%LOCALAPPDATA%\Logos\Logos.exe” /register
    2. regsvr32 “%LOCALAPPDATA%\Logos\System\L4SmrtTg.dll” (see below for 64-bit Office)

Note 1 the \Logos\ folder could be \Logos4\, \Logos5\ or \Verbum\ for your installation.
Note 2 the \System\ folder for v6.3 to v6.6 is replaced with a folder like \6.6.0.0069\. If more than one use the latest.

To open a Command Prompt, press the Windows key, type Command Prompt, and click on that. Then run the commands in steps 1 and 2, taking note of Note 1.

Windows 8.1 64-bit, Core i5-3330, 8GB RAM

Posts 42
LogosEmployee
Bryan Albert | Forum Activity | Replied: Tue, Nov 17 2015 9:56 AM

Joe,

Sorry you're having trouble, computers can be pretty finicky when it comes to running a script. Basically, the red error message is saying that PowerShell doesn't know what the term RegisterSmartTags.ps1 is (it doesn't recognize it as the name of a script name, which is what it is.) There are two possible reasons for this. First of all, you have to have a period and a backslash before the name of the script: .\RegisterSmartTags.ps1. Second, the script has to exist in the folder PowerShell is working in. In your screenshot, your PowerShell is in the the folder C:\Users\Joe, (as displayed on the prompt, PS C:\Users\Joe>. If you downloaded the script from the link in the instructions, your web browser probably downloaded the script to the folder C:\Users\Joe\downloads. So first you need to change to that folder, with the cd command (for change directory): cd downloads.

One trick you can use to make sure that PowerShell likes what you type is to use the Tab key to complete the command you're typing. For example, you could type register <Tab> and if you're in the right directory and the script is there, PowerShell will fill it out for you: .\RegisterSmartTags.ps1, adding the dot and backslash, then you just hit <Enter> and it will finally run the script. 

Hope that helps!

Bryan

Page 9 of 10 (191 items) « First ... < Previous 6 7 8 9 10 Next > | RSS