hI!! I HAVE WHOLE MY DAY LOOKING FOR ess1938s driver for dos SUPPORTED,FINALLY BUT I DON'T FIND IT!! pLEASE HELP ME ,iF ANYBODY TO HAVE ess1938s driver for dos OR SUPPORT TO ANY...

I HAVE SENT YOU A ATTACHMENT TO YOUR EMAIL IT IS ABOUT 29K , IT IS ALSO AVILABLE FROM WWW.JUMPTEC.DE/SW_DB/DOWNLOAD/BSI/ESS1938D.ZIP REGARDS CRAIG

Actually, there's no such thing. DOS drivers for the ESS1938 don't exist. DOS apps don't use drivers to access sound cards. The applications talk to the hardware directly, without the services of a driver. (This is why compatbility with certain models, like the Sound Blaster and Ad Lib, was so important.)

HI ANDREW, SO WHAT ? IS AT THE SITE ABOVE. I AGREE WITH YOU ABOUT NOT NEEDING DRIVERS AS SUCH AS I DO NOT HAVE A DRIVER FOR MY SB16 AND IT WORKS IF THE APLICATION HAS THE RIGHT DRIVER? BUT YOU CAN ALSO DOWNLOAD DRIVERS , WHAT ARE THESE ????. I WILL BE INTERESTED TO KNOW. REGARDS CRAIG.

Craig, This is not a driver. It's merely a setup utility and config file. All PCI sound cards and many ISA Plug-n-Play sound cards lack jumpers for configuring things like DMA channel assignments, hardware interrupt channel assignments, I/O port addresses, etc. In other words, they don't have jumpers you can use to assign hardware resources. Note that although some of these sound cards *do* have jumpers, but only for things like enabling/disabling CD-ROM interfaces, game ports, and MIDI ports and NOT for setting the IRQ, DMA, and I/O ports. These cards, although they do have jumpers for some functions, still require settings to be configured through Plug-n-Play. In addition, there are other features, such as whether the game port should be enabled or disabled, the default mixer settings, and what kind of emulation (typically Sound Blaster, Ad Lib, or Gravis) the card is supposed to provide (for those cards that can emulate more than one chipset). For Plug-n-Play cards, most or all of this configuration information is stored in EEPROM memory on the adapter card itself. Windows 9x/Me/2000/XP, Linux, BeOS, and other Plug-n-Play operating systems are capable of configuring these cards through the Plug-n-Play API and are also capable of using ACPI to retrieve the Plug-n-Play configuration information from a table. DOS cannot access this Plug-n-Play configuration information and cannot configure Plug-n-Play devices (not without some special extensions, anyway). This is why you have to run a special configuration program to set up these cards. The configuration program merely configures the card (because the jumpers you would ordinarily use to configure the card are absent) for use with DOS. It is not in any way a device driver. Most DOS software packages for these cards consist of * An executable configuration program, usually loaded by or launched from CONFIG.SYS or AUTOEXEC.BAT. This configuration program looks for configration information (settings) specified in a configuration file, normally an ASCII text file ending with an "INI" or "CFG" extension. * A configuration file, normally an ASCII text file ending with an "INI" or "CFG" extension. This configuration file contains all the settings, including DMA, IRQ, and I/O port settings, what kind of emulation to provide, mixer settings, what features are enabled or disabled, etc. Note that sometimes a configuration settings file isn't used. Sometimes, these settings are specified soley by using switches and/or arguments following the configuration program in CONFIG.SYS or AUTOEXEC.BAT. These packages also frequently include test/diagnostic utilities (many similar to Voyetra's SoundCheck), programs that allow you to view or change the configuration settings (without having to manually edit the config file or flags in CONFIG.SYS or AUTOEXEC.BAT.). Really nice ones may include such goodies as a DOS mixer, CD Player, or other handy little apps. I have even seen some vendors refer to "DOS drivers" in their documentation--particularly in poorly translated documentation from certain Taiwanese manufacturers. It could be a translation issue, it might just be simply to say "driver" than "configuration utility", or the writer responsible for the documentation may not have the foggiest idea what's going on (this is more often the case than you'd want to know!). The misconception that DOS uses drivers for sound cards seems to have spread wildly since 1993 or 1994 or so, when a lot of people who were using computers for the first time were using machines that were either running Windows 3.x or Windows for Workgroups 3.x on top of DOS. Rest assured, however, that these files are not device drivers. They basically just let you configure the card the way you would have done it if there were jumpers for those settings. In real-mode DOS, there's no such animal as far as sound cards are concerned.

By the way, I hope I didn't sound too pedantic, nit-picking, or rude. I didn't mean to be. I often come off as a down-talking, insulting, know-it-all and it's not intentional. I hope you weren't offended. There are so many widespread myths and misconceptions, so much bad information, and so much misused and loosely used terminology, it's almost impossible not to be confused or deceived by it. (I've seen so many things in CompTIA A+ and various Microsoft study kits and certification tests that were very, VERY wrong, it isn't funny. This has done a LOT to promote these myths.)

HI ANDREW, ON THE CONTRY I APPRECIATE ALL THE HELP THAT I CAN GET, ESPECIALLY WHEN IT IS PUT ACROSS SO ELEGANTLY . I KNOW NO WITH SOME CONFIDENCE THAT DOS DOSE NOT USE DRIVERS AS SUCH , AND MY OVERALL PICTURE OF THE WORKINGS OF DOS IS NOW ABIT CLEARER . THANCK AGAIN REGARDS CRAIG