Disable the PnP part on your system BIOS. Then, the ICU will be able to
set the card up properly. Once the BIOS has done the setup, nothing
else can change it.
Mike
Your getting these problems because of dos4GW: it does not suport
high-irq. Try replacing dos4gw with pmodew 1.22, it can be found as
pmw122.zip on several public archives like FTP.CDROM.COM. It's better,
faster and a hell of a lot shorter!!!
Yeah, I am well aware of DOS/4GW's limitations as far as upper IRQs are
concerned: I have been a happy GUSser for quite a while now, and have
experienced all of these problems :)
This is not the answer to my problem :(
Unless I re-bind all of my DOS/4GW games/programs/everything with PMode
[I have done it to DOOM for a laugh :)]. Would be interesting trying to
re-bind an executable on a CDROM :)
PMode is good for what it does. It does not handle the exceptions that
DOS/4GW does (hence making it faster). And it is slower to initialise
than DOS/4GW. And apparently (I've just heard, but haven't checked
myself) it takes up more real-mode memory _when running_ than DOS/4GW.
Yes, the stub is smaller than the DOS/4GW run-time executable.
And most of my DOS/4GW programs work okay on IRQ11: DOOM, Descent, our
demo (MIDAS and DOS/4GW). But some refuse: Duke Nukem 3D won't even run
if your GUS is on an IRQ above 7, so changing that to PMode will have no
effect.
Lewis-PF / G.P.F.
I can't disable the PnP part of my BIOS :(
And are you sure about the thing about after the BIOS setting up the
card, nothing else can touch it?
I have managed to move the card's DMA channels from within the Intel
ICU, which would have made the changes after the BIOS had setup the
card.
I don't think that PnP is a one-off thing during a boot. Anything can
change it afterwards. You just need to talk to the card via the ISA PnP
port, or something. Isolate the card, and set it up.
Win95 reconfigures cards after the BIOS has set them up.
Lewis-PF / G.P.F.
at least i can help you with the cp problem:
a) use pmode/w as a dos extender or
b) use system timer and use slow upload (see CP.INI for more info)
cu
Niklas
My experiance is that it does not always work (like with
System Shock, CDSHOCK.EXE and SSHOCK.EXE).
Prepgame is supposed to fix the high Irq problem as well, but if the
PMODE works, I usually go with it.
//Fockerman
I have my GUS on irq15, and it works fine. Duke3d doesn't work for me
either, but if you set it for sound blaster with general midi, and use
megaem, it runs perfectly. The sound is great too. Interestingly, I
HAVE to do that with ROTT, cause when I select ultrasound, it barfs up.
Beats me why. Bad driver programming. Anyways, cubic player also works
fine for me. Maybe your environment variables are inconsistent with the
new setup? As for win95, can't you force the driver to use irq7? ie:
don't use the scroll arrow to select the irq, but type it in yourself,
and ignore the error message. I haven't done this myself, so I have no
idea what will happen.
--
---
Now that I've given up hope, I'm feeling much better.
: I can't disable the PnP part of my BIOS :(
: And are you sure about the thing about after the BIOS setting up the
: card, nothing else can touch it?
Hmmm... I don't buy that myself, but then again my machine ain't PnP...
To have anything changed (hell, to initialize the card so that at least
the baseport is at 0x0220) I simply left the settings I wanted in
IWINIT.EXE, and made sure it's in my Autoexec.bat.
Then, to make sure Win95 doesn't trash the IW.INI file, I commented out
the "run=?:\ultrapnp\setultra.exe" file in the WIN.INI.
Win95 doesn't like to believe that the DMA channels can be changed, but
I've been able to alter everything else (baseports, IRQs) from within
Win95. The Win95 driver itself re-initializes the card to the Windows
registry settings, so it doesn't really matter at that point what my
IW.INI has in it.
--
Just another lamer in the soup,
Lance Kalzus
kalzus@[128.122.230.28]
>I changed my motherboard the other day, and it screwed my settings on my
>GUS PnP :(
>I had had it configured on IRQ7 in DOS, but my new PnP BIOS decided to
>move it to IRQ11.
Why don't you edit your autoexec.bat GUS initialization section
yourself. I'm not sure which number is which, but mess around w/ the
"SET ULTRASND=220,7,7,5,5" section.
Lora
I'm afraid I've tried that :(
IWINIT doesn't seem to do anything with this. The settings are just the
same, regardless of what the ULTRASND variable is set to.
IWINIT should take its settings from the IW.INI file, but it seems to
ignore that too.
And my settings are all consistent with the settings I want (ie IW.INI
and ULTRASND are all set to what I want), yet the card is still
configured differently. So says IWINIT -v9.
I have to set my ULTRASND variable to the settings that the card is
configured to, however, otherwise some software would work (that uses
the ULTRASND variable to get the GUS settings).
Oh well, Duke3D is currently resigned to the bin. It won't even work on
my SB16, claiming there is a conflict when I know damn well there isn't.
All other software works on my SB16, except Duke3D. Hmmmm.
I think my problem lies in telling the PnP part of my BIOS what settings
to set the GUS PnP to. Does anyone know how to do this??? I have checked
my BIOS settings (AWARD Pentium BIOS) and there is no a single option
about ISA PnP. I have even tried MR BIOS replacement, but that doesn't
have any settings either.
And I have got Cubic Player working via PMode (thanks Pascal), both
v1.666 and now v1.7. When can we expect full InterWave support?? :)
Lewis-PF / G.P.F.
> From: kalzus@[128.122.230.28] (Lance Kalzus)
> Newsgroups: comp.sys.ibm.pc.soundcard.tech
> Subject: Re: GUS PnP and IRQ7
> Date: 29 Mar 1996 00:39:53 GMT
> Organization: Pyros
> Lines: 29
> Distribution: world
> Message-ID: <4jfbgp$r...@news.nyu.edu>
> References: <aYRaLGAt...@dial.pipex.com> <9cr73EABDvVxEwDy@dial.p
ipex.com>
I can't get my news server to give me the posting. Keeps coming up
unavailable :(
Thanks,
Lewis-PF / G.P.F.
HAPPY DAYS ARE HERE AGAIN!!!!!
YES! YES! YES! YES!
Phewww, I feel much better now :)
Right, here goes an explanation.
Gravis just released a patch for the GUS PnP, in the form of an updated
EEPROM data file, and a program to load it into the GUS PnP.
Well, I loaded it, hoping that it would make IRQ7 a valid choice for the
Wave & Codec unit .... but it didn't :( Bad news.
But I had inspiration: I had now all the tools I needed to manually
reconfigure the GUS PnP. I had a file as a basis and a program to upload
the file to the GUS PnP.
So I studied the data file, and learnt what all the bytes were (well,
most of them. Enough to do what I wanted).
So I reconfigured one of the PnP settups, allowing IRQ5 & IRQ7 as valid
choices. Unfortunately, my BIOS refused to select these itself, and
Win95 locked up when I tried to manually select them myself :(
So I then took the sledgehammer approach :)
I reconfigured every single setup to only allow IRQ7, DMA 6&7, and I/O
240 (34C). And it worked !!!!!
I needed to use the Intel ICU to actually select the settings (my BIOS
just kept the old settings), and then Win95 immeadiately picked up the
same settings!
Amazing. I can now play Duke Nukem 3D again.
With semi-thanks to Gravis, who un-knowingly helped me.
Why oh why IRQ7 is not a valid selection for the Wave & Codec I do not
know. These means it cannot be totally GUS compatible, since a GUS can
easily be programmed to IRQ7. Duke Nukem 3D requires the GUS on IRQ7 or
less, so the PnP fails in this respect.
Well, I'm a happy bunny now :)
Lewis-PF / G.P.F.
> I'VE DONE IT !!!!!!!!!
>HAPPY DAYS ARE HERE AGAIN!!!!!
>YES! YES! YES! YES!
>Phewww, I feel much better now :)
Hey, that's great to hear that you figured out the problem!
Now can you tell the rest of us exactly what we need to do in order to
solve it as well? I'm expecting my GUS PnP to arrive this week and I
was hoping to be able to configure it for IRQ 3 (no, I'm not using
COM2:, and yes, I have disabled it).
Congrats and thanks for the help!
Ian