I have similar issues.
I am using XP Pro on a Dell 8400. I have clean installed the latest
6.5.1 after uninstall 6.5.0 via Windows and removed the directory
itself after reboot.
I have random crashes and always a crash at the end of a scan of the
library. I cannot display album art in album
Amadeus;157584 Wrote:
Suggestions? Is it the space between the words 'program' and 'files'?
Try single quotes (or is it double quotes?) around the path.
--
Mark Lanctot
Mark Lanctot's Profile:
Amadeus;157584 Wrote:
Suggestions? Is it the space between the words 'program' and 'files'?
You can try this as two commands.
CD C:\program files\slimserver\server (Press Enter)
slim.exe --d_scan --d_import --d_info(Press Enter)
Please note the double quotes in the first command line.
Thanks for the help. I was able to execute this command.
I was able to rescan my library. It crashed at the end of the scan
with the error message scanner.exe has encoutered a problem and needs
to close. We are sorry for the inconvenience.
(I used to use McAfee and now I use Kaspersky 6.0
Marc Sherman;139481 Wrote:
mcknej01 wrote:
After repeated previous attempts to use the beta of 6.5. I bit the
bullet again yesterday and moved from 6.3.x to the release version
of
6.5. As with the Betas this has not been a glowing success.
Did you file bugs about the problems you
stop the server.
start-programs-accessories-command prompt
type c:\program files\slimserver\server\slim.exe --d_scan --d_import
--d_info and press enter.
wait a bit for slimserver to get started, then open up your browser to
http://localhost:9000
start a clear library and rescan everything
I've never been able to complete a full scan with 6.5 / MySQL, the .db
file gets to about 18Mb in size then appears to crash. The server then
continues to run really slow, requiring a reboot. Hopefully someone
with more experience of the MySQL error messages in my original post
will be able
Same thing was happening to me after both upgrading and fresh install
(WinXP Pro, library with about 11,000 songs).
I tried running scanner.exe from the command line as described above,
and found an error message about a duplicate value in the years table
(after which the scan aborted).
Turns
I've seen this a couple of times this morning, too, when trying to do a
full clear rescan... at the time I kicked it off, there were around
57,000 tracks in the DB - maybe there's a faster way to obliterate all
the data? I'm on XP, running the new 6.5 release version, default
config.
--
