Re: [slim] Beware of 7.1 "upgrade"

2008-07-30 Thread audiogene
aubuti;323979 Wrote: > Smileys aside, you don't have to be a hard core developer to show a > little humility and at least consider that the problems you are > experiencing are *your* problems, rather than going on a rant about the > ignorance and shoddy work of Logitech/Slim and those who contrib

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread aubuti
audiogene;323970 Wrote: > OMG, that was it! While I had noticed the problem in the log I did not > come to this conclusion... But, I think, kdf is a hard core developer > who exactly knows where to trust the code and where not ;) Smileys aside, you don't have to be a hard core developer to show a

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread radish
Those MYI errors look like the ones generated when you have a badly behaved antivirus stomping ok mysql. What av do you run? Is it set to ignore *.MYI files? -- radish radish's Profile: http://forums.slimdevices.com/member

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread audiogene
kdf;323883 Wrote: > Anti-virus! This is the give away debug message. Your anti-virus > software is getting in the way of Mysql. Set it to ignore *.MYI and > *.MYD files. If you had an application exception, that may have gotten > turned off during the upgrade. > -kdf OMG, that was it! While I

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread MrSinatra
also, let us know what AV did this, and if you could set an exception to it successfully. -- MrSinatra www.LION-Radio.org Using: Squeezebox2 (primary) / SBR (secondary) / SBC - w/SC 7.1beta - Win XP Pro SP3 - 3.2ghz / 2gig ram - D-Link DIR-655 --

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread lanierb
And once you have it fixed please update the thread title to resolved. -- lanierb lanierb's Profile: http://forums.slimdevices.com/member.php?userid=5566 View this thread: http://forums.slimdevices.com/showthread.php?t=503

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread BramWithaar
this line "DBD::mysql::st execute failed: Can't create/write to file 'C:\WINDOWS\TEMP\#sql_928_0.MYI'" states that squeecenter can't write the temporary mysql files. I had this error also when my albumart didn't show. Diabling the virusscanner and then starting the full scan solved it. -- BramW

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread kdf
audiogene;323864 Wrote: > contributorTracks.track': DBD::mysql::st execute failed: Can't > create/write to file 'C:\WINDOWS\TEMP\#sql_928_0.MYI' (Errcode: 13) at > C:\PROGRA~1\SQUEEZ~1\server\CPAN/DBIx/Class/Storage/DBI.pm line 771. Anti-virus! This is the give away debug message. Your anti-vi

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread Phil Leigh
Indeed it didn't happen to me either and I'm now on 7.2... Anyway, as I said it hasn't erased your artwork (ie your many cover.jpg files), simply deleted them from the cache - which it should in a full rescan - and for some reason hasn't replaced them. My guess is that something is messing up the

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread MrSinatra
some months back, i went from 7.0 to 7.1 when i did, this did not happen to me. i would suspect, this is not happening to a lot of people. so the question is, why is it happening to you? is there something specific about your setup that would cause this? secondly... would it be possible to s

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread audiogene
Phil Leigh;323832 Wrote: > It can't have "erased" artwork...temporarily not having it in its cache > is rather different. > I would expect a full clear/rescan to fix this. IS the real problem > that you are having scanner issues? In 7.0.1 all artwork found during initital scan had been written t

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread Phil Leigh
It can't have "erased" artwork...temporarily not having it in its cache is rather different. I would expect a full clear/rescan to fix this. IS the real problem that you are having scanner issues? -- Phil Leigh You want to see the signal path BEFORE it gets onto a CD/vinyl...it ain't what you'

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread moley6knipe
Well, all I can say is with a 15k ALAC library with embedded jpegs it didn't lose my artwork cache when I did the same upgrade. If it's missing artwork it'll just build the artwork cache again when you do a rescan, surely? -- moley6knipe Win XP Pro SP3 > dBpoweramp Reference 13.1 > SqueezeCen

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread CatBus
audiogene;323825 Wrote: > As I pointed out I upgraded from a 7.0.1 SC. The 7.0.1 had found and > cached all the artwork - which 7.1 erased. Unable to repro here. Need more details to figure out why your upgrade experience seems to be different than everyone else's. The fact that 7.1 seems to b

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread audiogene
moley6knipe;323820 Wrote: > Well, there must be. How did SC find the art in the first place? As I pointed out I upgraded from a 7.0.1 SC. The 7.0.1 had found and cached all the artwork - which 7.1 erased. -- audiogene a

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread moley6knipe
audiogene;323811 Wrote: > During the migration of the database files all artwork files in the > artwork cache were erased. There is no way to get the artwork back - > neither by a rescan, nor by physically deleting all cache files and > doing a fresh scan. Well, there must be. How did SC find t

Re: [slim] Beware of 7.1 "upgrade"

2008-07-29 Thread Michael Herger
> As some already pointed out the new "official" release 7.1 of the SC > looks like a half-baked snapshot probably released under management > pressure (or is it plain ignorance?). Following the current discussions > on the beta board there are so many open issues with this version branch > and it

[slim] Beware of 7.1 "upgrade"

2008-07-29 Thread audiogene
As some already pointed out the new "official" release 7.1 of the SC looks like a half-baked snapshot probably released under management pressure (or is it plain ignorance?). Following the current discussions on the beta board there are so many open issues with this version branch and it is hardly