VOGONS


First post, by yukin

User metadata
Rank Newbie
Rank
Newbie

i have a sound blaster 16 model ct2830 running in dos 6.22. i have a problem that is not consistent but when it happen it stay like that for a while. all opl3 sound have no issue at all, the problem is with the digitize sounds. either no sound, low sound, or high scratching static noise. i had the problem once for a week then it just stop and work perfectly for a few days then it start again. is there something related to the hardware that need to be check to fix it? thanks

Reply 1 of 11, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

Do you have leaky caps on your mainboard?

Reply 2 of 11, by yukin

User metadata
Rank Newbie
Rank
Newbie

not a single visible leaky cap from what i see

Reply 3 of 11, by MagefromAntares

User metadata
Rank Member
Rank
Member

Hi,

I assume that you have checked for leaky caps on the card also not just only the motherboard.

There are some other things that can be checked according to the symptoms:
1. Bad solder joints on the components related to digital output on the card, making intermittent connection(Explaining why the sound goes from non-existent to distorted to actually working good. Checking every solder joint is a bit of pain though.)
2. Maybe an overheating issue, compare the temperature of the card's main ICs when the issue happens and when it doesn't, you can either use a remote thermometer or an IR camera to do that when the computer case is opened.

Less probable causes:
1. Bad connection with the ISA slot. (Unlikely, as that would most likely also effect the OPL3 voices too)
2. DMA transfer error from the motherboard. (Unlikely as that would explain the no sound, and in some cases the high scratching static noise, but not the low sound scenario)

"A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it." - Dune

Reply 4 of 11, by Lostdotfish

User metadata
Rank Member
Rank
Member

What speed processor are you running?

Reply 5 of 11, by yukin

User metadata
Rank Newbie
Rank
Newbie

high and low dma are both set to 1.
my cpu is a pentium mmx 166mhz.

will check the states of the solder joints.

Reply 6 of 11, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

High and low dma cannot both be 1.

Traditionally, low dma is 0 or 1, high dma is 3, 5, or 7.

Reply 7 of 11, by jh80

User metadata
Rank Newbie
Rank
Newbie

Yeah, if you have both high and low dma set the same and you try to run a game that utilizes both, you could get the problems you're describing. That might also be why the problem only appears sometimes.

Reply 8 of 11, by NeoG_

User metadata
Rank Oldbie
Rank
Oldbie
jh80 wrote on Yesterday, 00:29:

Yeah, if you have both high and low dma set the same and you try to run a game that utilizes both, you could get the problems you're describing. That might also be why the problem only appears sometimes.

Based on findings for the PicoGUS which uses the same DMA for low and high, it works for pretty much every game without issues and is a valid configuration - Also used officially with the Vibra 16XV. It's also recommended for other SB16 cards if you have an unstable 16-bit DMA controller.

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 9 of 11, by jh80

User metadata
Rank Newbie
Rank
Newbie
NeoG_ wrote on Yesterday, 00:33:
jh80 wrote on Yesterday, 00:29:

Yeah, if you have both high and low dma set the same and you try to run a game that utilizes both, you could get the problems you're describing. That might also be why the problem only appears sometimes.

Based on findings for the PicoGUS which uses the same DMA for low and high, it works for pretty much every game without issues and is a valid configuration - Also used officially with the Vibra 16XV. It's also recommended for other SB16 cards if you have an unstable 16-bit DMA controller.

As I recall, I had a problem with the patch for Crusader: No Remorse that improves SB16 support when I had DMA high and low set the same. That manifested as static-y sound possibly like the OP is describing. Using high DMA fixed the problem. There are probably more instances like that, but perhaps they are very rare, in which case it seems unlikely the OP is encountering them that often.

Reply 10 of 11, by drosse1meyer

User metadata
Rank Member
Rank
Member

I have a similar problem with a 2230... OPL is good, but absolutely no digitized sounds. Swapped with another 2230, works fine. The 'bad' card is recognized and init properly by unisound and Creative tools. I can see the wave levels responding when I play a sound in Windows too.

Is this possibly a bad op amp?

P1: Packard Bell - 233 MMX, Voodoo1, 64 MB, ALS100+
P2-V2: Dell Dimension - 400 Mhz, Voodoo2, 256 MB
P!!! Custom: 1 Ghz, GeForce2 Pro/64MB, 384 MB

Reply 11 of 11, by MagefromAntares

User metadata
Rank Member
Rank
Member
drosse1meyer wrote on Today, 16:16:

I have a similar problem with a 2230... OPL is good, but absolutely no digitized sounds. Swapped with another 2230, works fine. The 'bad' card is recognized and init properly by unisound and Creative tools. I can see the wave levels responding when I play a sound in Windows too.

Is this possibly a bad op amp?

I think on the 2230 the amplifier chip (Usually a TEA or UTC 2025 chip) is not used for mixing the digital channels, but to set the volume levels for the two stereo channels before the output after already mixing with the OPL sounds, so if that would cause the issue then most likely OPL would be affected too. If the wave level meter in Windows responds properly to digitized sounds then I would consider the most likely chips to affect it to be the ADC/DAC chip(Unfortunately a lot of different types were used on the CT2230 based on availability, so I cannot say an exact chip label) or the CT1745A stereo mixer. These are only the most likely causes, a lot of thing can go wrong with a Sound Blaster 16, also if haven't already check for bulging/leaking caps on the card, those can cause weird issues, however a complete loss of digitized sounds would be unusual.

"A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it." - Dune