Sound blaster 16 ct1740
![sound blaster 16 ct1740 sound blaster 16 ct1740](http://yehar.com/blog/wp-content/uploads/2010/10/CT2940-cut1.jpg)
The Panasonic interface is harmless because it does not require any resources beyond the I/O range used by the Sound Blaster 16. On some OEM boards, the CD Interface ports may not able to be disabled by design. On retail boards, the IDE port should be able to be disabled. The next generation began to add IDE support. The SCSI interface took up an IRQ and did not support booting hard drives. One board, the Sound Blaster 16 SCSI, had a SCSI port for a SCSI CD-ROM, and it could not be disabled. SB16s with the ViBRA chips are be detailed below.įirst generation SB16s supported Panasonic, Mitsumi or Sony CD Interfaces. Unfortunately, if you have to load CTCM, it adds noticeably to the boot time when booting to DOS. This allows you to disable the joystick, the MPU-401 MIDI interface, the Adlib Ports, High DMA or the whole card.
#Sound blaster 16 ct1740 software#
They are initialized through the software Creative Technology Configuration Manager (CTCM.EXE) and configured and disabled through the Creative Technology Configuration Utility (CTCU.EXE) or in PNP operating system like Windows 95. If you have a ViBRA chip, then you may have an ISA Plug N Play card. SBCONFIG.EXE or DIAGNOSE.EXE needed to be loaded in AUTOEXEC.BAT to tell the card which resources to use at boot. However, IRQ and DMA selection were done in software on startup. Second generation SB16s with the CT1747 Bus Interface and OPL chip required jumpers to set the I/O range (IOS0 & IOS1), joystick enable/disable (JYEN) and MIDI I/O Select 330/300 (MSEL). This bug will not be present in any card using the CT-1747 chip.įirst generation SB16s with the CT1746 Bus Interface chip were strictly configured by jumpers. The best fix for the problem is to use another card for MIDI. The bug will only occur when digital sounds and midi are being played. DSP versions 4.04, 4.05 and 4.16 will not suffer from this bug. The affected DSPs have been identified as versions 4.11, 4.12 & 4.13. This includes Star Wars - X-Wing and Tie Fighter (floppy versions) are good examples of such a game. Any game using LucasArts iMuse system may be subject to it. There are other games which may occasionally produce hanging notes regardless of the midi interface being used. : DOOM, DOOM II, Heretic, Hexen, Raptor, Hocus Pocus, Duke Nukem 3D and Blood are all examples of games which suffer from this bug.
![sound blaster 16 ct1740 sound blaster 16 ct1740](http://www.amoretro.de/wp-content/uploads/creative_sound_blaster_16_multi_cd_ct1750_isa_soundkarte.jpg)
It is important to identify games which produce hanging notes as a result of incompatibility with the various DSP versions of the 16-bit Sound Blaster series. Waveblaster MIDI daughterboards will suffer from the hanging notes bug, as will MIDI modules connected through the gameport. However, the passive components on the motherboard that assist in implementing the interface may be missing. Value and OEM cards generally do not have it, although there may be solder points for it. As there are an enormous number and variety of SB16s, I will not try to identify the features of every model. For the system builder, it is extremely difficult to find the right one without doing the homework. But the cards went through many generations and many OEM models. Their basic advance over the Sound Blaster Pro, 16-bit sound, is still the basic standard today. These cards were extremely common from 1992 to the end of the DOS era (1997).
#Sound blaster 16 ct1740 Pc#
No vintage PC product line is more complex than the Sound Blaster 16.