Search

Search in sorted by
  • Re: ANNOUNCEMENT: End of support for Windows 7, Windows 8.1 & MacOS 10.11–10.13

    It is unfortunate that you have decided not to continue to support Win7 & Win8.1, because when I installed Win10 and updated to the their latest version, a lot of my programs stopped working, and I could no longer print to my printer, even though I tried reinstalling the drivers. So I installed a version of "Stop Updates" on my Win10 laptop to keep
    Posted to General by Bob Bacle on Thu, Sep 5 2019
  • Resource No Longer in Library

    My Logos is telling me that a resource is no longer in my library when I click on the Hebrew Alphabet Tutor on the main screen. Why is that?
    Posted to Logos 8 by Bob Bacle on Wed, May 1 2019
  • Why So Expensive?

    Just wondering why your software is so expensive. I've got other Bible software on my computer and they are not that expensive, and some are free. Even with your special, it is still very expensive.
    Posted to General by Bob Bacle on Wed, Aug 1 2018
  • Re: Logos & Noet Bible Software Has Stopped Working

    Nothing has worked thus far. I cannot believe that your program depends so much on .NET framework from MS. Why can't you have the program written where it does NOT depend on MS code? This has been a problem with your program for several years. I have experienced this problem since Logos 3, and other people are experiencing the same problem. It looks
    Posted to Logos 6 by Bob Bacle on Mon, Jul 18 2016
  • Re: Logos & Noet Bible Software Has Stopped Working

    Yes, I rebooted when I installed the Visual C++ 2013 redistributable. That didn't help.
    Posted to Logos 6 by Bob Bacle on Mon, Jul 18 2016
  • Re: Logos & Noet Bible Software Has Stopped Working

    Did that but still won't load. Getting this information when trying to open the program: Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: Logos.exe Problem Signature 02: 6.13.0.20 Problem Signature 03: 577bdbdc Problem Signature 04: mscorlib Problem Signature 05: 4.6.1076.0 Problem Signature 06: 56d79d90 Problem Signature 07: 10fb
    Posted to Logos 6 by Bob Bacle on Mon, Jul 18 2016
  • Re: Logos & Noet Bible Software Has Stopped Working

    800624.Logos Log Files.zip OK...here are the log files.
    Posted to Logos 6 by Bob Bacle on Mon, Jul 18 2016
  • Re: Logos & Noet Bible Software Has Stopped Working

    What do you mean by "see my signature line?" What is a signature line? And how do I send log files to you? I have them zipped up.
    Posted to Logos 6 by Bob Bacle on Mon, Jul 18 2016
  • Logos & Noet Bible Software Has Stopped Working

    I started having this problem today (July 18, 2016) with Logos 6. I had this problem before and finally someone at Logos pointed me a .NET Framework file that I needed to install to make it work. I tried that file today and did a repair, but still having the same problem - "Logos Bible Software Has Stopped Working," and "Noet Has Stopped Working." This
    Posted to Logos 6 by Bob Bacle on Mon, Jul 18 2016
  • Re: Cannot Start 6 "Logos Bible software has stopped working"

    I started having the same problem today (July 18, 2016) with Logos 6. I had this problem before and finally someone at Logos pointed me a .NET Framework file that I needed to install to make it work. I tried that file today and did a repair, but still having the same problem - "Logos Bible Software Has Stopped Working." This is very disconcerting that
    Posted to Logos 6 by Bob Bacle on Mon, Jul 18 2016
  • Re: Logos & Noet Won't Open

    ProcDump wants me to go to the system folder for the dump file, but I don't have a system folder in my Logos5 folder or the Logos folder. The instructions are also for Logos 4 and Logos 5, but I was trying Logos 6 again to see if it works. Again no system folder there for the dump file.
    Posted to Logos 6 by Bob Bacle on Fri, Mar 18 2016
  • Logos & Noet Won't Open

    I was finally able to get rid of 80004005 error by using the Net repair tool. But now I have another problem - Logos & Noet refuse to open upon installation. I am getting the window up that says: "Logos Bible Software has stopped working Check online for a solution and close the program Close the program" I am on Windows 7 64-bit with 8GB of RAM on
    Posted to Logos 6 by Bob Bacle on Fri, Mar 18 2016
  • Re: CLR 80004005 error

    Thank you, but where is the Log file? I can't find it anywhere - I have searched under my username in the documents folder and in the Logos folder in AppData/Logos and there is no log file there.
    Posted to Logos 6 by Bob Bacle on Thu, Mar 17 2016
  • Re: CLR 80004005 error

    OK...I ran the Net repair tool and now the CLR 80004005 error does not come up. But now I am getting something new - the program crashes upon launch and all it allows me to do is to close the program. Here is the error found in Event Viewer: Application: Logos.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled
    Posted to Logos 6 by Bob Bacle on Thu, Mar 17 2016
  • Re: CLR 80004005 error

    OK...I did as you said in the Event Viewer, but there were no errors there for the Logos program. All there was were 2 Net Runtime Version errors (both identical). So what do I do next? Is there a solution? Other people have been experiencing the same problem since Logos 5 with no solution as of yet. Are you going to give us a fix for this problem?
    Posted to Logos 6 by Bob Bacle on Wed, Mar 16 2016
  • Re: CLR 80004005 error

    If you can tell me how to give you the Event Viewer info, I would be glad to give it to you. As far as Win10 is concerned, I am on a multiboot machine with WinXP, Win7, & Win10 installed, so I already know about Windows 10 and I have it. When I installed the Logos software on Win10, I got several errors also, but it finally did install (sort of). I
    Posted to Logos 6 by Bob Bacle on Tue, Mar 15 2016
  • CLR 80004005 error

    I have been using Logos for a few years now, and I just had to reinstall my OS (Win 7) and when I attempted to install Logos 6, it gave me the 80004005 error upon trying to launch it, which means it would not even open. So I uninstalled it, tried Logos 5, and it gave me the same error. Then I went all the way back to Logos 4, and it installed fine and
    Posted to Logos 6 by Bob Bacle on Tue, Mar 15 2016
Page 1 of 1 (17 items) |