On 22 Jun, 17:51, "Gary S. Terhune" none wrote:
"rpgs rock dvds" wrote in ...

The driver package for this card installs an unwanted legacy audio
device inside Device Manager. *It also adds a "SET BLASTER" line
inside autoexec.bat, which "cancels out" my own SET BLASTER line for
my real SoundBlaster card.

What do you mean your "real Soundblaster card"? If you 've already got your
"real" card in there, why are you installing another driver package for it?
Or do you have TWO Soundblaster cards? What's the difference between the two
Autoexec.bat lines. How does each one read? I peresume they're different?

If I remove the unwanted SET BLASTER line, the legacy audio device
simply adds it back in after a reboot.

Yes, it would do that. Why would you need the SET BLASTER line in
Autoexec.bat if you arne't loading any DOS drivers for the card?

If I remove the legacy audio device from Device Manager (by removing
it from my specific hardware configuration profile), what happens is
that after any reboot, I find that my own specific SET BLASTER line
gets removed!

I would expect that, also.

Now that the legacy audio device has been removed from my specific
hardware configuration profile, how can I stop it continuing to meddle
with my autoexec.bat file?

If the legacy SB device is removed, there shouldn't be any need for any
commands relating to it to be found ANYWHERE, including not in Autoexec.bat.
Why would you think otherwise?

Any thoughts gratefully received. *Thank you. *Best regards, Robert..

Answers to questioned that have been asked would be greatly appreciciated..
You either have a wrong idea about that line (and any others) in
Autoexec.bat or you really are trying to install two SB cards. You got me
curious as all get out. Are you really installing two sound cards?

--
Gary S. Terhune
MS-MVP Shell/Userhttp://grystmill.com

I will rephrase my OP in order to answer your queries -

My PC has the following two physical sound cards in it -

1) An ISA-based (non Plug and Play) AWE32 card.
2) A PCI-based Ensoniq PCIAudio ES1371 (which uses Creative drivers).

I installed the AWE32 first, for DOS usage. (I decided at this stage
not to ask Win98SE to search for any new hardware.)

Secondly, I inserted the ES card, and the Windows98 Creative driver
package was then duly installed. This driver package not only
installed the Windows driver for the ES card, but it also installed
another device which was called a "legacy audio device" for old DOS
games. I then asked Windows98 to add new hardware, in order to add in
the AWE32 card. It did this fine without any problems.

The problem is this: I really don't need the ES legacy audio device,
because what this legacy device does is add in its own SET BLASTER
line to the autoexec.bat file, which is as follows -

SET BLASTER A220 I5 D1 T4

This "overrides" my specific AWE32 SET BLASTER line, which is -

SET BLASTER A220 I7 D1 H5 P300 E620 T6

If I remove the ES legacy SET BLASTER line, after a reboot, this line
just gets added back in to the autoexec.bat file. If I either remove
or disable the legacy audio device, it not only removes its own SET
BLASTER line (which it should do), but crucially it unintelligently
also removes *my own* SET BLASTER line which I want to use for my
"real soundblaster", ie my AWE32 card.

To summarise: after either removing or disabling the unwanted ES
legacy audio device, I am finding that my own specific SET BLASTER
line which I want for my AWE32 card is *always* being removed from the
autoexec.bat file. It is like the legacy audio device is still
meddling with my autoexec.bat file, even though I have tried either
disabling it or I have also removed it from my current specific
hardware configuration profile. (In other words I've tried both
approaches - either disabling the legacy device, and I've also tried
removing it --- in both cases, Device Manager tells me that they are
either disabled or gone from my current hardware profile.)