Win98banter - View Single Post - Ensoniq Creative AudioPCI sound card autoexec.bat woes

**MEB[_2_]** · June 22nd 08, 07:17 PM posted to microsoft.public.win98.gen_discussion

"MEB" meb@not wrote in message
...
|
|
| "rpgs rock dvds" wrote in message
| ...
| | 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.
|
| 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

I should add, that when dealing with multifunction devices, or devices
which use this entry in Device Manager, it becomes somewhat more difficult
to remove its settings. Such as: modem sound card combos; modem sound
card IDE or proprietary CDROM interface other ....

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