Ensoniq Creative AudioPCI sound card autoexec.bat woes

[rpgs rock dvds]

Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes

On 23 Jun, 19:03, "MEB" <meb@not h...@hotmail.com> wrote:
> "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in messagenews:90b0e965-0bbe-4f6b-9afb-85632505212d@k30g2000hse.googlegroups.com...
> On 23 Jun, 10:04, "MEB" <meb@not h...@hotmail.com> wrote:
>
>
>
>
>
> > See you noted the issue of the manual 220 addressing on the AWE32 to
> > Franc...
>
> > \Very minor change of subject: When I installed the ES Creative
> > \software driver package, it made a right mess of it. For an unknown
> > \reason, none of the "pure DOS" emulation software got installed on to
> > \the hard drive. The "DOS box in Windows" legacy device emulation
> > \seemed ok though. This has happened on two fresh clean installs. I
> > \used the self extracting .EXE found on Creative's website, for an
> > \"AudioPCI device".
>
> > Sounds like you have the INF still installed or a bad un-install.
> > Check in the %windir%\INF folder for an INF dated around the time period
> of
> > the drivers, or with a name that seems related. Open it with a text editor
> > and see if it is for the card. Remove it after un-installing. Not sure
> about
> > your installer, but some of Creative's installers had crummy
> > un-installers/routines.
>
> > What is the Creative model and/or ESS chipset?
>
> > \
> > \Later on today I'm going to have a look in to INF files, to see if I
> > \can spot anything to do with the ES legacy audio device. I did see
> > \something like that last night, but I was too tired to pay proper
> > \attention to it. One thing I did wonder was: if the ES Creative
> > \driver package is a self-extracing/running .EXE, how can I modify any
> > \of its install files before they get used by Windows when it adds in
> > \the ES card?
>
> > Try to open it with Winzip or 7zip or the like, if that fails try adding a
> > command line option:
> > /removeonly
> > /uninst
> > /extract_all:<path>
> > /a
> > /extract {path}
> > /x {path}
>
> > Try a *universal extractor* and use that to open most files:
>
> >http://legroom.net/software/uniextract-Universal extractor
>
> >http://www.izarc.org/-IZArc universal extractor
> >http://www.download.com/3001-2250_4-10826781.html- IZArc download
>
> > --
> > MEB
> >http://peoplescounsel.orgfree.com
>
> \
> \Thanks a lot for the info!!
> \
> \Before I mention some interesting INF info I found, please note that
> \my Ensoniq AudioPCI sound card uses chipset 1371.  (I do have at my
> \disposal untested 1370 and 1373 chipset-based ES/Creative cards.)
>
>  Is there a link you can provide so we can look at the *particular/specific
> driver* you are using?
> AHHH, better post links to BOTH drivers you are using/ intend to use...
>
> IF it is a Creative, is it the Soundblaster 128? Which model {CT5808,
> other}?
>
>  PCI 128
>  http://support.creative.com/downloads/download.aspx?nDownloadId=257-
> 4.61MB
>
> CT5808http://support.creative.com/downloads/download.aspx?nDownloadId=975- 4.1MB
>
> * - multi card web update - Sound Blaster® Vibra128, Sound Blaster 16 PCI,
> Sound Blaster PCI 128, Sound Blaster 4.1 Digital, and Sound Blaster Ensoniq
> AudioPCI users running Windows 98SE, Windows ME, Windows 2000 and Windows XPhttp://support.creative.com/downloads/download.aspx?nDownloadId=1843-
> 4.62MB
>
> OR Equisonic AudioPCI specific [first is above]http://support.creative.com/Products/ProductDetails.aspx?catID=1&subC...
>
> BTW: running TWO SoundBlasters can cause additional setup issues as the
> drivers MAY cause conflicts [same card/driver manufacturer; same basic
> *Creative* code; different chipsets or the SAME chipsets, with specific
> settings/code setings for each model card; potentially some of the SAME
> drivers and/or file names with different support - over-write potential,
> registry conflicts, enum issues....]
>
> \
> \Re: INF files and Ensoniq legacy audio device --> I think I may have
> \found something!
> \
> \Inside C:\Windows\INF, there is this file:
> \
> \EAPCI95.inf
> \
> \Which I guess "translates to"  Ensoniq Audio PCI Windows 95
> \
> \Inside this file, I find this entry:
> \
> \[SSC_Legacy_Device.AddReg]
> \HKR,,DeviceDriver,,es1371.vxd
> \HKR,,DevLoader,,*CONFIGMG
> \HKR,,SBEmu,1,01
> \HKR,,EnumPropPages,,"es137195.drv,DrvEnumLegacyPages"
> \
> \I run "regedit", and do a search for "es1371.vxd" (see 2nd entry
> \above), and the search comes up with an interesting looking entry
> \under this regedit folder structure:
> \
> \HKEY_LOCAL_MACHINE - System - Services - CLASS - MEDIA - 0011
> \
> \Inside the folder called 0011 (mentioned at the end of the line
> \above), there is this entry:
> \
> \DeviceDriver es1371.vxd (see SSC_Legacy_Device above)
> \DevLoader CONFIGMG (see SSC_Legacy_Device above)
> \DriverDesc Creative Ensoniq AudioPCI Legacy Device (note the word
> \"Legacy")
> \InfPath EAPCI95.INF (INF file mentioned above)
> \InfSection SSC_Legacy_Device (see SSC_Legacy_Device above)
> \MatchingDeviceId VIRTUAL\SSC-Legacy
> \SBEmu 01
> \
> \(Please note that I have omitted some of the entries found as I am
> \typing all these entries in to this message by hand.)
> \
> \I *think* that the most promising entry in this section is the very
> \last one - the one that says SBEmu.  Maybe if I change the value of 01
> \to something like 0, then this might disable this legacy emulation
> \device??
>
>  It appears that it should have a Configuration Manager asociated with the
> driver software. Have you used it?
> Don has noted issues with autoexec.bat/autoexec.dos [thanks Don, definately
> a *slap forehead moment* for that type of access].
>
>  I want to look at those specific drivers you're using before commenting
> further...
>
> \As I have never used regedit before to do anything, I thought I'd
> \better show you this information found before I do anything at all to
> \the registry!!
> \
> \Thanks!
> \
>
>  Oh, that was a good idea, let us look at the *specific* driver files you
> intend to/are using before you continue...
>
> --
>  MEB
>  http://peoplescounsel.orgfree.com
> --
> _________- Hide quoted text -
>
> - Show quoted text -

I should have told you about this, I'm sorry...

The Creative driver package which I used to install the Creative/
Ensoniq AudioPCI es1371 chipset-based card was called -

"Standalone driver for Creative ENSONIQ AudioPCI on Windows 95/98."

The filename is called -

epw9xup.exe

If you go to this link -

http://support.creative.com/downloads/welcome.aspx?nDriverType=0&nOS=3&nLanguageLocale=1033#Drivers

You will see this download in the 4th item down this list.

There are other downloads here too. I tried installing the first one
listed in this list *after* I installed the one mentioned directly
above. This second download is called -

"Sound Blaster PCI cards Web Update for users running Windows 98SE,
Windows ME, Windows 2000 or Windows XP."

This filename is called -

SBPCI_WebDrvsV5_12_01.exe

After it was installed and my PC rebooted, it caused complete "blue
screen chaos" with Windows, so much so that I had to reformat my HDD.
Actually, I've just re-read the blurb for this specific download, and
it says -

"This package is not applicable to model CT4730 2-channel audio card"

I have a funny/bad feeling that my ES1371 is a CT4730 2-channel audio
card!

As for the drivers for the other sound card which I have, which is the
old ISA-based AWE32 (non-PnP), I just got them from the Windows 98SE
disc.

Re your comment: "It appears that it should have a Configuration
Manager asociated with the driver software. Have you used it?"

No, I do not know where it is, or whether or not I have this
installed. The thing is, you know that very first link I provided
above, the "Standalone driver for Creative ENSONIQ AudioPCI..." -
well, I think it was just that - a standalone driver package *without*
any additional apps with it. Perhaps that is what I am missing -
additional software so that I can properly fine-tune the ES card?

I'm wondering if I should also download and install this file -

capp_setupus.exe

This can be found on that same downloads page I provided above, and
the download package is called -

"SB PCI 64/128/128 vibra application updates"

Reading the blurb, it says it is OK for the following card -

1370 and 1371-based card models.

Thanks a lot for all your help, best regards, Robert.

 

[rpgs rock dvds]

Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes

On 23 Jun, 19:03, "MEB" <meb@not h...@hotmail.com> wrote:
> "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in messagenews:90b0e965-0bbe-4f6b-9afb-85632505212d@k30g2000hse.googlegroups.com...
> On 23 Jun, 10:04, "MEB" <meb@not h...@hotmail.com> wrote:
>
>
>
>
>
> > See you noted the issue of the manual 220 addressing on the AWE32 to
> > Franc...
>
> > \Very minor change of subject: When I installed the ES Creative
> > \software driver package, it made a right mess of it. For an unknown
> > \reason, none of the "pure DOS" emulation software got installed on to
> > \the hard drive. The "DOS box in Windows" legacy device emulation
> > \seemed ok though. This has happened on two fresh clean installs. I
> > \used the self extracting .EXE found on Creative's website, for an
> > \"AudioPCI device".
>
> > Sounds like you have the INF still installed or a bad un-install.
> > Check in the %windir%\INF folder for an INF dated around the time period
> of
> > the drivers, or with a name that seems related. Open it with a text editor
> > and see if it is for the card. Remove it after un-installing. Not sure
> about
> > your installer, but some of Creative's installers had crummy
> > un-installers/routines.
>
> > What is the Creative model and/or ESS chipset?
>
> > \
> > \Later on today I'm going to have a look in to INF files, to see if I
> > \can spot anything to do with the ES legacy audio device. I did see
> > \something like that last night, but I was too tired to pay proper
> > \attention to it. One thing I did wonder was: if the ES Creative
> > \driver package is a self-extracing/running .EXE, how can I modify any
> > \of its install files before they get used by Windows when it adds in
> > \the ES card?
>
> > Try to open it with Winzip or 7zip or the like, if that fails try adding a
> > command line option:
> > /removeonly
> > /uninst
> > /extract_all:<path>
> > /a
> > /extract {path}
> > /x {path}
>
> > Try a *universal extractor* and use that to open most files:
>
> >http://legroom.net/software/uniextract-Universal extractor
>
> >http://www.izarc.org/-IZArc universal extractor
> >http://www.download.com/3001-2250_4-10826781.html- IZArc download
>
> > --
> > MEB
> >http://peoplescounsel.orgfree.com
>
> \
> \Thanks a lot for the info!!
> \
> \Before I mention some interesting INF info I found, please note that
> \my Ensoniq AudioPCI sound card uses chipset 1371.  (I do have at my
> \disposal untested 1370 and 1373 chipset-based ES/Creative cards.)
>
>  Is there a link you can provide so we can look at the *particular/specific
> driver* you are using?
> AHHH, better post links to BOTH drivers you are using/ intend to use...
>
> IF it is a Creative, is it the Soundblaster 128? Which model {CT5808,
> other}?
>
>  PCI 128
>  http://support.creative.com/downloads/download.aspx?nDownloadId=257-
> 4.61MB
>
> CT5808http://support.creative.com/downloads/download.aspx?nDownloadId=975- 4.1MB
>
> * - multi card web update - Sound Blaster® Vibra128, Sound Blaster 16 PCI,
> Sound Blaster PCI 128, Sound Blaster 4.1 Digital, and Sound Blaster Ensoniq
> AudioPCI users running Windows 98SE, Windows ME, Windows 2000 and Windows XPhttp://support.creative.com/downloads/download.aspx?nDownloadId=1843-
> 4.62MB
>
> OR Equisonic AudioPCI specific [first is above]http://support.creative.com/Products/ProductDetails.aspx?catID=1&subC...
>
> BTW: running TWO SoundBlasters can cause additional setup issues as the
> drivers MAY cause conflicts [same card/driver manufacturer; same basic
> *Creative* code; different chipsets or the SAME chipsets, with specific
> settings/code setings for each model card; potentially some of the SAME
> drivers and/or file names with different support - over-write potential,
> registry conflicts, enum issues....]
>
> \
> \Re: INF files and Ensoniq legacy audio device --> I think I may have
> \found something!
> \
> \Inside C:\Windows\INF, there is this file:
> \
> \EAPCI95.inf
> \
> \Which I guess "translates to"  Ensoniq Audio PCI Windows 95
> \
> \Inside this file, I find this entry:
> \
> \[SSC_Legacy_Device.AddReg]
> \HKR,,DeviceDriver,,es1371.vxd
> \HKR,,DevLoader,,*CONFIGMG
> \HKR,,SBEmu,1,01
> \HKR,,EnumPropPages,,"es137195.drv,DrvEnumLegacyPages"
> \
> \I run "regedit", and do a search for "es1371.vxd" (see 2nd entry
> \above), and the search comes up with an interesting looking entry
> \under this regedit folder structure:
> \
> \HKEY_LOCAL_MACHINE - System - Services - CLASS - MEDIA - 0011
> \
> \Inside the folder called 0011 (mentioned at the end of the line
> \above), there is this entry:
> \
> \DeviceDriver es1371.vxd (see SSC_Legacy_Device above)
> \DevLoader CONFIGMG (see SSC_Legacy_Device above)
> \DriverDesc Creative Ensoniq AudioPCI Legacy Device (note the word
> \"Legacy")
> \InfPath EAPCI95.INF (INF file mentioned above)
> \InfSection SSC_Legacy_Device (see SSC_Legacy_Device above)
> \MatchingDeviceId VIRTUAL\SSC-Legacy
> \SBEmu 01
> \
> \(Please note that I have omitted some of the entries found as I am
> \typing all these entries in to this message by hand.)
> \
> \I *think* that the most promising entry in this section is the very
> \last one - the one that says SBEmu.  Maybe if I change the value of 01
> \to something like 0, then this might disable this legacy emulation
> \device??
>
>  It appears that it should have a Configuration Manager asociated with the
> driver software. Have you used it?
> Don has noted issues with autoexec.bat/autoexec.dos [thanks Don, definately
> a *slap forehead moment* for that type of access].
>
>  I want to look at those specific drivers you're using before commenting
> further...
>
> \As I have never used regedit before to do anything, I thought I'd
> \better show you this information found before I do anything at all to
> \the registry!!
> \
> \Thanks!
> \
>
>  Oh, that was a good idea, let us look at the *specific* driver files you
> intend to/are using before you continue...
>
> --
>  MEB
>  http://peoplescounsel.orgfree.com
> --
> _________- Hide quoted text -
>
> - Show quoted text -


PS:

Re your comment: "It appears that it should have a Configuration
Manager asociated with the driver software. Have you used it?"

Actually, I think I *have* used this. I think this was somewhere in
the ES audio legacy device's Properties section. However, I can't now
get access to this because I have removed this legacy audio device
from both my actively used hardware configuration profiles (perhaps I
should have disabled this legacy device instead).

Tomorrow, I'm going to do a complete fresh install, this time I will
try both the es1371 card again and also an es1373 card. For both
install attempts, I will try disabling the legacy audio device
component, and see how I get on. I will also install a 2nd sound
card, the ISA-based AWE32 card, and see how it all works (or not!)
together. I also would like to try out one or maybe two more
different downloads from the Creative website.

 

[rpgs rock dvds]

Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes

On 23 Jun, 15:46, "Don Phillipson" <e...@SPAMBLOCK.ncf.ca> wrote:
> "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in messagenews:6226e2d8-e266-4f11-83d4-266fe146f7da@79g2000hsk.googlegroups.com...
>
> > Unfortunately, I am finding that the (disabled or removed) Ensoniq
> > legacy audio device is still meddling with the autoexec.bat file which
> > I have carefully "fine-tuned" for my specific DOS requirements, which
> > I set-up in the manner you described in your post.
>
> 1.  Custom settings specific for individual DOS utilities are
> set in AUTOEXEC.DOS not AUTOEXEC.BAT (i.e. ought
> not to be called at reboot.)
>
> 2.  Standard Win98 installations do not require AUTOEXEC.BAT
> and CONFIG.SYS.  Default setting is to boot without either (i.e.
> if they are present, REName both to something else.  Because
> Windows loads after running AUTOEXEC.BAT and CONFIG.SYS
> its unique drivers (e.g. for a SoundBlaster) override any DOS
> settings loaded earlier (and may overwrite that part of RAM
> where they were loaded.)
>
> 3.  We can boot straight MS-DOS via / Start / Shut Down
> and then AUTOEXEC.BAT and CONFIG.SYS load as normal.
> MSCONFIG / General / Selective Startup check boxes let us
> select whether AUTOEXEC.BAT and CONFIG.SYS should be
> processed when starting Windows.
>
> --
> Don Phillipson
> Carlsbad Springs
> (Ottawa, Canada)

Thanks a lot, I will look in to all of this tomorrow.

 

[MEB]

Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes

Okay, downloaded that standalone driver, will look at it shortly. It appears
it may be just an *update* for an already installed driver set
http://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. OEM
http://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
--
_________


"rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message
news:a44f3b9e-55a9-4ce5-aec9-87d96374c105@c65g2000hsa.googlegroups.com...
On 23 Jun, 19:03, "MEB" <meb@not h...@hotmail.com> wrote:
> "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in
messagenews:90b0e965-0bbe-4f6b-9afb-85632505212d@k30g2000hse.googlegroups.co
m...
> On 23 Jun, 10:04, "MEB" <meb@not h...@hotmail.com> wrote:
>
>
>
>
>
> > See you noted the issue of the manual 220 addressing on the AWE32 to
> > Franc...
>
> > \Very minor change of subject: When I installed the ES Creative
> > \software driver package, it made a right mess of it. For an unknown
> > \reason, none of the "pure DOS" emulation software got installed on to
> > \the hard drive. The "DOS box in Windows" legacy device emulation
> > \seemed ok though. This has happened on two fresh clean installs. I
> > \used the self extracting .EXE found on Creative's website, for an
> > \"AudioPCI device".
>
> > Sounds like you have the INF still installed or a bad un-install.
> > Check in the %windir%\INF folder for an INF dated around the time period
> of
> > the drivers, or with a name that seems related. Open it with a text
editor
> > and see if it is for the card. Remove it after un-installing. Not sure
> about
> > your installer, but some of Creative's installers had crummy
> > un-installers/routines.
>
> > What is the Creative model and/or ESS chipset?
>
> > \
> > \Later on today I'm going to have a look in to INF files, to see if I
> > \can spot anything to do with the ES legacy audio device. I did see
> > \something like that last night, but I was too tired to pay proper
> > \attention to it. One thing I did wonder was: if the ES Creative
> > \driver package is a self-extracing/running .EXE, how can I modify any
> > \of its install files before they get used by Windows when it adds in
> > \the ES card?
>
> > Try to open it with Winzip or 7zip or the like, if that fails try adding
a
> > command line option:
> > /removeonly
> > /uninst
> > /extract_all:<path>
> > /a
> > /extract {path}
> > /x {path}
>
> > Try a *universal extractor* and use that to open most files:
>
> >http://legroom.net/software/uniextract-Universal extractor
>
> >http://www.izarc.org/-IZArc universal extractor
> >http://www.download.com/3001-2250_4-10826781.html- IZArc download
>
> > --
> > MEB
> >http://peoplescounsel.orgfree.com
>
> \
> \Thanks a lot for the info!!
> \
> \Before I mention some interesting INF info I found, please note that
> \my Ensoniq AudioPCI sound card uses chipset 1371. (I do have at my
> \disposal untested 1370 and 1373 chipset-based ES/Creative cards.)
>
> Is there a link you can provide so we can look at the *particular/specific
> driver* you are using?
> AHHH, better post links to BOTH drivers you are using/ intend to use...
>
> IF it is a Creative, is it the Soundblaster 128? Which model {CT5808,
> other}?
>
> PCI 128
> http://support.creative.com/downloads/download.aspx?nDownloadId=257-
> 4.61MB
>
> CT5808http://support.creative.com/downloads/download.aspx?nDownloadId=975-
4.1MB
>
> * - multi card web update - Sound Blaster® Vibra128, Sound Blaster 16 PCI,
> Sound Blaster PCI 128, Sound Blaster 4.1 Digital, and Sound Blaster
Ensoniq
> AudioPCI users running Windows 98SE, Windows ME, Windows 2000 and Windows
XPhttp://support.creative.com/downloads/download.aspx?nDownloadId=1843-
> 4.62MB
>
> OR Equisonic AudioPCI specific [first is
above]http://support.creative.com/Products/ProductDetails.aspx?catID=1&subC.
...
>
> BTW: running TWO SoundBlasters can cause additional setup issues as the
> drivers MAY cause conflicts [same card/driver manufacturer; same basic
> *Creative* code; different chipsets or the SAME chipsets, with specific
> settings/code setings for each model card; potentially some of the SAME
> drivers and/or file names with different support - over-write potential,
> registry conflicts, enum issues....]
>
> \
> \Re: INF files and Ensoniq legacy audio device --> I think I may have
> \found something!
> \
> \Inside C:\Windows\INF, there is this file:
> \
> \EAPCI95.inf
> \
> \Which I guess "translates to" Ensoniq Audio PCI Windows 95
> \
> \Inside this file, I find this entry:
> \
> \[SSC_Legacy_Device.AddReg]
> \HKR,,DeviceDriver,,es1371.vxd
> \HKR,,DevLoader,,*CONFIGMG
> \HKR,,SBEmu,1,01
> \HKR,,EnumPropPages,,"es137195.drv,DrvEnumLegacyPages"
> \
> \I run "regedit", and do a search for "es1371.vxd" (see 2nd entry
> \above), and the search comes up with an interesting looking entry
> \under this regedit folder structure:
> \
> \HKEY_LOCAL_MACHINE - System - Services - CLASS - MEDIA - 0011
> \
> \Inside the folder called 0011 (mentioned at the end of the line
> \above), there is this entry:
> \
> \DeviceDriver es1371.vxd (see SSC_Legacy_Device above)
> \DevLoader CONFIGMG (see SSC_Legacy_Device above)
> \DriverDesc Creative Ensoniq AudioPCI Legacy Device (note the word
> \"Legacy")
> \InfPath EAPCI95.INF (INF file mentioned above)
> \InfSection SSC_Legacy_Device (see SSC_Legacy_Device above)
> \MatchingDeviceId VIRTUAL\SSC-Legacy
> \SBEmu 01
> \
> \(Please note that I have omitted some of the entries found as I am
> \typing all these entries in to this message by hand.)
> \
> \I *think* that the most promising entry in this section is the very
> \last one - the one that says SBEmu. Maybe if I change the value of 01
> \to something like 0, then this might disable this legacy emulation
> \device??
>
> It appears that it should have a Configuration Manager asociated with the
> driver software. Have you used it?
> Don has noted issues with autoexec.bat/autoexec.dos [thanks Don,
definately
> a *slap forehead moment* for that type of access].
>
> I want to look at those specific drivers you're using before commenting
> further...
>
> \As I have never used regedit before to do anything, I thought I'd
> \better show you this information found before I do anything at all to
> \the registry!!
> \
> \Thanks!
> \
>
> Oh, that was a good idea, let us look at the *specific* driver files you
> intend to/are using before you continue...
>
> --
> MEB
> http://peoplescounsel.orgfree.com
> --
> _________- Hide quoted text -
>
> - Show quoted text -


PS:

Re your comment: "It appears that it should have a Configuration
Manager asociated with the driver software. Have you used it?"

Actually, I think I *have* used this. I think this was somewhere in
the ES audio legacy device's Properties section. However, I can't now
get access to this because I have removed this legacy audio device
from both my actively used hardware configuration profiles (perhaps I
should have disabled this legacy device instead).

Tomorrow, I'm going to do a complete fresh install, this time I will
try both the es1371 card again and also an es1373 card. For both
install attempts, I will try disabling the legacy audio device
component, and see how I get on. I will also install a 2nd sound
card, the ISA-based AWE32 card, and see how it all works (or not!)
together. I also would like to try out one or maybe two more
different downloads from the Creative website.

 

[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

Thanks very much for all of this help info. Please note that I want
to start over and I am currently in the position whereby I have the
new ES1373 card to try out, alongside a "new" old mobo. I'm going to
do all the usual setup routines such as format HDD, install Win98,
then do a battery of tests on the new ES sound card, including
disabling the legacy audio device, adding in an AWE32, etc, etc. I've
also got hold of an interesting old ISA card called PAS16 = Pro Audio
Spectrum 16, which I want to test out too.

Lots of testing to do! Be right back (in about 24-48 hours). Thank
you.

 

[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.

 

[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.

 

[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 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