[ACK] Installation Issue: No warning when Setup Waits

I used the beta installer and it terminated my session of Logos and then disappeared. Nothing happened until I realised it was chewing up wait states and mass storage space until I terminated the other session of Logos 6. Not good - - and why does it have to wait anyway?

7776.SetupWaiting.zip

Also, I have three "System" folders (1x 6.3..., 2x 6.4...) - one of them was not removed

Find more posts tagged with

Comments

Bradley Grainger (Logos)

Are you running multiple copies of Logos in different user profiles?

Dave Hooton

https://community.logos.com/discussion/comment/732057#Comment_732057

Yes, standard beta practice!!

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/732297#Comment_732297

This is one of the known issues with that approach.

Dave Hooton

https://community.logos.com/discussion/comment/732474#Comment_732474

When can I expect a fix, though. There should be a warning message at least.

Steve Workman

https://community.logos.com/discussion/comment/732640#Comment_732640

I have created a ticket for us to look into this further.

Dave Hooton

https://community.logos.com/discussion/comment/735878#Comment_735878

Thanks, Steve

Bryan Albert

https://community.logos.com/discussion/comment/736012#Comment_736012

Dave,

There is an issue where the bootstrapper sees the Logos.exe instance (your stable build) running in the other Windows user account, and assumes it's the shutting-down beta instance. This is a really unusual situation. We have a case for it, though it's a low priority...

As a work around, you could shut down the stable version of Logos, or log out that Windows user, before running LogosSetup.exe to update your beta version. Or, you could let the beta version update itself automatically. Since that happens in the background, it doesn't try to shut down Logos.

Bryan

Dave Hooton

https://community.logos.com/discussion/comment/736468#Comment_736468

As a work around, you could shut down the stable version of Logos, or log out that Windows user, before running LogosSetup.exe to update your beta version. Or, you could let the beta version update itself automatically.

There are times when the beta installer is preferred e.g. when I don't want the resource updates!

Bryan Albert

https://community.logos.com/discussion/comment/736630#Comment_736630

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

Dave Hooton

https://community.logos.com/discussion/comment/753971#Comment_753971

Will do.

Angela Murashov

https://community.logos.com/discussion/comment/753971#Comment_753971

When you get your first 6.6 update, let me know if it works.

This should be fixed in 6.6 Beta 1. Please let us know if it is not fixed. Thank you! [:)]

Dave Hooton

https://community.logos.com/discussion/comment/757241#Comment_757241

Will do!

Dave Hooton

https://community.logos.com/discussion/comment/757276#Comment_757276

The beta installer for 6.6 B1 did not wait for the other instance of Logos to close! Thank you.