I made a personal book from our denominational doctrinal statement on my laptop and used it several times. Now, as I go to the desktop and try to open it, it is not in my library. If I go to utilities and go to the PBB, I see it there and can click "open." If I do, Logos gives me an error saying I do not have a license to use my own personal book.It gives me an ID which starts PBB:9f7d363...
I can rebuild the book when I have my laptop again, but I am worried there is some deeper problem. Other PBs work fine.
Personal books didn't sync anything but the metadata until recently, and you must manually sync the compiled books now. Trying to open an uncompiled or unsynced book will give you that warning.
If you think something else is at play, please provide more info such as your software version. (This thread might then be moved to the appropriate forum for L5 or L6)
OSX & iOS | Logs | Install
Every personal book I build on one computer has to be rebuilt on the other computer to be read. I have to keep a flashdrive of my PB files to build every time I change computers.Is that normal or am I missing something?
John C. Livesay: Every personal book I build on one computer has to be rebuilt on the other computer to be read. I have to keep a flashdrive of my PB files to build every time I change computers.Is that normal or am I missing something?
Again, the metadata (author, title, etc.) has ALWAYS synced. The compiled book itself did not. With the release of L6, there is now a method to sync the compiled book. When you have finished compiling a book, you press the "upload" button.
So what I get from this is... if I build a book on computer A, I only have the "license" on that computer. If I then build it on computer B, the license changes to that computer, correct? I would think that if I built it on multiple computers, that I should be able to see it on each one, and only have to rebuild it if I make changes. Too bad I don't have L6.
John C. Livesay:If I then build it on computer B, the license changes to that computer, correct? I would think that if I built it on multiple computers, that I should be able to see it on each one, and only have to rebuild it if I make changes.
The "license" warning is probably a misnomer. All it really means is "Hey, this book ain't available on this computer!" I think you can compile it on both computers and use it on both computers as long as you don't make any changes...
John C. Livesay:Too bad I don't have L6.
As long as your computer specs are appropriate to run it, the L6 engine is free.
https://www.logos.com/product/47040/verbum-6-core-engine
John C. Livesay: So what I get from this is... if I build a book on computer A, I only have the "license" on that computer. If I then build it on computer B, the license changes to that computer, correct? I would think that if I built it on multiple computers, that I should be able to see it on each one, and only have to rebuild it if I make changes. Too bad I don't have L6.
John, once you build it on more than one computer you should be able to read it on each one. It is not just one at a time. I would recommend Logos 6, you can install the basic engine for free.
Edit: Alabama types faster than this old man!
Nope. every time I build it on a computer, the next one tells me no "license." Thanks for the info, I will try the free L6 engine.
John C. Livesay: Nope. every time I build it on a computer, the next one tells me no "license." Thanks for the info, I will try the free L6 engine.
Something is odd, as I went back and forth between two computers in Logos 5 without ant problem at all. Logos 6 is worth it though so I recommend going that way.
John C. Livesay:Nope. every time I build it on a computer, the next one tells me no "license."
One option is copying compiled pbb files from one Logos installation, then scan in other Logos installation(s).
Copy and scanning lbspbb file(s) avoids having to change path to docx for building on different platforms, then build.
Keep Smiling
Logos Wiki Logos 7 Beta Free Support
One thing that should also be noted (if I understand things right) there is a size limit, so if you have a very large book like Mark Barnes dictionary this would not automatically be sync enabled due to it's size, that said it has to be a very large book to run into this issue.
-Dan
St. Jerome's House † Install
Strange. This is a two page thing, with nothing but a list of doctrines and Scripture references. Other documents sync correctly, but I still cannot access it.
alabama24: John C. Livesay: Every personal book I build on one computer has to be rebuilt on the other computer to be read. I have to keep a flashdrive of my PB files to build every time I change computers.Is that normal or am I missing something? Again, the metadata (author, title, etc.) has ALWAYS synced. The compiled book itself did not. With the release of L6, there is now a method to sync the compiled book. When you have finished compiling a book, you press the "upload" button.
I am obviosly missing somethind here, more-than-likekly over looking something. I have compile two books since I installed Logos 6 onto my Desktop and I never see the "upload" button, either before or after I click finish at the end of the compile. What am I missing or overlooking?
Michael
Rev. Michael L. Burns:I have compile two books since I installed Logos 6 onto my Desktop and I never see the "upload" button, either before or after I click finish at the end of the compile. What am I missing or overlooking?
Maybe the files are simply too large. Have you tried a small one?
Running Logos 8 latest beta version on Win 10
Rev. Michael L. Burns:I am obviosly missing somethind here, more-than-likekly over looking something. I have compile two books since I installed Logos 6 onto my Desktop and I never see the "upload" button, either before or after I click finish at the end of the compile. What am I missing or overlooking?
As Mick suggested, if the file is too large, it is ineligible to upload. I don't know what you are trying to do. If the .docx isnt sensitive or copyrighted, you can upload the .docx here for us to experiment with. Here is what you should see AFTER you have compiled. Notice the very bottom right:
Thanks Mick,
I think the files are simply too large.