All I get is a pinwheel spinning and then a blank screen.
Logos Bible Software 6.0 SR-16.0.0.3721
Windows 8.1
16G Ram
3.40GHz
I have just noticed this as well.
Since I upgraded to the latest version that is all I get as well.
I was also experiencing problems earlier, but it seems to be working now. If you encounter additional problems, please report them here.
I am also experiencing this sometimes logos locks up and I have to use task manager to kill it Win 7 X 64
The servers are down. See the plethora of threads In this and the general forum.
After the server crash my Visual Copy no longer works. I get the error: "Some templates are unavailable. Retry" But no templates are showing.
Model Identifier: MacBook7,1
OS: Mavericks
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 3 MB
Memory: 4 GB
Visual Copy is still offline; please see this post for the current status: https://community.logos.com/forums/t/96696.aspx
Visual Copy is working again.
it is not working for me.
Hi Hayden - and welcome to the forums
Sorry to hear you are having problems but the particular issue discussed in this thread was resolved in November 2014. I suggest you start a new thread in this forum providing as much details about the problem you are seeing.
I've just tried it and it seems to work fine so I don't think it is a system-wide issue
Graham
This feature has stopped working for me again - when I try to "share" it via facebook it says "object moved" and it no longer appears in the posts.
Brian
This feature has stopped working for me again - when I try to "share" it via facebook it says "object moved" and it no longer appears in the posts. Brian
strange. [:s]
in the meantime, try saving the image and manually uploading to FB.
I can reproduce this.
Alabama's suggestion is a good one. If that doesn't work I suggest you start a new thread so it can be looked at.
If that doesn't work I suggest you start a new thread so it can be looked at.
I agree with Graham, but in either case, a new thread should be created clearly explaining and documenting the bug / error.
