[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::windows95

Title:	Microsoft Windows 95 ("Chicago")
Notice:	Please read topics 1 to 22 before writing anything
Moderator:	EEMELI::BACKSTROM

Created:	Sun Nov 13 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2958
Total number of notes:	19968

2896.0. "Sound Blaster Emulation for Multia" by JULIET::CABREIRA_RO (Bobby Cabreira) Tue Apr 08 1997 03:20

    A customer  has a Multia Enterprise client, which is now end of lifed.  
    The system was qualified for Windoows NT, and everything seemed to be
    working.  The customer has decided to install Windows 95 in this
    system, and is has a problem with the sound.   It has an imbedded 
    sound blaster compatible sound chip.  
    
    In one system, it works o.k., and looking at the Devices and
    properties, we see:
    
    	Sound, Video and Game controllers
    		MS Windows Sound System compatible
    		Windows Sound system Sound Blaster Emulation
                                                                  
    In other systems, it does not work, and Device Properties for MS
    Windows Sound System compatible has
    a Yellow Exclamation.  It also does not have "windows Sound system
    Sound Blaster Emulation".  Looking at the properties,  they are using 
    the same drivers( msopl.drv, mssndsys.drv, mssndsys.vxd), 
    and the same Resources.  (I/O 534-537, I/O 388-38B,
    Interrupt=9, DMA=0, DMA-1)
    
    The difference between the two is,  the first one has an extra tab
    (under properties) which is titled SETTINGS, and under it has a
    Emulation Support- Enable Sound blaster button (which can be checked).
    Also,  under the Windows Sound System-Sound Blaster Emulation, it has
    resources, and it is I/O 220-22f
    
    
    These 2 systems are exactly the same, and if a new reinstall of Windows
    95 is initiated on both systems,  the Device Sound blaster Emulation
    would not show up anymore.
    
    Question:
    
    1.  Under what circumstances would  the "Sound Blaster Emulation" be in
    Device properties? 
    2.  Is there any thing that we could do in the registry 
    to get the system to recognize and know that it needs to set it as
    Sound Blaster Emulation?
    
    
    Thanks,
    
    Bobby C.

T.R	Title	User	Personal Name	Date	Lines
2896.1	Not an answer but a vague recollection.....	CHEFS::TREVENNOR_A	A child of init	`Tue Apr 08 1997 06:40`	14
	Bobby, I'm guessing here but don't those SB compatibles have some kind of FLASH in them which can be updated? I remember being told by someone that you could upgrade the firmware on the chipset to fix some problems in the SB compatibility mode. I don't know who you would ask about it, have you trawled the PCBU web pages to look for something of this sort? I'm guessing that when this system had NT on it it might have had Can the BIOS on the machine tell you the rev levels? auto-updated the firmware rev levels or something? Just a thought. AT.
2896.2		NETCAD::GENOVA		`Tue Apr 08 1997 11:14`	6
	I have the same problem on one of my Multia's running Win95. I also haven't fiqured/stumbled out/on how to fix it. /art
2896.3		PCBUOA::BAYJ	Jim, Portables	`Tue Apr 08 1997 13:23`	19
	I have very bad (unofficial) news. It turns out that there were anomalys with the sound in the Multias. Now perhaps this only pertained to pre-release engineering samples. So take it with a big grain of salt. However, in the units we had, there was about a 50% no-op rate of sound in the Intel Multia units. I can't recall the exact diagnosis. It was either a manufacturing problem, or dual sourcing of the sound component. But the bottom line was, some had sound, and some didn't. Now, this isn't necessarily the case under Windows 3.1. However, NT just couldn't handle some of the subtle differences in the units. Again, I will state that this may only apply to pre-release, engineering samples. However, there were a lot of dissappointed folks who took Multias home and found they had no sound. jeb (ex-Multia developer)
2896.4	Multia = Alpha?	NETCAD::ATKINSON	Dave Atkinson	`Wed Apr 09 1997 15:30`	10
	<< A customer has a Multia Enterprise client, which is now end of lifed. << The system was qualified for Windoows NT, and everything seemed to be << working. The customer has decided to install Windows 95 in this << system, and is has a problem with the sound. ^^^^^^^^^^ Isn't Multia an Alpha product? Windows 95 is not an Akpha product and FX!32 doesn't do well with low level drivers, much less entire OS's ;-) Dave
2896.5		AXEL::FOLEY	http://axel.zko.dec.com	`Wed Apr 09 1997 16:03`	5
	There are/were Intel Multia's also. mike
2896.6	Need more information	NNTPD::"[email protected]"	Eric Dube	`Thu May 22 1997 19:49`	12
	Bobby- If I can get more information on your setup that works, I could probably reproduce the installation on my Multia in my office. I'm going to need some registry information though. Regards, Eric Dube [email protected] [Posted by WWW Notes gateway]