Perhaps interesting to a cryptologist ... but the relationship to the search term is less than obvious.
MJ, I think your are running the secret Bible Code search. Try searching for Obama and see if there are any hidden prophecies.
It works fine for me. It looks like yours has the wrong verses displayed. Is the Grid view also wrong?
You wouldn't happen to have indexing running when you do this. It looks like the search is point to the wrong location in the texts. An incomplete index would explain this (I think).
What version of the NRSV do you have?
(Go to the NRSV window and click the (i) to get the resource info and scroll down to the bottom)
What is telling the the length of time in search results
Todd 212 in 210 verses 10.68 sec
MJ 832 in 790 in 1.55 secs
This seems to indicate an indexing problem still.
MJ can you try in the command bar (CTRL+D) typing update resources or update now and see if you get anything.
The thing to remember is that indexing intially takes a very long time and if you shut down or your machine hybernates it won't pick up from where leaving off - it generally starts again.
CORRECTION: I miss understood in the beta - the indexing should continue from where it left off. Sorry if I confused you
Jason
I hibernated once accidentally while still indexing and it picked up the process and continued afterwards.
What is telling the the length of time in search results Todd 212 in 210 verses 10.68 sec MJ 832 in 790 in 1.55 secs This seems to indicate an indexing problem still. MJ can you try in the command bar (CTRL+D) typing update resources or update now and see if you get anything. The thing to remember is that indexing intially takes a very long time and if you shut down or your machine hybernates it won't pick up from where leaving off - it generally starts again. Jason
MJ searched over her Top Bibles, and I only searched NRSV since I don't know what her Top Bible are. That accounts for those differences. A search over my top bibles showed no problems. I thought it possible that her NRSV isn't the latest version since I once experienced highlight problems like that in the beta. However you look at it, it's still a problem, because, even if she is still indexing, it shouldn't show bad data.
P.S. Hibernate or standby will not kill the indexing process. Only shutdown will.
However you look at it, it's still a problem, because, even if she is still indexing, it shouldn't show bad data.
Well, Todd, I'm not quite sure how indexing works, but if she had an older NRSV that was replaced, and her current index points to the older, now updated, resource, the locators in the index could be pointing to locations that have shifted in the new resource. The search takes advantage of indexing by looking at the index, rather than the resource. This is quicker, but requires that the index be pointing to the correct place in the correct resource. So an old index with a new resource may cause the kind of problem we're looking at here.
Of course, I could be way off in how I understand this to work. In which case, I'll buy you a cup of coffee next time you're in town.
Thanks for the help - it is back working again so I will assume that indexing was going on ... despite there being no overt indication of it. It wouldn't be the first time that the indexing has appeared to be done but ...
Well, Todd, I'm not quite sure how indexing works, but if she had an older NRSV that was replaced, and her current index points to the older, now updated, resource, the locators in the index could be pointing to locations that have shifted in the new resource. The search takes advantage of indexing by looking at the index, rather than the resource. This is quicker, but requires that the index be pointing to the correct place in the correct resource. So an old index with a new resource may cause the kind of problem we're looking at here. Of course, I could be way off in how I understand this to work. In which case, I'll buy you a cup of coffee next time you're in town.
Makes perfect sense, but I still think they should detect it or prevent it while indexing is going on and tell the user. That's why I said it's a problem. I was obviously wrong about the reason, so you saved your three dollars for the mocha frappachino you were going to buy me. (not a big fan of regular coffee)
$3. Hmm. I'll put that in a jar and start saving for Portfolio. Let's see, if I save $3/week, how long will it take to get to $2100 . . .
Makes perfect sense, but I still think they should detect it or prevent it while indexing is going on and tell the user. That's why I said it's a problem. I was obviously wrong about the reason, so you saved your three dollars for the mocha frappachino you were going to buy me. (not a big fan of regular coffee) $3. Hmm. I'll put that in a jar and start saving for Portfolio. Let's see, if I save $3/week, how long will it take to get to $2100 . . .
If you buy one resource a week, how long before the upgrade price is less than $200?
Hi can you post your system specs? Thanks.
