>Are you deleting everything in the cache before trying this?
No, I didn't do that; assumed that starting a "Clear library and rescan
everything" would do that.
>The scanner keeps its status in a table in the database, so if a scan hangs up
>you
>could be stuck until you clear the table or delete the database.
I tried deleting all *.db files in the cache folder, and then starting SBS 7.6.
It immediately started a full rescan at startup, and whilst it was doing the
"discovering files" stage, it reported progress and didn't say the scan was
completed.
As soon as it got to "Scanning new files", it started to show that the scan was
finished, whilst also showing that the scan was still progressing (the scan
time is being refreshed every 5 secs).
I think actually the scanner has crashed (event viewer shows a perl.exe crash):
Application popup: perl.exe - Application Error : The instruction at
"0x08cf4364" referenced memory at "0x0518e038". The memory could not be "read".
So part of SBS thinks the scanner is still running because it never completed,
whilst other parts of SBS knows the scanner is not running?
So maybe I'll try to identify the track that's causing the scanner to fall
over; it needs to be a bit more robust (somehow handle bad files/tags without
crashing or at least detect/report when it has unexpectedly crashed).
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
