What is the card model?
Did you smell any burning plastic, when you turn it on is a certain component very hot?

My card is the model ct2760.
I have checked out for burned smell as one og the first things. Nothing.
Then i have checked out for unusual heat. Nothing eighter.
Just can't see what is the issue. Fighter dead or something I have missed.

A picture of the patient would probably help.

Uploading in a couple of hours. Away from home 🙁

Have them ready here. Took some close up shots, hope they can help. 😀

It is really dusty.
Take a q-tip and some alcohol and clean the contacts, after that use an rubber eraser and clean the contacts even more.
It looks like nicotine, are you a smoker?

Yeah, I do smoke. Can not be that because I recieved the card for a week ago. It has been in an antistatic bag and inside a closed box until yesterday.
Perhaps the former owner smoke too!! Hmmm.... Have to clean it even more and then use a rubber eraser.

No luck eighter, cleaning the gold contacts. 🙁

Edit:
And no luck cleaning the jumperpins around the card.
I am beginning to get worried that it might be gone forever. 🙁

What does the command "CTCM /t" say exactly, that I/O error you mentioned?
I have one SB16 with an I/O error too.

gerwin wrote:

What does the command "CTCM /t" say exactly, that I/O error you mentioned?
I have one SB16 with an I/O error too.

First the CSP.SYS are loaded in the Config.sys and it reports back that it can not find I/O:
"Error CSPSYS1004: Invalid Base I/O Adress"

Second in the Config.sys, the CTSB16.SYS is being loaded, and it too can not find the I/O:
"Error CTSOUND1008: Invalid "/BLASTER=A:XXX" Argument."

Third the CTMMSYS.SYS are loaded in the Config.sys, wich do not give any error.

All the "SET" commands then runs fine from Autoexec.bat...

The DIAGNOSE /S from within the Autoexec.bat reports back an error:
"Error: DIGN2008 The BLASTER Invironment settings are invalid"

The AWEUTIL /S from within the Autoexec,back gives back an error:
"ERR012: AWE32 Initialization Failed"

I hope this gives a better picture of what is going on....

Was hoping for the "CTCM /t" output. From a safe mode DOS prompt.
And maybe Diagnose without the /S parameter.

Sorry, I have no idea were to make that command. After I have finished loading all in Config.sys and Autoexec.bat.
I tried to find the CTCM folder that came with my SB16-Pro-PNP card. And ran CTCM /t
That made it go into some sort of Windows95 testing mode. I don't know what to do from there.

My AWE32 is the one, were I set the I/O by jumpers, (non pnp i guess it is), and DIAGNOSE can not find it.
Not even the AWE32 dos installers I have tried, can find the card at all possible I/O's that I have selected that way.

Yes, CTCM is supposed say "windows 95 test mode" when using "/t" in Dos 7.
Does it say more? does it give an error?

Nope. No errors at all. When I bypass all Config.sys and Autoexec.bat. The CTCM just runs the same way too.
It is the one from the SB16-Pro-PNP

The CTCM standalone installer does not report anything eighter, and strangely enough, it does not want to go into Win95 mode.
That is the CTCM installer from the "Theman's soundblaster drivers collection disk".

I am not trying this in Windows9X. This is pure MS DOS 6.22 (when I speak of dos, it has nothing to do with Windows) 😉
I have only mentioned that it will not come to life in Windows95 too, wich is installed on the other machine I have tried.

brostenen wrote:

Nope. No errors at all.

It is as if the card is not there!? Even more dead then the two broken SB16s I have stored.
At best OPL3/FM may just work? but I doubt that too.

Yes. Exactly. It is just dead..... Wich I really fear for.
All I did was to play Full throttle, and it all froze up.
The card have been dead since I did a warm-boot/reset-button.

Could be possible that the oscillator or some caps died?

You tried disabling the eeprom jumper right?
It stores its settings there.
Should reset it to default, once disabled and you must use diagnose then.

Seems this model of awe32 just has problems 🤣 , mine makes horrible noise, yours just stopped working...

Nevermind... yours is the model that dosn't have it... despite having the same model number bleh creative, didn't see that till I looked at your pictures closer.

It doesn't show up in Win9x? even when searched for with the hardware utility?

AlphaWing wrote:

You tried disabling the eeprom jumper right? It stores its settings there. Should reset it to default, once disabled and you mus […]
Show full quote

You tried disabling the eeprom jumper right?
It stores its settings there.
Should reset it to default, once disabled and you must use diagnose then.

Seems this model of awe32 just has problems 🤣 , mine makes horrible noise, yours just stopped working...

Nevermind... yours is the model that dosn't have it... despite having the same model number bleh creative, didn't see that till I looked at your pictures closer.

It doesn't show up in Win9x? even when searched for with the hardware utility?

How?
Do i set the jumper to reset, and test? Or what is the procedure? I am kind of new to this.
As I never had anything else than SB16's in the past, nothing as fancy as this. 🤣
(fancy as fancy can be in this case. 🤣)

I remember one friend I had back in 1996. He had an AWE32 and he was bitching about something.
He corrected it, yet I as stupid as one can be, did not pay any attention.
I just decided that AWE32's were not for me, so I ended up with an GUS-ACE and an SB16 Value Edition.

Now for the "fun" part.
What should I exactly do with this eeprom jumper? (scratching-in-my-beard-smiley)