Guest rpgs rock dvds Posted June 22, 2008 Posted June 22, 2008 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.
Guest Gary S. Terhune Posted June 22, 2008 Posted June 22, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes "rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message news:4add8afa-0260-4d07-887f-6a7442e9b0f5@c65g2000hsa.googlegroups.com... > 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/User http://grystmill.com
Guest Don Phillipson Posted June 22, 2008 Posted June 22, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes "rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message news:4add8afa-0260-4d07-887f-6a7442e9b0f5@c65g2000hsa.googlegroups.com... > 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. This is normal for DOS apps (e.g. legacy software for Win95/98). The question is why you need to load any DOS apps. or drivers (perhaps for a DOS game: if so, you could do this via AUTOEXEC.DOS for this particular game, activated uniquely for it via its own / Properties / Program / Advanced where you check the two boxes MS-DOS mode and Specify a new MS-DOS configuration and write the commands into the two boxes for CONFIG.SYS and AUTOEXEC.BAT. But at least some of these games run perfectly well under Windows, i.e. use Windows drivers, and need no CONFIG.SYS and AUTOEXEC.BAT at boot -- only those specific to a single DOS app as above. -- Don Phillipson Carlsbad Springs (Ottawa, Canada)
Guest rpgs rock dvds Posted June 22, 2008 Posted June 22, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes On 22 Jun, 17:51, "Gary S. Terhune" <none> wrote: > "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in messagenews:4add8afa-0260-4d07-887f-6a7442e9b0f5@c65g2000hsa.googlegroups.com... > > > 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.)
Guest rpgs rock dvds Posted June 22, 2008 Posted June 22, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes On 22 Jun, 18:05, "Don Phillipson" <e...@SPAMBLOCK.ncf.ca> wrote: > "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in messagenews:4add8afa-0260-4d07-887f-6a7442e9b0f5@c65g2000hsa.googlegroups.com... > > > 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. > > This is normal for DOS apps (e.g. legacy software for Win95/98). > > The question is why you need to load any DOS apps. or drivers > (perhaps for a DOS game: if so, you could do this via AUTOEXEC.DOS > for this particular game, activated uniquely for it via its own > / Properties / Program / Advanced > where you check the two boxes > MS-DOS mode > and > Specify a new MS-DOS configuration > and write the commands into the two boxes for CONFIG.SYS > and AUTOEXEC.BAT. > > But at least some of these games run perfectly well under > Windows, i.e. use Windows drivers, and need no CONFIG.SYS > and AUTOEXEC.BAT at boot -- only those specific to a single > DOS app as above. > > -- > Don Phillipson > Carlsbad Springs > (Ottawa, Canada) I really want to be able to restart Win98 in "pure DOS mode" for some DOS apps. And please note that I already do what you say in your post re running DOS apps. 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.
Guest Gary S. Terhune Posted June 22, 2008 Posted June 22, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes Why do you need two audio cards if both of then support DOS? Why not get rid of the ISA card altogether? Or is that the only one that has the game controllers ports that you need? I think Don has your answer. -- Gary S. Terhune MS-MVP Shell/User http://grystmill.com "rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message news:bf7b176f-39b7-4f22-86cf-e6985e818d1b@27g2000hsf.googlegroups.com... On 22 Jun, 17:51, "Gary S. Terhune" <none> wrote: > "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in > messagenews:4add8afa-0260-4d07-887f-6a7442e9b0f5@c65g2000hsa.googlegroups.com... > > > 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.)
Guest MEB Posted June 22, 2008 Posted June 22, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes "rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message news:4add8afa-0260-4d07-887f-6a7442e9b0f5@c65g2000hsa.googlegroups.com... | 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 http://peoplescounsel.orgfree.com -- _________
Guest rpgs rock dvds Posted June 22, 2008 Posted June 22, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes On 22 Jun, 18:43, "Gary S. Terhune" <none> wrote: > Why do you need two audio cards if both of then support DOS? Why not get rid > of the ISA card altogether? Or is that the only one that has the game > controllers ports that you need? > > I think Don has your answer. 1) I really want both sound cards: The ISA-based AWE32 card gives me DOS MIDI daughter board based music, and the PCI Ensoniq gives me good Windows based MIDI music using large file patch sets. 2) re Don answer, I'm afraid I am already using this approach to exit to DOS, and I am finding that the autoexec.bat file still gets tampered with.
Guest MEB Posted June 22, 2008 Posted June 22, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes "MEB" <meb@not here@hotmail.com> wrote in message news:Ogvmt$I1IHA.3680@TK2MSFTNGP05.phx.gbl... | | | "rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message | news:4add8afa-0260-4d07-887f-6a7442e9b0f5@c65g2000hsa.googlegroups.com... | | 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 -- _________
Guest rpgs rock dvds Posted June 22, 2008 Posted June 22, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes On 22 Jun, 18:50, "MEB" <meb@not h...@hotmail.com> 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!
Guest Franc Zabkar Posted June 22, 2008 Posted June 22, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes On Sun, 22 Jun 2008 10:29:48 -0700 (PDT), rpgs rock dvds <rpgsrockdvds@hotmail.co.uk> 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.
Guest MEB Posted June 22, 2008 Posted June 22, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes 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" <fzabkar@iinternode.on.net> wrote in message news:jhgt545igvjctmftfop1f0k1lbbfksab15@4ax.com... | On Sun, 22 Jun 2008 10:29:48 -0700 (PDT), rpgs rock dvds | <rpgsrockdvds@hotmail.co.uk> 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.
Guest MEB Posted June 22, 2008 Posted June 22, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes 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" <rpgsrockdvds@hotmail.co.uk> wrote in message news:5315504b-06be-44b9-ba94-2e45992e9df5@b1g2000hsg.googlegroups.com... On 22 Jun, 18:50, "MEB" <meb@not h...@hotmail.com> 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!
Guest rpgs rock dvds Posted June 23, 2008 Posted June 23, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes On 22 Jun, 22:24, Franc Zabkar <fzab...@iinternode.on.net> wrote: > On Sun, 22 Jun 2008 10:29:48 -0700 (PDT), rpgs rock dvds > <rpgsrockd...@hotmail.co.uk> 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. Re: "...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.
Guest rpgs rock dvds Posted June 23, 2008 Posted June 23, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes On 23 Jun, 00:43, "MEB" <meb@not h...@hotmail.com> 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?
Guest MEB Posted June 23, 2008 Posted June 23, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes "rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message news:9d1a8958-0dd6-4217-88c7-c1caeb0d5063@25g2000hsx.googlegroups.com... On 23 Jun, 00:43, "MEB" <meb@not h...@hotmail.com> 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 -- _________
Guest Antriksh Posted June 23, 2008 Posted June 23, 2008 RE: Ensoniq Creative AudioPCI sound card autoexec.bat woes 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. >
Guest rpgs rock dvds Posted June 23, 2008 Posted June 23, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes 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 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.) 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?? 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!
Guest Don Phillipson Posted June 23, 2008 Posted June 23, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes "rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message news: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)
Guest MEB Posted June 23, 2008 Posted June 23, 2008 Re: Ensoniq Creative AudioPCI sound card autoexec.bat woes "rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message news: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 CT5808 http://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 XP http://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&subCatID=207&prodID=420&prodName=Ensoniq%20AudioPCI&subCatName=Others&CatName=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....] \ \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 -- _________
Guest rpgs rock dvds Posted June 23, 2008 Posted June 23, 2008 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.
Guest rpgs rock dvds Posted June 23, 2008 Posted June 23, 2008 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.
Guest rpgs rock dvds Posted June 23, 2008 Posted June 23, 2008 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.
Guest MEB Posted June 24, 2008 Posted June 24, 2008 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.
Guest rpgs rock dvds Posted June 24, 2008 Posted June 24, 2008 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.
Recommended Posts