does DIAGNOSE.EXE work?

That normally will work from a clean dos boot to test the card.

canthearu wrote:

does DIAGNOSE.EXE work?

That normally will work from a clean dos boot to test the card.

Everything "works" in as much as they output success. Diagnose outputs the BLASTER settings as normal. The only issue I can detect is the lack of output sound, and the fact I can't really set IRQ to anything other than 10 using CTCU.

So diagnose runs, reports success, but NO output to speakers.

If this is the case, there is some fault in the output circuit of the card. Done a good physical inspection of both sides of the cards yet?

you have to set the card to one of “standard” configs
like address 220 or 240, Irq 5 or 7, dMA low 1 or 3, dma high 5 or 7. check other hardware for resources conflicts, may be remove it and check the sound works ok.
then add removed cards one by one checking that sound still works.
if after reinstalling several card sound blaster became speechless, try to reconfigure that card to use another resources.

Cbb wrote:

you have to set the card to one of “standard” configs like address 220 or 240, Irq 5 or 7, dMA low 1 or 3, dma high 5 or 7. che […]
Show full quote

you have to set the card to one of “standard” configs
like address 220 or 240, Irq 5 or 7, dMA low 1 or 3, dma high 5 or 7. check other hardware for resources conflicts, may be remove it and check the sound works ok.
then add removed cards one by one checking that sound still works.
if after reinstalling several card sound blaster became speechless, try to reconfigure that card to use another resources.

I tried it in Win95 using normal settings...220/7/1/5...all the drivers seem happy, everything seems OK...just no sound. Maybe the card is stuffed.

The infamous CT3670 strikes again 😵

Have you tried it under Win 9x or even Win2k/XP? Have you checked threads about reflashing the card into AWE64?

The Serpent Rider wrote:

The infamous CT3670 strikes again 😵

Have you tried it under Win 9x or even Win2k/XP? Have you checked threads about reflashing the card to AWE64?

Yep it sounds like a notorious card. Tried win98 no luck, haven't tried flashing. Don't care if it destroys it, it's going in the bin otherwise.

Try XP.

The flash worked but no change. Tried XP, tried another PC with a working AWE64 and exactly the same. Everything detected, looks like it's fine...but then zero sound coming out. Tried another sound card an immediately worked again. Must be dead.

I'm not familiar with that particular model, but does it have the line/amp jumpers near the outputs? Maybe someone was fiddling with those and disconnected the audio output from the output jacks?

SirNickity wrote:

I'm not familiar with that particular model, but does it have the line/amp jumpers near the outputs? Maybe someone was fiddling with those and disconnected the audio output from the output jacks?

I don't believe so, as it has a line out. It looks like this: http://retronn.de/hwpics/soundblaster_sb32pnp_ct3670.jpg.

It seems like something has been disconnected, I will have a closer look tonight.

Related question: Would there be a reason to re-flash a working CT3670 to an AWE64?

I'm assuming this would allow enable the extra 32 software synth channels in Windows. That isn't really important to me, but is there anything else I'm missing out on?

Tenorman wrote:

Related question: Would there be a reason to re-flash a working CT3670 to an AWE64?

I'm assuming this would allow enable the extra 32 software synth channels in Windows. That isn't really important to me, but is there anything else I'm missing out on?

AWE64 vxd drivers and SF loading in Win98 is probably a good one.

Not sure that I follow. I use Windows Me on the computer I have this card installed and I was able to install the drivers from Creative's site and load sound fonts using the AWE Control Panel. I dual boot and also have Windows 3.1, but haven't tried sound font loading there.