Viserion wrote:

does anybody knows what jumpers should be set out without extra ram.

This is a scan from the manual that came with my AWE32.
The DRAM_EN jumper under the RAM slots on the card is what tells the card whether to use RAM added to the slots or not.

Thanks, will try it out.

The fact that neither DOS or Windows 9x detects the card is a bit worrying and, since this is a Plug 'n Play card, Windows 98 should detect it straight away when you boot up the first time.
Have you tried uninstalling all your previous drivers to see whether Windows detects the card again?
Sometimes a card can be obstructed by the bracket (when you plug it into the ISA slot) - what I sometimes do is to slightly bend the lower end of the bracket to ensure that the card goes completely into the ISA slot.

PS: U17 is sometimes populated with the CT1748-SBP chip, which is the Advanced Signal Processor (ASP), also known as the Creative Signal Processor (CSP). It was used by very few applications and is not really required.

Then I at least know it's not reqired.

It is worringly that it's not detected anywhere.
Not tried to uninstall any drivers, had a strange ESS 1868 card before(it has a 6/9V power input via the bracket for some reason).

I try if I can get it going in another system, that is a bit nonstandard to say the least.

It should however be detected in Dos, as that is a brand new installation.

Under DOS you require at least CTCM to be loaded. CTCU is only required for DOS 6.22 or earlier, since with later DOS versions (that came with Windows 9x) CTCM just read a configuration file called ctpnp.cfg under the Windows folder.

Viserion wrote:

Not tried to uninstall any drivers, had a strange ESS 1868 card before(it has a 6/9V power input via the bracket for some reason).

That's not strange. It's power output and was meant for active speakers, saving an additional PSU.

Tried a lot of different things, and nearly changed or took outalmost all of the hardware to see if there was a conflict, with no results.

This was in dos however. Tried to run diagnose or install, but either go a flat out not detected, or failed the I/O detection.
Tried 220h, 240h, 260h and 280h plus auto detect, but all failed.

Never thought about out put, I guess that would have been somewhat useful back in the day.

Any other jumpers I could try?

As that is the only idea I can think of at this point.

Did get the 2x16mb 30 pin simms today, but made no difference.

it should at least show up in post as a PNP card, much like your AWE64 does. In fact in Win9x it should behave the same as the AWE 64
It's sounding more and more like a dead card 🙁

jesolo wrote:

Under DOS you require at least CTCM to be loaded. CTCU is only required for DOS 6.22 or earlier, since with later DOS versions (that came with Windows 9x) CTCM just read a configuration file called ctpnp.cfg under the Windows folder.

/\ THIS /\

When installing my 2MB CT3600 (as AWE 32) PNP card I had to load this before the install program detected the card. Once I did that- everything when smooth and installed flawlessly. This was a DOS / Win 3.11 machine so it may not translate to your situation.

I ordered a CPU(P200MMX) that arrived today to test this card on a second system.
Could not get the CPU to work on either the second or first system, though the first system does boot when reinstalling the K6-2+.

Second MB(M5ALA) is not a super socket 7, so doesa not support K6-2+ CPU.

Seller of the AWE32 has found another card that is tested working, so I retun this card and hope to get a working card in return.

When looking at it the AWE32 is sligthley bent towards the middle, so this migt be the cause for the failure.

Sent the card back, and seller bent som pins back, and sent the same card back.
Not sure which pins however.

Tested it, and there is still problems with it.

In Win2k it was horrible broken as it was stuttering so bad that whatever was played was unrecognizeable.
It would BSOD after a short while.

I reinstalled Win2k first with other card(Audican 32 pro), and later with the AWE32.
First card worked flawlessly, the AWE32 was better. MP3s can be played, but any game running for a little while will cause it to BSOD.
Used inbuilt drivers, as I can't find Win2k drivers for the AWE32.

In Win98 using Creative drivers, and it works a lot better than in win2k. The 2*16mb sticks are detected, and all appears to work well.
I could load soundfonts, and play the piano in the Creative program suite.
However any game will crash after a little while.There are also noise that should not be there.
MP3s will play fine however.

In Dos I tried doom2, and it would not detect it as AWE32, buit if I chose general Soundblaster card it would work, but unstable as sometime sound effects would work others not.
Music will not work in AWE32 mode, but sometimes in Soundblaster mode.
When running diagnose I get an error that says "The hardware chip required for Advance WaveEffects Synthesis is found to be missing or faulty", and in aweutil I get "ERR012 : AWE32 initialization failed".
I am using drivers from Creative in dos, downloaded from here,

It baffles me that it works better in Win98 than in either Dos or Win2k.
So far if I have understood everything the soundfonts should not be working in Win98 if the chip is faulty, but it won't work in Dos or Win2k.

I simply can't figure this one out.