SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?


To: Eric L who wrote (36808)9/14/2003 5:36:24 PM
From: mr.mark  Respond to of 110652
 
"although have you ever seen an explanation of why this "stall" occurs, and whether or not it indicates some corruption in either a compressed file or a corruption in NAV?"

while i share your curiosity in matters such as this, *there are times* when i must decide to move on, more or less accepting the fact that finding an explanation would be difficult, time consuming, and possibly not even correct.

and if i have found a viable solution, i realize that that is all i needed from the start, so moving on feels okay.

many times, getting to the bottom of a problem is helpful. other times it seems besides the point.

in the case we are discussing, and i think i linked this fact, after getting the scan to complete (via unchecking the scan within compressed files option), i then made a *point* of scanning the problem file (folder) specifically, all by itself... and it scanned fine.

so the question of why and how could have at that point grown enormously, but i chalked it all up to ghosts in the machine and moved on.

interestingly, if i am not mistaken, over time, i went back to scanning within compressed files and all is well again.

hth