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