Shouldn't it just work with the regular Sound Blaster 2.0 (CT1350b) driver in Windows. No driver should be needed for DOS I would think.

allready tried no driver only SET BLASTER=A220 I5 D1 T2 not working,
drivers for sb 2.0 under DOS, not working,
sb diag 220 port ok irq5 freezes computer i have DOS only on that computer

Don't be confused by the aztech drivers not detecting the card. The installer is searching that sound galaxy card in particular and doesn't continue if it's not present, it doesn't mean that it can't see any compatible card.

but it quits installer immediately ! any way to install driver? files are packed in *.azt archives... hmm dunno what crazy format it is, unable to unpack

Well then, Lemme pull out one of my BXII cards and install the driver so it will unpack.

thx

I just happen to have BXII drivers - I am uploading them
I kept this fresh installation because it was BS to mess with the weird installer 🤣
hope this works!

keropi wrote on 2021-05-11, 18:45:

I just happen to have BXII drivers - I am uploading them
I kept this fresh installation because it was BS to mess with the weird installer 🤣
hope this works!

just one question - what to add to autoexec and config.sys? lot of executables in /DRIVERS/ directory...

pretty sure AFAIR if you run AZSETUP or SG2 they will make the changes after testing.... it's been too long can't say I remember 100%

Nice.. and I just finished running the installer after having to reformat the CF card I was using because it lost it's mind.

Anyway, the only lines it adds to the Autoexec.bat are:

SET BLASTER=A220 I5 D1 T2
SET SOUND=C:\SGBXII

Nothing gets added to config.sys

So there are no DOS drivers. It should work just like a Sound Blaster 2.0 like I was thinking.

@ Keropi. I don't see why you said it was a weird installer. It was just a normal menu that verified where to install and asked if Windows 3.1 was installed. Then installed from the first disk and asked for the second disk. When it was finished, it ran a sound test and then said to restart the system.

Edit:
AZSETUP is for Windows and SG2 is for DOS.

SG2 test to see if it sees the card, has an FM and SB Sound test, a MIDI port test and an update environment option.

The stuff in the Drivers folder is for specific stuff and nothing needs to be loaded to make the card work.

If your card is still not working, then there is either something wrong with it or something wrong with your computer.

What are the specs of the rest of the system? Is something else using the same IRQ or DMA already?

tested in two different systems 486,32mb ram 128 CF ... -> removed sound blaster (working corectly I5 D1 A220) and tested aztech - so IRQ5 and port 220+ is sure free and with SB was working ... no progress, also same problem, yamaha chip is playing (adlib ...) but digital sound not working i guess 80C51 internal eprom maybe died ?!?

cyclone3d wrote on 2021-05-11, 20:10:

[...]
@ Keropi. I don't see why you said it was a weird installer. It was just a normal menu that verified where to install and asked if Windows 3.1 was installed. Then installed from the first disk and asked for the second disk. When it was finished, it ran a sound test and then said to restart the system.

I just had this mental note that it was weird... maybe I was thinking of something else - it's been a couple of years since I messed with these cards

post some good pics p1p1p1 , maybe there is some visible damage

hmm visible damage 0, checked xtal OK 12.0Mhz, data logger says there are data appearing on input ports from AZTSB0792-U07 so this chip is probably ok, but i cant see any output on way to amp...

Resistor R43 to the left of the crystal looks suspicious. It has definitely been resoldered. I would check it and the traces connecting to it.

There is a blob of solder on top of that resistor as well. Would not surprise me if it is fried.

Try NSSI please. It has a sound card detection routine..

https://www.navsoft.cz/products.htm

keropi wrote on 2021-05-12, 17:35:

I just had this mental note that it was weird... maybe I was thinking of something else - it's been a couple of years since I messed with these cards

And you are correct, I've kept the installation directory too.
For the drivers version taken from Aztech's FTP the installer needs to be run from drive A: and the disk images are for 1.44MB disks (the original box back then had both 3.5" and 5 1/4" DD disks). And then there is actual hardware detection as I wrote earlier in this thread, the installer doesn't just try to find some card that works, it wants to detect specifically that sound galaxy.

So you can't just do the installation on an XT with DD drives, or if your 3.5" drive is not A:, or by copying the disk contents to the hard drive, or by attempting the installation in dosbox to get the files... You need to create floppies, have a PC with a 3.5" HD drive as A: and the card present in it. Too much, better save the installation directory and autoexec entries!

konc wrote on 2021-05-13, 08:36:

And you are correct, I've kept the installation directory too. For the drivers version taken from Aztech's FTP the installer nee […]
Show full quote

keropi wrote on 2021-05-12, 17:35:

I just had this mental note that it was weird... maybe I was thinking of something else - it's been a couple of years since I messed with these cards

And you are correct, I've kept the installation directory too.
For the drivers version taken from Aztech's FTP the installer needs to be run from drive A: and the disk images are for 1.44MB disks (the original box back then had both 3.5" and 5 1/4" DD disks). And then there is actual hardware detection as I wrote earlier in this thread, the installer doesn't just try to find some card that works, it wants to detect specifically that sound galaxy.

So you can't just do the installation on an XT with DD drives, or if your 3.5" drive is not A:, or by copying the disk contents to the hard drive, or by attempting the installation in dosbox to get the files... You need to create floppies, have a PC with a 3.5" HD drive as A: and the card present in it. Too much, better save the installation directory and autoexec entries!

yes exactly!
I now fully remember why I kept the install dir 🤣

Gotcha. I still wouldn't say it is weird though.

That made me think that there was something wrong with the installer itself.

cyclone3d wrote on 2021-05-13, 04:39:

Resistor R43 to the left of the crystal looks suspicious. It has definitely been resoldered. I would check it and the traces connecting to it.

There is a blob of solder on top of that resistor as well. Would not surprise me if it is fried.

nope, resistor is ok, resoldered because of xtal test , impossible to test xtal connected to resistor + MCU
that card has another problem 74123 is half-dead but it is not important, it is handling RESET signal so i desolder it, still it looks like dead 80c51

NSSI cant detect anything 😁 not detected - but atleast MIDI is playing normally, YM3812 is working