🚀 go-pugleaf

In article <437n53$v...@news.ccit.arizona.edu>,
Robert  Dejournett <rob...@argon.GAS.UUG.Arizona.EDU> wrote:
>In article <42t6uh$s...@access1.digex.net>,
>Robear <rob...@access1.digex.net> wrote:
>>In article <42rs9f$l...@dingo.cc.uq.oz.au>,
>>Andrae Muys <a.m...@mailbox.uq.oz.au> wrote:
>>
>>>Anyway from experience's associates have had with the dreaded Win95
>>>its implementation of DOS is severly flawed. (just try modifying your
>>>system files for one 'feature').  Personally I'll stick with
>>>3.xx/Linux and if I need 32-bit Windows I'll go to either WINE,
>>>DOSemu, or NT.
>>
>>>Andrae Muys
>>
>>I've run about 30 DOS games, some of them fairly picky about setup, under
>>W95.  Its' DOS seems flawless.  Care to tell us how it is flawed?  I'd
>>like to know what to avoid, and right now, everything I've tried works.
>>
>>David Pipes
>
>How about the sound support?  I have a GUS and an original SB and can't
>get *either* of them to work...The GUS drivers for win3.1 don't work for
>95, and the soundblaster I can't a squeak or anything out of ;)  THe games
>actualy seem okay, i ran warcraft and MOM to name just two under 95, but
>without any sort of sound it is disappointing (sound, voice, or music, 
>that is!)
>
>-ROb
>

My SB16 with Roland worked flawlessly, first time.  Hmmm...  Did you check to
see that it was using the correct drivers, and that they are not conflicting
with each other?

If it loads the GUS drivers first, they probably take up the resources for
the SB16, and hey presto! neither works.  I got mine to work by specifying
the SB16 and the MPU-401, so it can talk to two interfaces at once.

I had two device driver conflicts, and one had the same symptoms - the device
didn't work at all until I removed the conflict.  Take a look.

Good luck,
	David Pipes