keropi wrote on 2021-09-28, 18:02:

so I am 99,9% sure if you de-activate with eeprom tool all your worries will be gone 😀

All my worries were already gone when I received your card. 😀 Anyway, I deactivated it with the eeprom tool and now it works as I want it to work.

Shame is that now you can't add the P330 string to the BLASTER env before running UNISOUND as that will mute the MIDI output. This comes in handy as some programs/games use this string (like dosmid). But I can add it after running UNISOUND of course.

Yoghoo wrote on 2021-09-28, 18:51:

All my worries were already gone when I received your card. 😀 Anyway, I deactivated it with the eeprom tool and now it works as I want it to work.

Shame is that now you can't add the P330 string to the BLASTER env before running UNISOUND as that will mute the MIDI output. This comes in handy as some programs/games use this string (like dosmid). But I can add it after running UNISOUND of course.

glad to hear all is good again - enjoy the card and thanks for the support! 😀

Hello JazeFox and the rest!

Thanks again for this great utility.

I have a problem.
If I try to use the utility to define two sound cards such as ess and awe64 ct4520,
then the utility does not detect ess (es688f+968f), it only detects awe64 ct4520.
If I pull the awe64 ct4520 out of the motherboard, the utility detects the ess without problems.

I tried the utility for simultaneously determining two sound cards sb16 ct2770 (not pnp) + ess (es688f+968f)
and in this combination both sound cards are detected and there are no problems.

Can anyone help me?
Thank you all in advance!

you likely have a resource conflict, what are your jumpers on the SB16 set to?

Please read again, since sb16 no problem with ess.
the problem is only when initializing awe64 with ess.

Resources are assigned correctly, both awe64 and ess sound cards work well in Windows 98.
awe 240 i5 d0 h5 t6 e640 f398
ess 220 i7 d1 t4 u10(mpu irq) f388

I wonder why unisound allows to configure both high/low DMA for YMF71x chips? 16bit high DMA doesn't seem to work on them (probably not supported). Setupsa doesn't support configuring high DMA at all.

AlexZ wrote on 2021-10-01, 23:41:

I wonder why unisound allows to configure both high/low DMA for YMF71x chips? 16bit high DMA doesn't seem to work on them (probably not supported). Setupsa doesn't support configuring high DMA at all.

The second DMA is likely for WSS which as you guessed it doesn't support high DMA.

AlexZ wrote on 2021-10-01, 23:41:

I wonder why unisound allows to configure both high/low DMA for YMF71x chips? 16bit high DMA doesn't seem to work on them (probably not supported). Setupsa doesn't support configuring high DMA at all.

As with some other chipsets, it isn't really for "high DMA", but rather separate capture and playback 8-bit DMA channels, so that full-duplex operation can be supported. For a DOS gaming environment, this is generally never needed, and you can assign only one channel with no loss of functionality.

hi,

I just want to report to unisound driver problem with Orpheus sound card.
First of all, I really apreciate this driver. It is very intuitive to use. It works with Orpheus sound card with no major problem.

here is my only problem with unisound. I use external Midi modules(Sound Canvas 55mk2) connects to Orpheus sound card by using a dedicated midi port(looks like just stereo jack to Midi port). if I start Doom with general MIDI support it plays no Midi music.. just game sound. With same physical setting Orphinit.exe works and it plays midi music in Doom.
symtom is very weird.. because I can see Midi IN activity LED or signal light is on and blinking, which means Sound canvas 55 receives MIDI signal from orpheus sound card but SC-55 does not produce any Midi Music... just slient.
When I use unisound I use correct blaster environment augments and no other fancy options at all. It initialize orpheus correctly.. as long as I don't use external Midi deivce.
Is this known issue ? or just wrong setting ?

overdriver wrote on 2021-10-14, 04:41:

hi, […]
Show full quote

hi,

I just want to report to unisound driver problem with Orpheus sound card.
First of all, I really apreciate this driver. It is very intuitive to use. It works with Orpheus sound card with no major problem.

here is my only problem with unisound. I use external Midi modules(Sound Canvas 55mk2) connects to Orpheus sound card by using a dedicated midi port(looks like just stereo jack to Midi port). if I start Doom with general MIDI support it plays no Midi music.. just game sound. With same physical setting Orphinit.exe works and it plays midi music in Doom.
symtom is very weird.. because I can see Midi IN activity LED or signal light is on and blinking, which means Sound canvas 55 receives MIDI signal from orpheus sound card but SC-55 does not produce any Midi Music... just slient.
When I use unisound I use correct blaster environment augments and no other fancy options at all. It initialize orpheus correctly.. as long as I don't use external Midi deivce.
Is this known issue ? or just wrong setting ?

Sounds like a mpu port conflict to me, are you sure that unisound does not activate csmpu at port 330 and on the same time pcmidi is at port 330 too?
With stock orpheus.ini for orphinit csmpu is disabled so this could be a clue of what is happening

keropi wrote on 2021-10-14, 05:19:

overdriver wrote on 2021-10-14, 04:41:

hi, […]
Show full quote

hi,

I just want to report to unisound driver problem with Orpheus sound card.
First of all, I really apreciate this driver. It is very intuitive to use. It works with Orpheus sound card with no major problem.

here is my only problem with unisound. I use external Midi modules(Sound Canvas 55mk2) connects to Orpheus sound card by using a dedicated midi port(looks like just stereo jack to Midi port). if I start Doom with general MIDI support it plays no Midi music.. just game sound. With same physical setting Orphinit.exe works and it plays midi music in Doom.
symtom is very weird.. because I can see Midi IN activity LED or signal light is on and blinking, which means Sound canvas 55 receives MIDI signal from orpheus sound card but SC-55 does not produce any Midi Music... just slient.
When I use unisound I use correct blaster environment augments and no other fancy options at all. It initialize orpheus correctly.. as long as I don't use external Midi deivce.
Is this known issue ? or just wrong setting ?

Sounds like a mpu port conflict to me, are you sure that unisound does not activate csmpu at port 330 and on the same time pcmidi is at port 330 too?
With stock orpheus.ini for orphinit csmpu is disabled so this could be a clue of what is happening

OK I didn't know there is a option to turn off CSMPU specifically. I will try that. and I don't think I have ever activated CSMPU unless it is default setting. I will report back once I am done.

Thanks for suggestion!

keropi wrote on 2021-10-14, 05:19:

overdriver wrote on 2021-10-14, 04:41:

hi, […]
Show full quote

hi,

I just want to report to unisound driver problem with Orpheus sound card.
First of all, I really apreciate this driver. It is very intuitive to use. It works with Orpheus sound card with no major problem.

here is my only problem with unisound. I use external Midi modules(Sound Canvas 55mk2) connects to Orpheus sound card by using a dedicated midi port(looks like just stereo jack to Midi port). if I start Doom with general MIDI support it plays no Midi music.. just game sound. With same physical setting Orphinit.exe works and it plays midi music in Doom.
symtom is very weird.. because I can see Midi IN activity LED or signal light is on and blinking, which means Sound canvas 55 receives MIDI signal from orpheus sound card but SC-55 does not produce any Midi Music... just slient.
When I use unisound I use correct blaster environment augments and no other fancy options at all. It initialize orpheus correctly.. as long as I don't use external Midi deivce.
Is this known issue ? or just wrong setting ?

Sounds like a mpu port conflict to me, are you sure that unisound does not activate csmpu at port 330 and on the same time pcmidi is at port 330 too?
With stock orpheus.ini for orphinit csmpu is disabled so this could be a clue of what is happening

OK, now it is working MIDI music with unisound!
All I did was add 'Blaster= P0' to disable Midiport address(of Crystal chipset). It was suggested by my friend in different internet forum. other Unisound extra setting for Orpheus sound card is only to enable Crystal MPU but there is No disable function.. unless you put port address '0' to 'Blaster=' parameter. I thought it disable Crystal MPU by default but extra setting in 'blaster=' does that for sure.
so my blaster setting is 'Blaster= A220 I5 D1 H4 P0'

I'd like to thank you Keropi and other friend to point it out. thanks~!

overdriver wrote on 2021-10-15, 16:46:

OK, now it is working MIDI music with unisound! All I did was add 'Blaster= P0' to disable Midiport address(of Crystal chip […]
Show full quote

OK, now it is working MIDI music with unisound!
All I did was add 'Blaster= P0' to disable Midiport address(of Crystal chipset). It was suggested by my friend in different internet forum. other Unisound extra setting for Orpheus sound card is only to enable Crystal MPU but there is No disable function.. unless you put port address '0' to 'Blaster=' parameter. I thought it disable Crystal MPU by default but extra setting in 'blaster=' does that for sure.
so my blaster setting is 'Blaster= A220 I5 D1 H4 P0'

I'd like to thank you Keropi and other friend to point it out. thanks~!

yep, that is the setting to disable CSMPU with unisound... you can also use the eeprom config tool on Oprheus website, selecting option 3 will disable CSMPU in eeprom and you won't have to use P0
or you can have it active at port 300 so there are no conflicts with pcmidi

keropi wrote on 2021-10-15, 17:01:

overdriver wrote on 2021-10-15, 16:46:

OK, now it is working MIDI music with unisound! All I did was add 'Blaster= P0' to disable Midiport address(of Crystal chip […]
Show full quote

OK, now it is working MIDI music with unisound!
All I did was add 'Blaster= P0' to disable Midiport address(of Crystal chipset). It was suggested by my friend in different internet forum. other Unisound extra setting for Orpheus sound card is only to enable Crystal MPU but there is No disable function.. unless you put port address '0' to 'Blaster=' parameter. I thought it disable Crystal MPU by default but extra setting in 'blaster=' does that for sure.
so my blaster setting is 'Blaster= A220 I5 D1 H4 P0'

I'd like to thank you Keropi and other friend to point it out. thanks~!

yep, that is the setting to disable CSMPU with unisound... you can also use the eeprom config tool on Oprheus website, selecting option 3 will disable CSMPU in eeprom and you won't have to use P0
or you can have it active at port 300 so there are no conflicts with pcmidi

Well, TIL that's what I've been doing wrong with UNISOUND. Thought something was up with the driver when I swapped to ORPHINIT and things just worked.

Just wanted to pop in and say thanks, this tool works great with my AWE32/SB32 and AWE64.

IT does not work with ISA sound card labeled as K2Y-PRO 16 with ADJ1846JP soundPort chip, OPTI 82C929A chip and Yamaha 262 chip,

Error: sound card not detected

This is not a Plug & Play chip, 82C931 is the first OPTi chip that adds it.

goethe wrote on 2021-10-24, 20:36:

IT does not work with ISA sound card labeled as K2Y-PRO 16 with ADJ1846JP soundPort chip, OPTI 82C929A chip and Yamaha 262 chip,

Error: sound card not detected

For 82C929 use these drivers instead: https://github.com/JKnipperts/OPTi82c929_Driver

Hello everyone to this forum .
I wrote a small pnp card initializer for the TOS/GEM environment (Atari ST). I am trying to find information on the use of SoundBlaster cards, can someone help me with a link on how to detect these cards without pnp-BIOS. I suppose they have their own initiation sequence different from the PnP standard.
Thank you in advance for your help 😉

well non pnp dont really have an init sequence per se, just when you use them you issue some hardware resets to the IO space.