Have you used the CTCU, the dos utility to assign the resources to these cards?

Malik wrote:

Have you used the CTCU, the dos utility to assign the resources to these cards?

Of course

I only removed my GUS PnP and packed it away this morning, but it was working in a dual boot 95/Dos 5.02 system with an SB Pro 2. The files were a bit of a mess because Win 95 and DOS were on different hd's and I changed the bios settings when rebooting to a different OS. And the GUS software was a hassle to setup and I ended up with things cross-referenced [C: and D: mixed up].

However, here is what I think I had in my working GUS PnP configuration:

autoexec.bat contains:

@SET ULTRADIR=C:\ULTRASND
@C:\ULTRASND\ULTRINIT.EXE -dj

SET INTERWAVE=C:\GRAVIS\ULTRASND\IW.INI
SET IWDIR = C:\GRAVIS\ULTRASND

PATH= ... C:\ULTRASND; C:\GRAVIS\ULTRASND

I have a feeling the first two lines above were left over from an GUS ACE install.

config.sys contains:

device=C:\GRAVIS\ULTRANSD\IWINIT.EXE id=GRV00001
INTERWAVE=C:\GRAVIS\ULTRASND\IW.INI

IW.INI contains amongst a lot else:

[vendor grav_org]
default.fff=c:\ultrasnd\midi\

For sound in heretic I also need to type:

SET ULTRASND=220,5,7,11,5

Maybe not all this is relevant [as it may relate to other things I was trying, and not be necessary] but it might help you work out what you need to do.

If you have no joy with this I'll dig out my PnP and test it again.

🤣

Edit: Also noticed my Heretic is setup up for Gravis as sound card but General MIDI @330 for music.

rumbadumba wrote:

I only removed my GUS PnP and packed it away this morning, but it was working in a dual boot 95/Dos 5.02 system with an SB Pro 2 […]
Show full quote

I only removed my GUS PnP and packed it away this morning, but it was working in a dual boot 95/Dos 5.02 system with an SB Pro 2. The files were a bit of a mess because Win 95 and DOS were on different hd's and I changed the bios settings when rebooting to a different OS. And the GUS software was a hassle to setup and I ended up with things cross-referenced [C: and D: mixed up].

However, here is what I think I had in my working GUS PnP configuration:

autoexec.bat contains:

@SET ULTRADIR=C:\ULTRASND
@C:\ULTRASND\ULTRINIT.EXE -dj

SET INTERWAVE=C:\GRAVIS\ULTRASND\IW.INI
SET IWDIR = C:\GRAVIS\ULTRASND

PATH= ... C:\ULTRASND; C:\GRAVIS\ULTRASND

I have a feeling the first two lines above were left over from an GUS ACE install.

config.sys contains:

device=C:\GRAVIS\ULTRANSD\IWINIT.EXE id=GRV00001
INTERWAVE=C:\GRAVIS\ULTRASND\IW.INI

IW.INI contains amongst a lot else:

[vendor grav_org]
default.fff=c:\ultrasnd\midi\

For sound in heretic I also need to type:

SET ULTRASND=220,5,7,11,5

Maybe not all this is relevant [as it may relate to other things I was trying, and not be necessary] but it might help you work out what you need to do.

If you have no joy with this I'll dig out my PnP and test it again.

🤣

Yes, of course it works alongside other non PnP cards as the Sb Pro
Have another Gus PnP card living next to an AWE32 non PnP, Ensoniq Soundscape, Roland Super MPU

Mine was working fine alongside an EWS64XL [which is plug and play] as well as an SB Pro2.

😀

rumbadumba wrote:

Mine was working fine alongside an EWS64XL [which is plug and play] as well as an SB Pro2.

😀

In a PnP motherboard?

Since Win95 detects the pnp cards, I guess so. Motherboard is a Gigabyte GA-686BX.

Sometimes using iwinit -hunt helps. But sometimes not.

I did go through a period when iwinit couldn't find the card - can't remember what resolved this - it may have been a resource conflict.

GUS PnP v1.0 and AWE64 Gold CT4390 living happily together in one of my PC's. There is MS-DOS 6.22, Windows 98SE and Windows XP installed. Both cards working simultaneously in all three OS'es without any problems.

aleksej wrote:

GUS PnP v1.0 and AWE64 Gold CT4390 living happily together in one of my PC's. There is MS-DOS 6.22, Windows 98SE and Windows XP installed. Both cards working simultaneously in all three OS'es without any problems.

Any chance you can tell how how you got it working? 😀

Here is my SB AWE32 CT3980 + GUS PnP setup:

Note: I've used the "GUS PnP EEPROM tool" (download here) to deactivate any GUS PnP resources except the base I/O address, one IRQ and one DMA. This is not absolutely necessary, but makes the configuration a lot easier.

Relevant CONFIG.SYS entries:
None.

Relevant AUTOEXEC.BAT entries:

1SET BLASTER=A220 I5 D1 H5 P330 E620 T6
2SET CTCM=C:\SB\CTCM
3SET SOUND=C:\SB
4SET INTERWAVE=C:\GUS\IW.INI
5SET IWDIR=C:\GUS
6SET ULTRASND=240,3,3,7,7
7SET ULTRADIR=C:\GUS
8C:\SB\CTCM\CTCM.EXE
9C:\SB\AWEUITL.COM /S
10C:\GUS\IWINIT.EXE

Relevant entries in CTPNP.CFG

1[SB16]
2Disable=0
3Port0=220
4Port1=330
5Port2=388
6Irq0=5
7Dma0=1
8Dma1=5
9
10[IDE]
11Disable=1
12
13[GAMEPORT]
14Disable=0
15Port0=200
16
17[AWE]
18Disable=0
19Port0=620
20Port1=a20
21Port2=e20

Relevant entries in IW.INI

1[setup 0]
2SynthBase=240
3CodecBase=34C
4CDBase=0
5ATAPIBase=0
6MpuBase=0
7AdlibBase=0
8GamePort=0
9IRQ1=7
10IRQ2=7
11CDIRQ=0
12MPUIRQ=0
13SBIRQ=0
14DMA1=3
15DMA2=3
16CDDMA=0

I do not use the GUS PnP under Windows (this opens another can of worms).
The gameport and AdLib port are assigned to the AWE card. Also, I do not use any GUS emulation programs except the MEGAEM MIDI emulation.

EDIT: I forgot the BIOS settings:
PnP OS Installed: No
All PCI IRQs (video, network, USB) assigned manually.
All ISA IRQs/DMAs/Memory blocks set to None/ICU.

Hope this helps...

5u3 wrote:

Here is my SB AWE32 CT3980 + GUS PnP setup: […]
Show full quote

Here is my SB AWE32 CT3980 + GUS PnP setup:

Note: I've used the "GUS PnP EEPROM tool" (download here) to deactivate any GUS PnP resources except the base I/O address, one IRQ and one DMA. This is not absolutely necessary, but makes the configuration a lot easier.

Relevant CONFIG.SYS entries:
None.

Relevant AUTOEXEC.BAT entries:

Copy code to clipboard

1SET BLASTER=A220 I5 D1 H5 P330 E620 T6
2SET CTCM=C:\SB\CTCM
3SET SOUND=C:\SB
4SET INTERWAVE=C:\GUS\IW.INI
5SET IWDIR=C:\GUS
6SET ULTRASND=240,3,3,7,7
7SET ULTRADIR=C:\GUS
8C:\SB\CTCM\CTCM.EXE
9C:\SB\AWEUITL.COM /S
10C:\GUS\IWINIT.EXE

Relevant entries in CTPNP.CFG

Copy code to clipboard

1[SB16]
2Disable=0
3Port0=220
4Port1=330
5Port2=388
6Irq0=5
7Dma0=1
8Dma1=5
9
10[IDE]
11Disable=1
12
13[GAMEPORT]
14Disable=0
15Port0=200
16
17[AWE]
18Disable=0
19Port0=620
20Port1=a20
21Port2=e20

Relevant entries in IW.INI

Copy code to clipboard

1[setup 0]
2SynthBase=240
3CodecBase=34C
4CDBase=0
5ATAPIBase=0
6MpuBase=0
7AdlibBase=0
8GamePort=0
9IRQ1=7
10IRQ2=7
11CDIRQ=0
12MPUIRQ=0
13SBIRQ=0
14DMA1=3
15DMA2=3
16CDDMA=0

I do not use the GUS PnP under Windows (this opens another can of worms).
The gameport and AdLib port are assigned to the AWE card. Also, I do not use any GUS emulation programs except the MEGAEM MIDI emulation.

EDIT: I forgot the BIOS settings:
PnP OS Installed: No
All PCI IRQs (video, network, USB) assigned manually.
All ISA IRQs/DMAs/Memory blocks set to None/ICU.

Hope this helps...

The weird thing is that I've done exactly what you haver done (exact the same resource settings) but the Gus PnP init says it cannot find my card?
Mauybe time to upgrade my 0306 bios version..

Ah, you're trying to get them running on the PVI-486SP3? That's a tough one, because the BIOS is from the days when PnP was only mentioned in connection with selected curse words. 😜

I've found no option to prevent the board from assigning seemingly random resources to ISA-PnP cards when booting, which is very counterproductive when these PnP cards are supposed use certain pre-defined resources.
In theory it should be possible to get both of the cards running by editing the PnP resource profiles stored on the EEPROMs of the cards, but apparently the PVI-486SP3 BIOS ignores these profiles and they always end up being given the wrong resources or no resources at all.
On my P5A board the two PnP sound cards can coexist in peace (after much haggling and negotiating), but on the 486 board I've given up and resorted to non-PnP cards (CT3900 + GUS classic).

5u3 wrote:

Ah, you're trying to get them running on the PVI-486SP3? That's a tough one, because the BIOS is from the days when PnP was only […]
Show full quote

Ah, you're trying to get them running on the PVI-486SP3? That's a tough one, because the BIOS is from the days when PnP was only mentioned in connection with selected curse words. 😜

I've found no option to prevent the board from assigning seemingly random resources to ISA-PnP cards when booting, which is very counterproductive when these PnP cards are supposed use certain pre-defined resources.
In theory it should be possible to get both of the cards running by editing the PnP resource profiles stored on the EEPROMs of the cards, but apparently the PVI-486SP3 BIOS ignores these profiles and they always end up being given the wrong resources or no resources at all.
On my P5A board the two PnP sound cards can coexist in peace (after much haggling and negotiating), but on the 486 board I've given up and resorted to non-PnP cards (CT3900 + GUS classic).

Yeah, I'm trying it on my PV/I 486SP3 mobo....it's like you said in a previous port about it: "it's plug'n'play bios is a joke" 😁

I'm going to stick in a CT2760 or CT3900 instead 😀

Here is my setup:

Ofcource, GUS PnP "emasculated" by IWEEPROM utility. One port (340), one IRQ (11) and two DMA (6,7) - that's what i keep on.

Now, here is relevant fragments of my CONFIG.SYS and AUTOEXEC.BAT files with different sections for different GUS IRQ - 11 or 7 (for stupid games like Duke Nukem 3D and etc. which doesn't work with GUS on IRQ higher than 7).

CONFIG.SYS

1[MENU]
2SUBMENU=GUSIRQ11, Ultrasound on IRQ11
3SUBMENU=GUSIRQ7,  Ultrasound on IRQ7
4MENUDEFAULT=GUSIRQ11,10
5
6[GUSIRQ11]
7blablabla...
8device=c:\ctcm\ctcm.exe
9blablabla....
10
11[GUSIRQ7]
12include=GUSIRQ11
13
14blablabla...

AUTOEXEC.BAT

1blablabla...
2SET PATH=...C:\ULTRASND;C:\AWE32;...
3blablabla...
4REM ========= AWE32 initialization =========
5SET BLASTER=A220 I5 D1 H5 P330 E620 T6
6SET MIDI=SYNTH:1 MAP:E MODE:0
7SET SOUND=C:\AWE32
8SET CTCM=C:\CTCM
9c:\awe32\diagnose.exe /s
10c:\awe32\aweutil.com /s
11c:\awe32\mixerset.exe /p /q
12REM ========= AWE32 initialization =========
13blablabla...
14GOTO %CONFIG%
15
16:GUSIRQ11
17blablabla...
18REM == Ultrasound initialization on IRQ11 ==
19SET INTERWAVE=C:\ULTRASND\IW.INI
20SET IWDIR=C:\ULTRASND
21SET ULTRADIR=C:\ULTRASND
22SET ULTRASND=240,6,7,11,11
23SET ULTRA16=34C,7,11,1,0
24c:\ultrasnd\iwinit.exe
25REM == Ultrasound initialization on IRQ11 ==
26blablabla...
27GOTO DONE
28
29:GUSIRQ7
30blablabla...
31REM == Ultrasound initialization on IRQ7 ==
32SET INTERWAVE=C:\ULTRASND\IWI7.INI
33SET IWDIR=C:\ULTRASND
34SET ULTRADIR=C:\ULTRASND
35SET ULTRASND=240,6,7,7,7
36SET ULTRA16=34C,7,7,1,0
37c:\ultrasnd\iwinit.exe
38REM == Ultrasound initialization on IRQ7 ==
39blablabla...
40GOTO DONE
41
42:DONE
43blablabla...

Now, last section of IW.INI (IWI7.INI)

1[setup 0]
2mode=pnp
3GPusage=IRQ
4revision=B0
5csn=1
6pnprdp=20b
7UseDma=true
8SynthBase=240
9CodecBase=34c
10AdLibBase=0
11GamePort=0
12ATAPIBase=0
13DMA1=6
14DMA2=7
15IRQ1=11
16IRQ2=0
17CDBase=0
18CDIRQ=0
19CDDMA=4
20SBIRQ=0
21SBDMA=1
22MpuBase=0
23MPUIRQ=0
24vendor_id=GRV0001
25effects=on
26winrdp=277
27dosrdp=20b
28config=0
29ptelar=0

Here is only difference - IRQ1 value (11 or 7).

Thats all.

aleksej wrote:

Here is my setup: […]
Show full quote

Here is my setup:

Ofcource, GUS PnP "emasculated" by IWEEPROM utility. One port (340), one IRQ (11) and two DMA (6,7) - that's what i keep on.

Now, here is relevant fragments of my CONFIG.SYS and AUTOEXEC.BAT files with different sections for different GUS IRQ - 11 or 7 (for stupid games like Duke Nukem 3D and etc. which doesn't work with GUS on IRQ higher than 7).

CONFIG.SYS

Copy code to clipboard

1[MENU]
2SUBMENU=GUSIRQ11, Ultrasound on IRQ11
3SUBMENU=GUSIRQ7,  Ultrasound on IRQ7
4MENUDEFAULT=GUSIRQ11,10
5
6[GUSIRQ11]
7blablabla...
8device=c:\ctcm\ctcm.exe
9blablabla....
10
11[GUSIRQ7]
12include=GUSIRQ11
13
14blablabla...

AUTOEXEC.BAT

Copy code to clipboard

1blablabla...
2SET PATH=...C:\ULTRASND;C:\AWE32;...
3blablabla...
4REM ========= AWE32 initialization =========
5SET BLASTER=A220 I5 D1 H5 P330 E620 T6
6SET MIDI=SYNTH:1 MAP:E MODE:0
7SET SOUND=C:\AWE32
8SET CTCM=C:\CTCM
9c:\awe32\diagnose.exe /s
10c:\awe32\aweutil.com /s
11c:\awe32\mixerset.exe /p /q
12REM ========= AWE32 initialization =========
13blablabla...
14GOTO %CONFIG%
15
16:GUSIRQ11
17blablabla...
18REM == Ultrasound initialization on IRQ11 ==
19SET INTERWAVE=C:\ULTRASND\IW.INI
20SET IWDIR=C:\ULTRASND
21SET ULTRADIR=C:\ULTRASND
22SET ULTRASND=240,6,7,11,11
23SET ULTRA16=34C,7,11,1,0
24c:\ultrasnd\iwinit.exe
25REM == Ultrasound initialization on IRQ11 ==
26blablabla...
27GOTO DONE
28
29:GUSIRQ7
30blablabla...
31REM == Ultrasound initialization on IRQ7 ==
32SET INTERWAVE=C:\ULTRASND\IWI7.INI
33SET IWDIR=C:\ULTRASND
34SET ULTRADIR=C:\ULTRASND
35SET ULTRASND=240,6,7,7,7
36SET ULTRA16=34C,7,7,1,0
37c:\ultrasnd\iwinit.exe
38REM == Ultrasound initialization on IRQ7 ==
39blablabla...
40GOTO DONE
41
42:DONE
43blablabla...

Now, last section of IW.INI (IWI7.INI)

Copy code to clipboard

1[setup 0]
2mode=pnp
3GPusage=IRQ
4revision=B0
5csn=1
6pnprdp=20b
7UseDma=true
8SynthBase=240
9CodecBase=34c
10AdLibBase=0
11GamePort=0
12ATAPIBase=0
13DMA1=6
14DMA2=7
15IRQ1=11
16IRQ2=0
17CDBase=0
18CDIRQ=0
19CDDMA=4
20SBIRQ=0
21SBDMA=1
22MpuBase=0
23MPUIRQ=0
24vendor_id=GRV0001
25effects=on
26winrdp=277
27dosrdp=20b
28config=0
29ptelar=0

Here is only difference - IRQ1 value (11 or 7).

Thats all.

Thanks

Might help me if I use the cards in a real PnP system not in my "proto PnP" motherboard Asus PV/I 486SP3 which can only handle one PnP card 😵

Amigaz wrote:

The AWE32 seem to work even though the CTCM spits out some error message but both FM, dig. sound and AWE Midi synth works...

What a happy happenstance. I recently encountered this same issue (Creative CT2940 + GUSPnP).

These errors appear to be the result of CTCM trying to assign resources to the GUS. You'll find that CTCU can even be used to configure the Ultrasound, which shouldn't be possible...

The solution that resolved these issues for me was to upgrade the GUS' EEPROM, using the "Gravis.rom" image found in the P20DISK3.ZIP archive.

Cloudschatze wrote:

What a happy happenstance. I recently encountered this same issue (Creative CT2940 + GUSPnP). […]
Show full quote

Amigaz wrote:

The AWE32 seem to work even though the CTCM spits out some error message but both FM, dig. sound and AWE Midi synth works...

What a happy happenstance. I recently encountered this same issue (Creative CT2940 + GUSPnP).

These errors appear to be the result of CTCM trying to assign resources to the GUS. You'll find that CTCU can even be used to configure the Ultrasound, which shouldn't be possible...

The solution that resolved these issues for me was to upgrade the GUS' EEPROM, using the "Gravis.rom" image found in the P20DISK3.ZIP archive.

Aha! thanks

might try this if I want to throw on the Awe card again in this machine...but right now it sits rotting in te basement of my new appartment

5u3 wrote:

I've found no option to prevent the board from assigning seemingly random resources to ISA-PnP cards when booting, which is very counterproductive when these PnP cards are supposed use certain pre-defined resources.

There is a way, but it's different.

If the BIOS assigns random ressources, simply flush the ressources again (as the PC does on reboot) and then reconfigure it as usual (as if you would had a PnP BIOS with PnP aware OS enabled, thus not configuring any ressources on non-boot relevant ISA cards).
To flush ressources again use the isa-pnptools from linux (the DOS version ofcourse).

There is also a link to an archive that includes the dos compiled binaries:
http://www.roestock.demon.co.uk/isapnptools/