This update has 1 new Report and 7 improvements and 2 fixes. See the release notes to view these changes.New Feature, reads exported XMLs from Logos 5.3 Beta2! (read more in the above release notes and in the announcement in the Beta forum)Added report Catalog Summary which shows you interesting details on a Single Catalog.

For those who want to install this new Update, please go to the Download page on the website and follow the instructions.[users who already have LLR installed, please follow Step 1 carefully]

As I replied via email, my guess is that you don't have L5.3 Beta installed in your Mac VM, but have it installed only in the Mac. So LLR doesn't find the necessary info for L5.3 Beta in your VM for Mac. LLR was initially designed to run where L5 (or L4) was installed.

This is a unique case in which i did not anticipate (but i can see how it would be useful for Mac users). So i am working on allowing the XML feature in LLR to work even when L5.3 Beta is not installed. It will warn you tho when you have Read Logos Catalog DB selected and press the Read DB button (the warning will tell you that LLR could not find L5 running in your user account). But it will work when you select Read Exported XML File and press the Read XML button (when i get it fixed).

As i said, your case is unique. All those who run L5 in the same user account as LLR is installed should have no problem (this should include most users).

We got Jon's problem solved. This will be included on the next release of LLR.

It will allow those who use a Mac VM to install and run LLR. But you will need to save your XML files from your Mac install into a location where the VM and LLR can find them (edit: if you don't have L5.3 Beta installed in the VM, otherwise you could run L5.3 Beta in the VM and export your XMLs there.).

Edit: just found a bug in LLR's download webpage for Chrome users. I fixed this bug, when you go to LLR's webpage, tell your browser to Refresh and the download portion of the webpage should display properly. Sorry that i missed this.

i am working with Tes in Europe who's computer is setup for 24-hour display. This is causing some problems with LLR. LLR's code is building date/time strings and when those computers are set for 24-hour, they force LLR's code not to display AM/PM info for the time.

i am working on it and will post a fix for LLR when i get it resolved and fixed.

Fixed crashing for the Edit Catalog operation. This was due to LLR not handling computers which have 24-hour time as their standard.

Fixed crashing during the LastUpdated Change Report. This would effect European users who use the Date format with decimal points used as separators.

The first time that LLR is run after this install, it will adjust date/time to use the AM/PM in LLR operations. You will see this in the Saved Catalog DB listbox and the Backup listbox. Also when you click on any item in the Backup listbox, the new info file will be updated.

Please apply this update to your LLR install.

For those who want to install this new Update, please go to the Download page on the website and follow the instructions.[users who already have LLR installed, please pay attention to the ALERT]

P.S. Thanks Tes for allowing me to use your computer for hours while i tested these fixes!

P.S. (2) Users who had installed LLR ver 1.1.0.0 will not need to uninstall LLR prior to installing this update. You just need to close LLR and then reopen LLR, you should see a notice (see image below) asking if you want to install the newer version (click OK to allow LLR to be updated).

"I am working with Tes" Our dearest brother Steve is too generous to mention me as if Iassociated him in his diligent work in fixing the LLR which took him 61/2 hrs. The opportunity was he contacted me by teamviwer to help me as usual, he has done for years, which I am so grateful for his commitment to help for those of us who are less privileged in technical knowledge. While he was updating the LLR for me, he noticed that there was a bug in the program. I waited some hours watching him and went to bed. I slept well and he continued to fix it until he finally got the job done. He did it on my computer. I cannot even consider it as a slight contribution. It is not to mention at all comparable to his hard work. It is me that who has benefited from his wonderful work. May the Lord bless you my brother. I would like to thank you on behalf of all of us who are in Europe to fix it for us.