This is really frustrating, after update software will not WORK !

Ok, I am just about ready to toss in the towel with this software. Yesterday I had problems with the software not working with layouts. No response from tech support to speak of. I could of tried to submit logs today, but now I cannot even run the software at all

The latest update comes down and guess what, the software installer asks for my password and then promptly gives me a message "installing error" and then quits.

I tried this several times.

The bottom line, my software is totally non functional and will not run , I've had nothing but problems since I purchased this.

I had several other problems which I did not post regarding the software ending while in reading mode.

What the heck is up with all this?

I simply cannot afford this instability.

How can an update like this be released. Where is the quality control? How many beta testers were involved, what was tested ect. Did you get any feedback from testers before release changes into the software.

It is my opinion at this point that best practices are not being followed for software release.

Those changes should not be released in dribs/drabs on a ad hoc schedule, fixes should be bundled, and tested with a beta cycle much like Apple does for OS/X

The quality and methods for implementing change are out of control in my mind.

I've shink wrapped complex software with rigourous change control in place as a professional so I know what I am speaking of

Find more posts tagged with

Comments

Mr. Simple

I've decided that since I have no layout customization left, it broke yesterday, and now the system just keeps looping on the install process with no way to stop it I am just going to delete all evidence of logos 4 on my laptop and start afresh. I will get up and running faster than tech support can fix it.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/233344#Comment_233344

I've decided that since I have no layout customization left, it broke yesterday, and now the system just keeps looping on the install process with no way to stop it I am just going to delete all evidence of logos 4 on my laptop and start afresh. I will get up and running faster than tech support can fix it.

Apologies (plus understand frustration). Wiki has Uninstalling and Reinstalling in Logos 4 Mac with Reset Logos 4 User Files - if have disk space, can avoid resource download time.

The latest update comes down and guess what, the software installer asks for my password and then promptly gives me a message "installing error" and then quits.

Option: delete Logos application (move to trash), restart Mac, Download current stable release of Logos 4 Mac, copy Logos Bible Software 4 to Applications folder, then launch Logos 4 Mac (may need force quit, see forum http://community.logos.com/forums/t/31392.aspx, followed by another launch).

Keep Smiling [:)]

Mr. Simple

https://community.logos.com/discussion/comment/233353#Comment_233353

Ok -

I want to make a recommendation. Obtaining a crash log on Mac OS X is incredibly easy since it automatically creates easily accessible crash logs for you. When you experience a problem, it's two clicks and it's all send off formatted. I've also been able to send os/x profile information ad hoc when working with tech support. Here are two screen shots to illustrate how easy it is for the user. Note the fact that the user has a box to enter text to describe the problem as well.

Logos 4 should implement and automate along similar lines. Would save everyone a headache.

Real Slick -

Mr. Simple

https://community.logos.com/discussion/comment/233356#Comment_233356

Before you responded to this, I had re-installed the application. So far I've worked around the issue.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/233356#Comment_233356

I want to make a recommendation. Obtaining a crash log on Mac OS X is incredibly easy since it automatically creates easily accessible crash logs for you. When you experience a problem, it's two clicks and it's all send off formatted. I've also been able to send os/x profile information ad hoc when working with tech support. Here are two screen shots to illustrate how easy it is for the user. Note the fact that the user has a box to enter text to describe the problem as well.

Concur Apple crash reports are easy to click and send; unfortunately crash report does not include Logos4.log and Indexer.log files that can be quite helpful for Logos developers to replicate issue and fix crash. Some forum discussions have crash information in posted Logos4.log and Indexer.log files that include Apple's crash report path, Logos developers have requested copies of those crash reports.

Also, some Logos 4 Mac crashes do not generate an Apple Crash Report, but usually have information in Logos4.log and Indexer.log files.

Forum Logos Log Scribe has an easy to use application for compressing Logos 4 log files for forum posting (places file to post on your desktop). Forum link copied from How to Report Bugs in Logos 4 Mac section.

Keep Smiling [:)]

Mr. Simple

https://community.logos.com/discussion/comment/233370#Comment_233370

Thanks for the reply - I do understand that the apple crash report does not include what you need. What i am saying is automate it for the user using some tool. Automator, Applescript, whatever works. If the user can generate then software should be able to automate it.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/233376#Comment_233376

Thanks for the reply - I do understand that the apple crash report does not include what you need. What i am saying is automate it for the user using some tool. Automator, Applescript, whatever works. If the user can generate then software should be able to automate it.

As a Logos user, currently Logos Log Scribe (written by another Logos user) is easy log file scripting solution for forum posting.

Pondered an idea for Logos: wonder about adding to code that writes Logos4_Crash.txt to compress log files and crash txt after Logos4_Crash.txt file closure.

Having read many Logos4.log and Indexer.log files,know Logos4_Crash.txt file not always generated; depends on user to report issue(s) to tech support or forum (post/reply). Likewise screen shot(s) for some issues are adequate for reporting (e.g. screen partially blank or Hebrew vowel point displacement).

Keep Smiling [:)]

Keep Smiling 4 Jesus :)

How can an update like this be released. Where is the quality control? How many beta testers were involved, what was tested ect. Did you get any feedback from testers before release changes into the software.

Currently service releases are not publicly beta tested before stable release since service releases are fixing bugs, but not adding new functionality. When a public beta cycle is in progress, cannot be used to test stable service release fixes.

Hindsight observation for Logos: 4.2a service release "candidates" could have been released to Beta channel for public testing for a day or two before Stable channel since a Beta test cycle is not in progress.

Keep Smiling [:)]