Missing Resources in Beta install in separate Windows account

Mark A. Smith said:

Chris,

How about copying the files to a new location, then using the scan command in the new installation to see if Logos will pick these up and transfer them to your resources directory?

Mark,

I realize I could do this, but wondered if that might "corrupt" the beta - in light of Bradley's stern warning in http://community.logos.com/forums/t/8883.aspx

Bradley Grainger said:

Do not share resources or Data folders between the stable Logos 4 and the Logos 4 Beta release; the format of data files and (some) resources in Logos 4 Beta may have changed, making them unreadable by Logos 4.

 And, I don't think it should miss a bunch of resources. It's the old "If it misses these this time, what might it miss another time" fear of the Cloud.

I guess I'd like to get a fix rather than a work around.

Chris

Mark A. Smith said:

I think Bradley's warning is about shared resources and folders. Copying then scanning would put those resources into your new folder. You wouldn't be sharing them.

Oh, I thought he was warning that "some" resources have changed format and can't be shared (or exchanged). Because I don't know which I was unwilling to go ahead like a bull.

I also wondered how someone who hasn't messed around like we have in our files would be able to solve this issue.

Because it affected a resource I use for a reading plan it was obvious something was wrong - it was all over my banner - like a Banner in the Sky!

Chris

Mark,

I tried moving one of the missing files and then ran scan. Closed L4 and re-opened. Waited. No resource. Closed again. Re-opened. No resource.

Still at 1314 resources.

I think my licence must be corrupted on the server. I suspect I'll have to call. I guess it will have to wait until Monday.

I might try a straight copy the file into the beta resource file - don't remember if some have found this works or not.

Chris

EDIT: Must have mistyped something. Tried again and now it's there.

Now for the other ones.

Rosie Perera said:

Chris Elford said:

I think my licence must be corrupted on the server. I suspect I'll have to call. I guess it will have to wait until Monday.

 

Just FYI, if you suspect a corrupted license file, the corrupted one might be on your computer rather than on the server. It is safe to delete your copy of it and force it to be downloaded fresh from the server, as instructed by Bradley Grainger in this post.

Sounds like you're on the way to success though, so you probably don't need to try this.

Rosie,

Thanks for that. I remember seeing that post, but never put it together with my issue. I tried it, the license.dat file that was downloaded today is different from the one that was installed when I put the Beta on, but update resources still says there are no updates available.

Scan seems to be the only solution.

FWIW, here's are the files that were not installed:

Chris

Stephen Filyer said:

Chris be warned:

three of these files will cause problems. You do NOT want them on any system:

LEXHAMSGGNT.lbssyn

LEXHAMSGGNT.lbxclv

(and I think ) LEXglossary.logos 4 (not sure of it)

But the first two have been replaced by the newer CASCADIA files etc.

Dave Hooten has a thread on this somewhere in response to a problem I had with these. They were supposedly OFF of mine yet were still CRASHING everything (ie. M$ error report etc.)

Regards

Steve

Thanks, Steve. I haven't actually scanned them in yet -- just the 131 people book, because I wanted to give time for such a response as yours.

What's funny (not ha ha, but CURIOUS) is that those are in my SR2 data files and aren't causing any problem. I had problems during the private beta when they converted to Cascadia. I hadn't picked up on the fact they had not deleted those files.

Are you (along with Dave) recommending they be deleted from all files.

EDIT: Steve, the first two files are .lbssyn and .lbxclv, but the Glossary files is a .logos4 file, so I think it is probably safe.

Chris