Is it possible to give any indication of when the next release is due?

Usually 4 weeks apart. In the mean time you can use ossmix to set the
specific settings. You will need to look at the device's README files (under the docs directory for specific settings). Eg SBLive supports
FRONT+REAR, FRONT, REAR, DISCRETE - you can set it as
ossmix spkmode FRONT or ossmix spkmode REAR, etc.

I'm still getting a problem with the driver starting at system startup though. This would appear to be because the path in /etc/rc.local points to /usr/local/bin/soundon, whereas the binaries (and everything else) are installed into /usr/lib/oss/bin . Should I (a) change the path or ((b) move the binaries to /usr/local/bin?

I'm still getting a problem with the driver starting at system startup though. This would appear to be because the path in /etc/rc.local points to /usr/local/bin/soundon, whereas the binaries (and everything else) are installed into /usr/lib/oss/bin . Should I (a) change the path or ((b) move the binaries to /usr/local/bin?

I think you are mistaken /etc/rc.local? i wouldnt it start it that way on freebsd....place start up scripts under /usr/local/etc/rc.d/

The simplest shortest way is to link soundon, soundoff etc to your path for example ln -s /usr/lib/oss* or /usr/local/bin/oss* depending on where you installed oss to /usr/bin/

I think you are mistaken /etc/rc.local? i wouldnt it start it that way on freebsd....place start up scripts under /usr/local/etc/rc.d/

No, I'm not mistaken, the message I get is as I reported. Also using /usr/local/etc/rc.d for startup scripts is deprecated in fbsd 5.*, which is perhaps why the installation did it that way. All the install paths were determined by the installation and then update procedures, not me.

I think you are mistaken /etc/rc.local? i wouldnt it start it that way on freebsd....place start up scripts under /usr/local/etc/rc.d/

No, I'm not mistaken, the message I get is as I reported. Also using /usr/local/etc/rc.d for startup scripts is deprecated in fbsd 5.*, which is perhaps why the installation did it that way. All the install paths were determined by the installation and then update procedures, not me.

Hi,

We've also fixed up the automatic boot setup. THe problem was that the rc.local had /usr/local/bin/soundon and the older OSS 3.9.8 used to put a copy of soundon in /usr/local/bin. We've updated the FreeBSD 3.99.1i version with the proper fix - now if you enable automatic boot setup it will add the proper path to soundon in /etc/rc.local

You can place startup scripts in /etc/rc.d too but i would not, its fine if they place it in rc.local, as far as i know its not in use but you can create a rc.pleh and it will run if you get the point.

The installation of the incorrect path into rc.local is something the installer did, not me. I was merely reporting the problem. I would also not put anything into rc.local, or even create the file. All I did was run the install instructions.

The installation of the incorrect path into rc.local is something the installer did, not me. I was merely reporting the problem. I would also not put anything into rc.local, or even create the file. All I did was run the install instructions.

I know i wasnt blaming you...I think there maybe a miscommunication from my first post, cuz i did not speak of the soundconf option to install start up scripts rather a do it yourself method. So no hard feelings enjoy