Newsgroups:	comp.os.msdos.djgpp
From:	Elliott Oti <e DOT oti AT stud DOT warande DOT ruu DOT nl>
Subject:	Re: MikMod and SoundBlaster
Sender:	usenet AT fys DOT ruu DOT nl (News system Tijgertje)
Message-ID:	<33988C5F.23EF@stud.warande.ruu.nl>
Date:	Fri, 6 Jun 1997 22:17:03 GMT
Reply-To:	e DOT oti AT stud DOT warande DOT ruu DOT nl
References:	<33972814 DOT 7B9C AT fcbob DOT demon DOT co DOT uk>
Mime-Version:	1.0
Organization:	The Gauge Variance Promotion Society
Lines:	27
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Dan Goodman wrote:
> 
> I recently tried to get MikMod working, and it will run fine in DOS, but
> when I run it through Windows, I either get it saying it is running in
> No Sound mode, or in 8 Bit Mono (and nothing comes out). My Blaster
> variable is set to A220 I5 D1 T4 (what does the T mean by the way?
> excuse my ignorance...). The card in a SoundBlaster16B 3D according to
> the text file. Any ideas?

I have written a number of programs using MikMod in the past and all of
them have had problems running under Windows (3.11 and 95). The MikMod
port to DJGPP has a number of problems: in my experience on something
like 95% of the cards and machines it runs on, it fails to initialise
the SoundBlaster card properly if run first before any other programs
initialise the sound card. I.e if you start Windows/DOS without sound
(no digitalized soundbites/chimes) MikMod will fail to find the card. If
the sound card *is* initialized, Mikmod will start OK, but often
misbehaves when playing samples. It puzzles me, because it doesn't hook
the timer interrupt at all -- a source of trouble with other mod
libraries under Windows. 
My solution to the card initialization problem is to use the SB05DJ
initialization routines instead (cut and paste :). As for the erratic
behaviour under Windows, well ... Program N' Pray :)

-- 
------------ Elliott Oti ---------------
   ------------- http://www.fys.ruu.nl/~oti  ---------

- Raw text -