[slim] Re: 6.2.1->6.2.2 now gets "Can't open file for:"

2006-02-07 Thread John Stimson
I think I figured it out. The custom conversions file is called slimserver-convert.conf according to the slimserver Wiki. That's what AlienBBC uses. I guess I will still have to pay attention to changes to slimserver-convert.conf and custom-types.conf when I upgrade AlienBBC. -- John Stimson

Re: [slim] Re: 6.2.1->6.2.2 now gets "Can't open file for:"

2006-02-06 Thread kdf
Quoting John Stimson <[EMAIL PROTECTED]>: Is the use of those files documented somewhere? I have looked for documentation for the slimserver software. The slimdevices web site refers me to the "help" section of the slimserver web interface. I can't find anything in there. The only other docu

[slim] Re: 6.2.1->6.2.2 now gets "Can't open file for:"

2006-02-06 Thread John Stimson
Is the use of those files documented somewhere? I have looked for documentation for the slimserver software. The slimdevices web site refers me to the "help" section of the slimserver web interface. I can't find anything in there. The only other documentation I can find is the Installation.txt

Re: [slim] Re: 6.2.1->6.2.2 now gets "Can't open file for:"

2006-02-06 Thread KDF
John Stimson wrote: It was an issue with the conf files. I copy them forward to preserve AAC support so I don't have to hand edit the new conf files. It's worked up to this point. Can slimserver.conf include changes to the types established in types.conf or the recipes given in convert.conf?

[slim] Re: 6.2.1->6.2.2 now gets "Can't open file for:"

2006-02-06 Thread John Stimson
It was an issue with the conf files. I copy them forward to preserve AAC support so I don't have to hand edit the new conf files. It's worked up to this point. Can slimserver.conf include changes to the types established in types.conf or the recipes given in convert.conf? That would be an easi

[slim] Re: 6.2.1->6.2.2 now gets "Can't open file for:"

2006-02-04 Thread notanatheist
Use either Swaret or Slapt-get to get your Slack box up to date. Mine has been brought up from around 9 to 10.2 that way. After which, rebuild the modules, and go. I've never done a rescan or copied config files since it should be looking in ~/.slimserver.conf for settings. -- notanatheist