Ensoniq Creative AudioPCI sound card autoexec.bat woes

[Guest rpgs rock dvds]

Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes

 

On 24 Jun, 03:27, "MEB" <meb@not h...@hotmail.com> wrote:

> Okay, downloaded that standalone driver, will look at it shortly. It appears

> it may be just an *update* for an already installed driver sethttp://www.soundcard-drivers.com/drivers/262/262924.htm.

>  If it is, then it isn't what you need as other support files are missing.

> Look at the offered drivers there - use *more* to see information for the

> driver.

>  You can also go directly to driverguide.com, signup, and search there.

>

>  As I had indicated, using more than one SoundBlaster will cause additional

> issues... you said you had some other cards to play with,, why not use a

> Blaster and another manufacturer's card...

>

> RE: blue screen

>  Make sure you have NO old INFs from prior installation attempts...

> Since your intending a clean install, get TOTAL UNINSTALLER [TUN] and use it

> before installing the cards and drivers. It will allow complete removal. Do

> one at a time, WITH restarts, and export/save text of monitored

> installations for later reference.http://www.aplusfreeware.com/categories/util/uninst.html

>

>  The cards should have a model and/or ID number on them.. better look,,

>  Sound Blaster 16 PCI Digital Sound card. Model CT4730. OEMhttp://www.soundcard-drivers.com/companies/258.htm

>

> *IF* using two Blasters, configure the PnP card First, BEFORE *disabling*

> Dos emulation, shut down, re-start, check that it remains disabled. Then

> install the second.  Try manually changing the Awe32 jumpers to

> non-conflicting addresses and IRQs BEFORE installing it or the driver..

> should be a manual setup screen after software installation, make sure you

> use the manual settings you set there or in Device Manager. *Disable*

> Awe32's DOS emulation. Re-start to Command Prompt Only, delete

> %windir%\win386.swp, check the autoexecs for lines,  restart to Normal and

> re-enable the PnP ESS Dos emulation. Restart, and check that everything is

> set properly... only then try to test the cards....

>

>  See prior postings related to this conflict and setup, autoexec, etc...

>

> --

>  MEB

>  http://peoplescounsel.orgfree.com

 

Solution found!

 

I wanted to test out my "new" es1373-based chipset audio card, as

opposed to the one I had been using the other day, which was based

around the es1371 chipset. The new card model for testing is called

CT4740.

 

I did these 4 tasks -

 

1) Installed standalone driver package called SBAudioSetup_W9x.zip

from the Creative website.

 

After installing, I went to Device Manager and selected Properties for

the newly installed audio device. Inside this properties section, I

unchecked the legacy emulation option. After a few reboots, I then

did -

 

2) Added a SET BLASTER=... line to my autoexec.bat (I purposefully

didn't bother to physically add an old ISA-based SoundBlaster to my

machine - I figured that by simply adding a SET BLASTER line to the

autoexec.bat file was sufficient for my first round testing purposes.)

 

After a reboot, I noticed that even though the Legacy audio device had

been completely removed from Device Manager, my newly added SET

BLASTER had also been removed from autoexec.bat!

 

So I then did -

 

3) Installed the SBPCI_WebDrvsV5_12_01.exe package. This "upgrades"

the CT4740 audio device to use WDM drivers, which I think is the key

to solving this problem. After this installation was complete, I

noticed that all references inside Device Manager for Legacy audio

device were gone.

 

So I then re-added my SET BLASTER line to the autoexec.bat file,

rebooted, and then noticed that the SET BLASTER line remained

untouched - it hadn't been deleted.

 

Just to finish things off I did -

 

4) Installed the audio device apps, called capp_setupus.exe (along

with the 4 .LIB files)

 

Just to finalise testing, I then added in an old ISA-based SB16,

installed this device inside Windows 98SE using the drivers from the

Win98SE disc, and did some dxdiag sound and music testing on both

audio devices - all tests were OK. I also rebooted a couple of times,

and my SET BLASTER line still remained untouched.

[Guest MEB]

Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes

 

Sounds good [pun intended], thanks for posting back...

 

--

MEB

http://peoplescounsel.orgfree.com

--

_________

 

"rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message

news:3b685a89-cd2e-4a70-bff7-7dd353977207@z72g2000hsb.googlegroups.com...

On 24 Jun, 03:27, "MEB" <meb@not h...@hotmail.com> wrote:

> Okay, downloaded that standalone driver, will look at it shortly. It

appears

> it may be just an *update* for an already installed driver

sethttp://www.soundcard-drivers.com/drivers/262/262924.htm.

> If it is, then it isn't what you need as other support files are missing.

> Look at the offered drivers there - use *more* to see information for the

> driver.

> You can also go directly to driverguide.com, signup, and search there.

>

> As I had indicated, using more than one SoundBlaster will cause additional

> issues... you said you had some other cards to play with,, why not use a

> Blaster and another manufacturer's card...

>

> RE: blue screen

> Make sure you have NO old INFs from prior installation attempts...

> Since your intending a clean install, get TOTAL UNINSTALLER [TUN] and use

it

> before installing the cards and drivers. It will allow complete removal.

Do

> one at a time, WITH restarts, and export/save text of monitored

> installations for later

reference.http://www.aplusfreeware.com/categories/util/uninst.html

>

> The cards should have a model and/or ID number on them.. better look,,

> Sound Blaster 16 PCI Digital Sound card. Model CT4730.

OEMhttp://www.soundcard-drivers.com/companies/258.htm

>

> *IF* using two Blasters, configure the PnP card First, BEFORE *disabling*

> Dos emulation, shut down, re-start, check that it remains disabled. Then

> install the second. Try manually changing the Awe32 jumpers to

> non-conflicting addresses and IRQs BEFORE installing it or the driver..

> should be a manual setup screen after software installation, make sure you

> use the manual settings you set there or in Device Manager. *Disable*

> Awe32's DOS emulation. Re-start to Command Prompt Only, delete

> %windir%\win386.swp, check the autoexecs for lines, restart to Normal and

> re-enable the PnP ESS Dos emulation. Restart, and check that everything is

> set properly... only then try to test the cards....

>

> See prior postings related to this conflict and setup, autoexec, etc...

>

> --

> MEB

> http://peoplescounsel.orgfree.com

 

Solution found!

 

I wanted to test out my "new" es1373-based chipset audio card, as

opposed to the one I had been using the other day, which was based

around the es1371 chipset. The new card model for testing is called

CT4740.

 

I did these 4 tasks -

 

1) Installed standalone driver package called SBAudioSetup_W9x.zip

from the Creative website.

 

After installing, I went to Device Manager and selected Properties for

the newly installed audio device. Inside this properties section, I

unchecked the legacy emulation option. After a few reboots, I then

did -

 

2) Added a SET BLASTER=... line to my autoexec.bat (I purposefully

didn't bother to physically add an old ISA-based SoundBlaster to my

machine - I figured that by simply adding a SET BLASTER line to the

autoexec.bat file was sufficient for my first round testing purposes.)

 

After a reboot, I noticed that even though the Legacy audio device had

been completely removed from Device Manager, my newly added SET

BLASTER had also been removed from autoexec.bat!

 

So I then did -

 

3) Installed the SBPCI_WebDrvsV5_12_01.exe package. This "upgrades"

the CT4740 audio device to use WDM drivers, which I think is the key

to solving this problem. After this installation was complete, I

noticed that all references inside Device Manager for Legacy audio

device were gone.

 

So I then re-added my SET BLASTER line to the autoexec.bat file,

rebooted, and then noticed that the SET BLASTER line remained

untouched - it hadn't been deleted.

 

Just to finish things off I did -

 

4) Installed the audio device apps, called capp_setupus.exe (along

with the 4 .LIB files)

 

Just to finalise testing, I then added in an old ISA-based SB16,

installed this device inside Windows 98SE using the drivers from the

Win98SE disc, and did some dxdiag sound and music testing on both

audio devices - all tests were OK. I also rebooted a couple of times,

and my SET BLASTER line still remained untouched.

[Guest SIGABOT]

RE: Ensoniq Creative AudioPCI sound card autoexec.bat woes

 

I understand what you are tring to do.

Before I tell you how, I would like to say, You can play a DOS game without

legacy drivers if executed from windows. Also, you can have windows search

for non-plugin-play hardware. Make sure you mind your IRQ's. You can't simply

declare your blaster settings manualy. First you must check the jumpers on

the old non-pnp and check the auto-asigned setting that your pnp-BIOS set for

you for the pnp-card. Or, you must go into your BIOS setup and force the

settings for your pnp-card to be diferent from the other card. You may not

have enough IRQ's to go around, you may not be able to share them and if you

did, you would get poor sound.

You could use a WDM driver for one card and a VXD driver for the other,

there by using less IRQ's and having one legacy DOS SOUND BLASTER entry.

(WIN98se and above WDM, SB-PCI WDM)

(WIN95 and above, VXD Ensoniq AudioPCI WIN95)

The one that is PNP should use the (WDM)

Uninstall the DOS Drivers then update the windows drivers.

Updating allows you to see what card and to choose specifically what driver.

You can get the latest drivers from http://www.creative.com, select other and legacy.

Tip for how you have it now:

Leave both "SET SOUNDBLASTER= " in there. The last entry changes the one

before.

You could have 10 set blaster or more and only, the last one matters.

I am curious, Please tell me why, you want to use two sound cards?

 

Eric

SIGABOT@hotmail.com