Search

Search in sorted by
  • Re: Smart Tags broken in 6.3 SR1

    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
    Posted to Logos 6 by Bryan Albert on Tue, Nov 17 2015
  • Re: 6.8 B1: Smart Tags not registered (Windows)

    Thank you!
    Posted to Logos Desktop Beta by Bryan Albert on Mon, Nov 16 2015
  • Re: Smart Tags for Logos version 6.7

    [quote user="Bradley Grainger (Faithlife)"] There should be an updated LSmtTg64.dll file in your "Logos\System" folder. If it's not there, there may be a problem with the installer; we'll investigate. [/quote] 6.8 Beta 1 should install the LSmtTg64.dll file for 64-bit Office. Also, please see the update PowerShell script RegisterSmartTags.ps1 discussed
    Posted to Logos 6 by Bryan Albert on Fri, Nov 13 2015
  • Re: System folder and Smart Tags in v6.7

    Concerning Smart Tags on Windows, please try the updated PowerShell script RegisterSmartTags.ps1 discussed at https://community.logos.com/forums/p/105737/780081.aspx#780081. Thanks, Bryan
    Posted to Logos Desktop Beta by Bryan Albert on Fri, Nov 13 2015
  • Re: Logos 6.7 (6.7.0.0036) now available

    [quote user="Dave Hooton"] [quote user="Dylan Rondeau"]This release features:[/quote] No comment about Smart Tags, yet it has changed and people are having problems!! [/quote] Concerning Smart Tags on Windows, please try the updated PowerShell script RegisterSmartTags.ps1 discussed at https://community.logos.com/forums/p/105737/780081.aspx#780081. Thanks
    Posted to Logos 6 by Bryan Albert on Fri, Nov 13 2015
  • Re: 6.8 B1: Smart Tags not registered (Windows)

    In the meantime, please try the updated RegisterSmartTags.ps1 PowerShell script as discussed at https://community.logos.com/forums/p/105737/780081.aspx#780081
    Posted to Logos Desktop Beta by Bryan Albert on Fri, Nov 13 2015
  • Re: 6.8 B1: Smart Tags not registered (Windows)

    This should be fixed with a coming release.
    Posted to Logos Desktop Beta by Bryan Albert on Fri, Nov 13 2015
  • Re: Smart Tags broken in 6.3 SR1

    I've updated the Windows PowerShell script to register Logos COM and Logos Smart Tags for Logos 6.7 and newer. It's works with Logos installed to the System folder, has enhanced messages and a few fixes. There's a new feature for registering the LSmtTg64.dll for 64-bit Office, too. Enabling PowerShell script execution On most Windows versions, PowerShell
    Posted to Logos 6 by Bryan Albert on Fri, Nov 13 2015
  • Re: Smart Tags broken in 6.3 SR1

    [quote user="John Stasse"] Previously I found Bryan Adam's 'PowerShell script' to work for each new update, but now that L4SmrTg.dll has been moved back into the Logos4\System folder it won't work as it looks for the .dll as previously as a separate folder for the update number under Logos4. I don;t suppose that 'PowerShell script' can be reworked to
    Posted to Logos 6 by Bryan Albert on Wed, Nov 4 2015
  • Re: 115.2 mb perpetual update problem

    [quote user="Mark"] Another Logos Bible Software setup is already in progress. Please wait for it to finish. [/quote] That message is displayed when Logos Setup detects that another instance of itself is already running. Under certain circumstances, the setup can run longer than expected and we found that users were occasionally launching Logos Setup
    Posted to General by Bryan Albert on Mon, Sep 28 2015
  • Re: Update failing

    [quote user="Dr. Victor Anderson"] Files are attached. Thanks for debugging for me! [/quote] Thanks for the log files, it looks like your machine is having the same problem that the upgrade-to-Windows-10 machines are having, unfortunately. In any case, if you could try this procedure and tell me if it works: In Windows Explorer, navigate to the C:\Users
    Posted to Logos 6 by Bryan Albert on Wed, Sep 9 2015
  • Re: Update failing

    [quote user="Dr. Victor Anderson"]I'm a LONG time Logos user, running Win7 Pro in a school environment (DTS). I have all the same symptoms of failed installation of that 115 mb update. (Download is successful.)[/quote] At this point, I would only expect this problem on a machine that had Windows recently upgraded to Windows 10, so I wonder if you are
    Posted to Logos 6 by Bryan Albert on Fri, Sep 4 2015
  • Re: Update failing

    [quote user="Nord Zootman"] That worked! Unfortunately I must not have logging set to run unless I start it with the ctrl key so it did not generate new logs. If it helps I can restart and send you those. it did generate a cef.log which I never noticed before. I am attaching that. [/quote] Great! I have a better idea of what's going on here, thanks
    Posted to Logos 6 by Bryan Albert on Tue, Sep 1 2015
  • Re: Update failing

    [quote user="Nord Zootman"] This computer was updated to windows 10 last week. Does that have any bearing on what is happening? [/quote] Thanks for the logs, I found another clue. It most likely does have something to do with the upgrade, though I'm not yet sure just what. Here's one more thing you can try, having to do with the file C:\Users\Lockport
    Posted to Logos 6 by Bryan Albert on Mon, Aug 31 2015
  • Re: Update failing

    [quote user="Nord Zootman"] What should I try next? [/quote] Nord, As an experiment, could you please delete the en-US, es-MX, and es-ES folders from your C:\Users\Lockport\AppData\Local\Logos4 folder, then launch Logos again to see if it's update will work? If it works or not, I'd love to see the DigitalLibraryInstall.log file that Windows Installer
    Posted to Logos 6 by Bryan Albert on Mon, Aug 31 2015
  • Re: Update failing

    Could you please upload the newly-created DigitalLibraryInstall.log file? Thanks! Bryan
    Posted to Logos 6 by Bryan Albert on Mon, Aug 31 2015
  • Re: Update failing

    Nord, Does your machine's C:\Users\Lockport\AppData\Local\Logos4 folder have a folder named System? You may need to copy and paste that path into the Address Bar of Windows Explorer, depending on your Windows Explorer settings. If so, with Logos not running, see if you can delete that folder. If you can, see if Logos can then update when you launch
    Posted to Logos 6 by Bryan Albert on Fri, Aug 28 2015
  • Re: Update failing

    On a Windows machine, Logos launches LogosSetup.exe in the background, which then launches Microsoft's Windows Installer to install the Logos application update. Windows Installer is returning the 1603 error code, which means, " A fatal error occurred during installation." Windows Installer logs its activities to a log file, which should be found in
    Posted to Logos 6 by Bryan Albert on Fri, Aug 28 2015
  • Re: Installation Issue: No warning when Setup Waits

    Dave, I did some work on the bootstrapper and while I was in there, I think I fixed this behavior. If LogosSetup.exe finds Logos.exe running under a different user account, it should just skip it instead of waiting indefinitely for it to close. When you get your first 6.6 update, let me know if it works. Bryan
    Posted to Logos Desktop Beta by Bryan Albert on Wed, Aug 5 2015
  • Re: Logos 6 questions

    Sarah, Thanks for the report, I'll make a case for the accessibility setting. The setting is saved on my machine, so there must be something more subtle going on. Bryan
    Posted to Logos 6 by Bryan Albert on Fri, Jun 26 2015
Page 1 of 3 (42 items) 1 2 3 Next > |