-
That's exactly what I'm seeing, Rob.
-
@Daniel, My Logos has successfully updated from 8.14.0.0010 to 8.15.0.0004 with 5.11 wine-staging although it did have a couple of hiccups, e.g. re-downloading 3.5Gb of resources, and I think it had two attempts at downloading. So far, after light use, I've not noted any particular additional issues, but these may emerge as I use it more. The process
-
Yes, it was all the way from 8.10.0032 to 8.14.0.0010 using wine-staging 5.11
-
My wine-staging 5.11 is now successfully indexing and updating Logos via a command line install on debian bullseye 64 bit and win10 and dotnet48. Updating Logos wasn't working for me up to 5.9 staging (approx) but is now (I think there was a general problem with 5.10 staging). Indexing in win10 is successful. I haven't tested 5.12. Happy to provide
-
John, Yes it is!
-
Hi, Frank. I'm interested in this, because I'm getting problems. I'm using Debian Bullseye with wine-staging at 5-rc3, 64 bit. When I try to install in win7, it automatically goes to indexing and crashes. When I tried to reset the directories as per your instructions of Christmas Day, it complained that I needed to update Logos to the latest version
-
Sorry, Frank, I spoke too soon. It seems that while Logos.exe is not reporting indexing taking place, nevertheless it indexes in the background when I run Logos, and continues when I close it. I can see the LogosIndexer.exe process gradually consuming more and more memory until eventually the amount of memory seems to start dropping. However, the process
-
Frank, are you running under winxp or win7? I've just had success with indexing following the "install under win7 then index and run under winxp" mantra - albeit with Debian Bullseye, wine-staging 4.21. Had the same / a similar problem as you under win7.
-
Bill[quote user="Bill Anderson"] But, the Debian container runs slower than the Ubuntu container, so it's back to that one for me. [/quote] I don't believe my "how to" involves a container. I've not yet got to grips with the indexing. That lengthy process might be slowing it down. There's also a possible question over the whether the "path:parse_url
-
Bill, yes, you have to download the .msi file from the Logos website. And then replace the bit of the path in bold above to that link. I'll update my "how to" to make it clearer. Many Thanks Nick
-
Bill, stupid question, in the first instance, but you did make the bold path local to your own system (sorry if my notes were confusing): WINEPREFIX=$HOME/wine-logos8/ msiexec /i /path/to/Logos/Installer /Logos-x64.msi All the best. Nick
-
Thanks. Instructions updated!
-
Just a quick question: Did you need to install wasta-logos-setup? If so, why? I DIDN'T do so under debian in the instructions above, and results that are not at all bad . . . My suspicion (which may be wrong) is that you might have a problem with an incorrect libjpeg using wasta-* (I did, but other things have changed in my system since then)
-
This is my Debian "how to". It's not thoroughly tested yet. I've not had a chance to explore what works and doesn't. What follows may need filling out, so feel free to ask any questions. Many thanks for everyone's hard work. ====================================== /etc/apt/sources.list: deb [arch=amd64,i386] http://ftp.uk.debian.org/debian/ buster main