Ensoniq Creative AudioPCI sound card autoexec.bat woes

On Sun, 22 Jun 2008 10:29:48 -0700 (PDT), rpgs rock dvds
put finger to keyboard and composed:

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

I'm wondering why the second line has the same IO port (0x220) as the
first. Surely the ES legacy audio device is not sharing the same IO
port with your ISA-based (non Plug and Play) AWE32 card? Could the ES
legacy audio device that Windows sees actually be your AWE32 card???

It may be an idea to check the resources used by each device just to
see what is going on.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

That might relate to the DOS applications/games requiring a certain defined
and limited set of addresses and IRQs to function correctly [programmed into
the application/game],,, though I agree what Device Manager shows might be
instructive, certainly the driver portion for SB emulation would indicate
what particular card's software was being used [though that might still
leave a ghost/hidden driver or registry setting from the other card].

--
MEB
http://peoplescounsel.orgfree.com
--
_________


"Franc Zabkar" wrote in message
...
| On Sun, 22 Jun 2008 10:29:48 -0700 (PDT), rpgs rock dvds
| put finger to keyboard and composed:
|
| 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
|
| I'm wondering why the second line has the same IO port (0x220) as the
| first. Surely the ES legacy audio device is not sharing the same IO
| port with your ISA-based (non Plug and Play) AWE32 card? Could the ES
| legacy audio device that Windows sees actually be your AWE32 card???
|
| It may be an idea to check the resources used by each device just to
| see what is going on.
|
| - Franc Zabkar
| --
| Please remove one 'i' from my address when replying by email.

Right whatever is the last SET BLASTER statement will be the setting,
however, if it has already loaded its DOS emulation software, there will
likely still be an error when running DOS games/other [if not at other times
as well]. Same is true for any *SET* or *SET=* statement, which is why some
programmers will include SET {something}=NUL or SET {something} = {blank} to
clear these settings.

If you determine you must use that secondary BAT, add your
SET=SST{somethings} for the Voodoo to ensure they don't get corrupted or
removed, if this is the computer setup with a Voodoo in it.

--
MEB
http://peoplescounsel.orgfree.com
--
_________


"rpgs rock dvds" wrote in message
...
On 22 Jun, 18:50, "MEB" meb@not wrote:

my OP snipped to prevent this post getting too large and unwieldy

There are generally a few things that can be done.

One is to check the installation INFs prior to driver installation, to see
if you can remove the specific settings for the DOS emulation entries, and
by doing so, defeat their installation. This will generally work in most
instances and provides the most stable setups *WHEN POSSIBLE*.
Errors can occur when the device actually needs the emulation/DOS
autoexec.bat entry to initialize its full complement of ISA/PCI/PnP
aspects
[generally found in older/early ISA and ISA PnP cards or *cheapo/knockoff*
PCI cards]. This then copies those modified INFs to the INF directory
during installation, defeating errors in later installations of devices
[when you see that "building device information data base"]. This CAN,
however, cause unseen conflicts and/or errors IF the device IS PnP [chip
code discovery] and attempts to constantly set its requirements, even when
disabled or not installed. There MAY be debug routines and/or chip writing
apps which can make these modifications [semi]permanent, if supported on
the
device.
See this group for a recent discussion:
EMM386: Unrecoverable privileged operation error #I7 - 05/26/2008 -
05/29/2008

Another is to allow the installation, but disable [not remove] DOS SB
support in Device Manager for the secondary device. IF the second card has
removed the primary card's DOS support, then run Device Manager Install
New Hardware and see if it will re-find the original DOS emulation for the
primary card.

Another is to install the secondary card FIRST, disable DOS SB emulation
support, shut down, restart, check autoexec and remove the old line(s)
then
install the actual primary card and driver. Check the autoexec.bat for
improper entries. It may take more than one restart to get everything
right.

If you're attempting this AFTER installations, then open the installation
INFs [located in %windir%\INF\] and find the registry entries that were
created, then manually modify or remove the relevant entries from the
registry [export them first in case you make a mistake or they aren't the
right entries]. Also check in win.ini and system.ini to see if they
contain
entries which need removed. This requires you be familiar with the
registry,
its editing and areas, Windows directory installation entries [digit codes
at times], and other aspects that many may not be familiar with.

--
MEB
http://peoplescounsel.orgfree.com
--
_________

This looks very interesting - I want to look in to this but right now
I'm quite tired because I've been on the machine for over 10 hours and
I need to stop for a rest. Incidentally I did manage a "quick fix" by
adding this line to the autoexec.bat file -

call mybat.bat
(rest of autoexec.bat lines here...)

Inside the file called mybat.bat, I have my SET BLASTER line.

By doing this, the "Creative/Ensoniq meddling" doesn't affect what is
inside the mybat.bat file.

However I really want to get this fixed properly, so when I've rested
I am going to explore INF files, etc. (Never done that before!)

Thanks!

On 22 Jun, 22:24, Franc Zabkar wrote:
On Sun, 22 Jun 2008 10:29:48 -0700 (PDT), rpgs rock dvds
put finger to keyboard and composed:

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

I'm wondering why the second line has the same IO port (0x220) as the
first. Surely the ES legacy audio device is not sharing the same IO
port with your ISA-based (non Plug and Play) AWE32 card? Could the ES
legacy audio device that Windows sees actually be your AWE32 card???

It may be an idea to check the resources used by each device just to
see what is going on.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.


"...Could the ES legacy audio device that Windows sees actually be
your AWE32 card???"

I think I might know why this is happening - Windows installed the ES
card first, then afterwards I "added new hardware" to add in the
AWE32, even though the non-PnP AWE32 was inserted in to the mobo
first.

The Windows ES legacy device grabbed IO 220 perhaps because it didn't
know anything about the AWE32's physical jumpers being set to use that
IO addy as well.

When I "added new hardware" for the AWE32, I did not do an "automatic
search for hardware", but instead I manually selected to add in just
an AWE32 card. I did this because I tried to prevent a "whole package
of junk" being added in, like joystick ports etc. When I manually
selected the AWE32 to add to Windows, it rather unintelligently only
offered to add this card to Windows using its factory default
settings, one of which was IO 220. I must admit that I forgot that
the ES legacy device was also using that IO port.

It's quite amusing really, because when I was doing my dxdiag sound
and music testing, I was wondering why the dxdiag testing information
pop-up message box Ping! sound was coming out of one set of
headphones, and the test music itself was coming out of another set of
headphones.

Even though all this seems like a mess, it actually caused no serious
problems at all.

I have subsequently removed the ES legacy device from my hardware
configuration profiles, but as mentioned in my later posts in this
topic thread, it seems as if the ES legacy device is still trying to
tamper with my autoexec.bat file, even though I have tried to get rid
of this device.

On 23 Jun, 00:43, "MEB" meb@not wrote:
*That might relate to the DOS applications/games requiring a certain defined
and limited set of addresses and IRQs to function correctly [programmed into
the application/game],,, though I agree what Device Manager shows might be
instructive, certainly the driver portion for SB emulation would indicate
what particular card's software was being used [though that might still
leave a ghost/hidden driver or registry setting from the other card].

--
*MEB
*http://peoplescounsel.orgfree.com

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

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?

"rpgs rock dvds" wrote in message
...
On 23 Jun, 00:43, "MEB" meb@not wrote:
That might relate to the DOS applications/games requiring a certain
defined
and limited set of addresses and IRQs to function correctly [programmed
into
the application/game],,, though I agree what Device Manager shows might be
instructive, certainly the driver portion for SB emulation would indicate
what particular card's software was being used [though that might still
leave a ghost/hidden driver or registry setting from the other card].

--
MEB

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


"rpgs rock dvds" wrote:

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.

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

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!

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?

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

On 23 Jun, 10:04, "MEB" meb@not 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 extractorhttp://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.)

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,DrvEnumLegacyPag es"

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 structu

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

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!

"rpgs rock dvds" wrote in message
...

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)

"rpgs rock dvds" wrote in message
...
On 23 Jun, 10:04, "MEB" meb@not 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/download...DownloadId=257 -
4.61MB

CT5808
http://support.creative.com/download...DownloadId=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 XP
http://support.creative.com/download...ownloadId=1843 -
4.62MB

OR Equisonic AudioPCI specific [first is above]
http://support.creative.com/Products...=Sound+Blaster

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

\
\ 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,DrvEnumLegacyPa ges"
\
\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 structu
\
\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
--
_________