BUG: Verbum 5.2b6 will not scan this file

I have one file, NGUIDE21.LSF, which will not scan into the Mac version of Verbum - it is in my Windows version of Verbum, and it is not corrupt as I can bring it up and peruse it. Is there another way I can get this file loaded into my library? Thanks

Find more posts tagged with

Comments

Dave Hooton

I think you also need its index file NGUIDE21.LIX.

Don Awalt

https://community.logos.com/discussion/comment/613259#Comment_613259

Thanks Dave, I have that in the same folder

Would logs help figure out why it' not being loaded in to the Mac library?

Don Awalt

https://community.logos.com/discussion/comment/613330#Comment_613330

Another question, Dave, could the index file be bad? I did try searching on a phrase that wold be found in there and it worked...

Don Awalt

https://community.logos.com/discussion/comment/613340#Comment_613340

As a test I did Hide on a Windows version of verbum, then unhide, restarted and it did not show the file in my library - which is to be expected as I do not think this is on the Logos servers. But then, I SCANed the folder where the file and its index were, restart5ed and the resource was there. So this is some sort of bug in the Mac version it appears.

Don Awalt

https://community.logos.com/discussion/comment/613347#Comment_613347

I think the Mac version does not recognize the valid license. On a Windows Verbum, I dragged the resource to the bar at the top. From the Mac version, I clicked it. It said "You don't have a license to view this resource". The license number is correct - LLS:1000.3.3 I found in a prior test that if a resource is hidden, it will say so.

Why does the Mac version say I don't have a license to this?

Can anyone from Logos reply - Bradley have you read this?

I would just like to know if it's bug that Logos can fix so I can get all my resources on the Mac version of the product.

Thanks!

NB.Mick

https://community.logos.com/discussion/comment/613398#Comment_613398

Strange. It seems Logos doesn't recognize 1000.3.3 (nor nguide21 either, looks just the same) as valid resources:

Don Awalt

https://community.logos.com/discussion/comment/613419#Comment_613419

It does on Windows. I even hid it and rescanned it under Windows to make sure it was till recognized, and it worked perfectly. This is a Mac bug.

It's an old user guide, I could just hide it to have the libraries match, but I thought this might be a bug that affects other licensed products since it pops up from time to time. It sure would be nice to hear from Logos, I guess I will have to call next week, it doesn't appear anyone from Logos will respond here despite my requests.

Dylan Rondeau

https://community.logos.com/discussion/comment/613434#Comment_613434

It does on Windows. I even hid it and rescanned it under Windows to make sure it was till recognized, and it worked perfectly. This is a Mac bug.

It's an old user guide, I could just hide it to have the libraries match, but I thought this might be a bug that affects other licensed products since it pops up from time to time. It sure would be nice to hear from Logos, I guess I will have to call next week, it doesn't appear anyone from Logos will respond here despite my requests.

Hi Don,

It took me awhile to track down a copy of the resource (since .lsf/.lix resources aren't on our servers, I had to find the actual file), but I experienced similar issues scanning it into my Mac. Are there other resources with those extensions you scanned that did work? I presume there's something wrong with that particular resource somehow. I've made a case for a developer to see what's going on.

Also, in the future, if you need or expect a more immediate response, it's probably best to call Tech support (especially if it's urgent) or to email us at logosbugs AT logos.com. That inbox is checked often, and doesn't have the threat of being buried under other threads. A resource not scanning is definitely an issue we want to address, but may not be as high priority as it is for you, and therefore might take longer to get to. A 1 day turnaround in the forums is (I feel) reasonable, especially when the thread is posted at the end of the day. That said, I'm sorry you felt your issue was neglected.

Don Awalt

https://community.logos.com/discussion/comment/613436#Comment_613436

Hi Dylan, thanks for the reply. It's not a significant resource, but I was concerned it might be a bug that affects other resources and I thought it should be addressed. Thanks for the tip about the email and phone. Sometimes we get into using the forums because people here know so much, it seems 90% of the time the problem can be solved without bothering tech support!

As for other LSF files - I thought of that too, I have 4 other LSF files that scanned in fine on the Mac - so it must be this resource or its corresponding index file.

Thanks for checking into this!

fgh

https://community.logos.com/discussion/comment/613436#Comment_613436

A 1 day turnaround in the forums is (I feel) reasonable

Definitely (unless it's a crash without a workaround, or something else extremely urgent, like an empty Library). I remember when the average response time for my bug reports was about a month. And before that there were no responses at all. You just had to hope they were read (which it has turned out afterwards they weren't).

In justice to Don, though, his issues started with Mac Question - scan on Wednesday, then went on to BUG in 5.2b beta 6 Mac - scan does not work on Thursday, then to this thread, BUG: Verbum 5.2b6 will not scan this file, later the same day, and finally to BUG: Mac version of 5.2B6 says I don't have a valid license but I do on Friday. I can understand why to him it feels like a very long time has gone by without a response from Logos. I was surprised myself to find that it was only two days. It felt like I'd been getting posts about it for most of the week. And I'm not emotionally involved, the way he is.

Don Awalt

https://community.logos.com/discussion/comment/613627#Comment_613627

Hi Dylan, I was wondering if anything has been discovered as to why this resource won't scan?

thanks!

Don

Don Awalt

https://community.logos.com/discussion/comment/614844#Comment_614844

Hi Dylan, I was wondering if anything has been discovered as to why this resource won't scan?

thanks!

Don

Dylan Rondeau

https://community.logos.com/discussion/comment/616789#Comment_616789

Hi Dylan, I was wondering if anything has been discovered as to why this resource won't scan?

thanks!

Don

Hi Don, sorry I missed your last post. We do have a developer who is looking into the case, but as of yet I haven't heard anything. Sorry for the delay on this, I will let you know as soon as I hear back. I apologize if the issue is getting in the way of your study. [:(]

Don Awalt

https://community.logos.com/discussion/comment/616858#Comment_616858

No problem, just interested in getting it resolved. Thank you for your help Dylan!

Don Awalt

https://community.logos.com/discussion/comment/616903#Comment_616903

Hi Dylan, is there any chance this inability to read an old resource will be resolved in 5.3 now in beta? I fear it will be lost in all the beta activity, and I have hope only in that you said its more serious when a resource can no longer be read in Logos. It's rather small and insignificant, so I worry this won't be fixed any time soon, if ever. Plus the precedent scares me.

Any hope?

Thanks,

Don

Dylan Rondeau

https://community.logos.com/discussion/comment/622097#Comment_622097

This is fixed in 5.2b SR-4.

Don Awalt

https://community.logos.com/discussion/comment/635349#Comment_635349

Hi Dylan, I tried the Scan of NGUIDE21.LSF/LIX and it did not work. I know the Scan worked because I had a pbb I had compiled on my Windows machine in the same Resources folder, and that scanned in successfully.

Note I am on Verbum Mac not Logos, could that make a difference?

Let me know what if anything you want me to do.