Amiga.org

The "Not Quite Amiga but still computer related category" => Alternative Operating Systems => Topic started by: Wilse on October 06, 2004, 06:45:45 PM

Title: MOS emu / sblive driver?
Post by: Wilse on October 06, 2004, 06:45:45 PM
Stupid question, I know, but I just reinstalled my SBLive 5.1, which has been in my A1 for the last several months.

Thing is, I've forgotten where to find/put the driver.

Someone put me out of misery please. :-D
Title: Re: MOS emu / sblive driver?
Post by: Star69 on December 07, 2004, 11:34:15 AM
Read the chipset off the large chip on the board and search for it on either www.soundblaster.com or www.driverguide.com.  I would recommend the latter as the soundblaster website is cr@p and if it's an OEM product (usually if it came pre-installed on your system), Creative don't support it(!?!?)
Title: Re: MOS emu / sblive driver?
Post by: CaptainHIT on December 07, 2004, 12:08:54 PM
@ Star69:

Since when does creative or driverguide sites offer MOS drivers for those cards? :-D
Title: Re: MOS emu / sblive driver?
Post by: CaptainHIT on December 07, 2004, 12:15:15 PM
@ Wilse:

I don't know about MOS ver much, but i guess the design is nearly identical to the Classic Amiga, so i will tell you where the driver for that is, maybe it will help you find out it for MOS also. :-)

It's maybe AHI related, so:

SYS:Devs/ahi.device is the ahi.device itself...
SYS:Devs/AHI/sb128.audio could be the driver you need.
SYS:Devs/AudioModes/SB128 contains the audio modes that are available with that card.

So this info was given for a Soundblaster128 installed in a classic Amiga using AHI. Maybe you should have a look there too. But i really don't know about MOS. And where to get the MOS drivers?
Maybe some MOS people will answer to that. ;-)
Title: Re: MOS emu / sblive driver?
Post by: Tempest on December 07, 2004, 01:03:39 PM
@Wilse

You can find the MOS AHIusr package here:

http://www.lysator.liu.se/~lcs/files/ahi/beta/
Title: Re: MOS emu / sblive driver?
Post by: Star69 on December 07, 2004, 01:35:21 PM
Should have been paying attention there :oops: