[Ess Solo 1 Es1938s Windows 7 Driver Zip
Jamar Lizarraga
Hi guys,
Have a PC with windows 98 and trying to get an ESS es1938S (1938 chipset) PCI card going under DOS.
The SYS file loads OK but the ESSOLO.COM in the autoexec.bat file comes back with the message:
You need to load appropriate files in config.sys before loading essolo.com. Can't remember but I think it's essolo.drv and esfm.drv in config.sys. I don't even think you need the Windows driver (only the plain dos driver files from the package).
Sorry to wake up an old thread, but after getting an ESS Solo-1 from eBay and installing it, initially I couldn't manage to get it to work under DOS and Windows 98 SE using the drivers provided on Phil's computer lab website: -es1938s-solo-1.html , on a K8M890-based motherboard (MSI K9VGM-V), which has TDMA support, same as K8T890-based motherboards as reported in PCI sound cards and Chipsets from various manufacturers...
Secondly, the driver provided in solo1_drv_w9x_4.12.01.1165.zip (WDM version 4.12.01.1165) did not work at all for me in Windows 98 SE despite the card using IRQ 5, and working fine in DOS/XP/Linux. The "ESS SOLO-1 PCI AudioDrive" driver would have a yellow exclamation mark with the error message "This device is either not present, not working properly, or does not have all the drivers installed. (Code 10.)".
WDM-Driver does not work for FM
Cannot find the "audiodrive" is irq/dma bios failure
messing with pci-sets/ini's does mostly not work or is not far better then using the standard config. (e.g. turrican II)
the driver phil recommends kills my wavetable-module, so I am alwas using 1149 driver on win9x.
for dos I install the win3x driver in win3x and let it do it's thing.
sometimes it's better to put the Printer-Port to IRQ5 so that the Solo1 takes IRQ7 but that depends on your chipset. the later intel chipsets do not rout digisound correctly so that it will perhaps not work if you are using a faster cpu and a later intel-chipset. ALI/VIA are much better, but it also depends on the speed of the cpu.
you can try to set the win9x environment differently in win9x to the dos-settings within win9x. that gives you sometimes better compatibility. eg. Adress 240 than 220. Win9x emulates SB16 at 220 therefore using 240 can make a difference.
I've been setting up a Gigabyte GA-5SMM board with the solo-1 card. I followed philscomputerlab.com's instructions and had the exact same issues. Your post fixed my DOS setup and I now have sound in dos! Thank you so much. Now I just need to find a VBE that works.
I recently got an ESS Solo-1 PCI card for a Windows 95/DOS rig. While it works mighty fine in both Windows and DOS, I absolutely can't figure out how to enable the gameport. While installing the Windows drivers, only the device and DOS emulation drivers are installed, and there doesn't seem to be any trace of gameport in the device manager, or the game controller window. Same thing under DOS, loading the essolo.com properly configures the card, but always returns "Game Port Disabled" message.
I ran into the exact same problem. There is no way to activate the gameport. The driver does DISABLE it on start before Win95 is loaded. Changing the essolo.ini, changing the essolo.sys/com does not help. I can't figure out what the problem is. Installing a gameport manual in win95 does not work, it installs but it's not working.
I do have an older Win95-diver. This one installs the gameport just fine, BUT even if all drivers are installed (win-vxd and dos-emulation and joystick), there is NO sound in dos-window/fullscreen and in windows the sound stutters or even stops while playing (e.g. jediknight).
I've read a lot of posts here trying to find solutions to my issues to no avail. So I thought I'd ask and see if I can get some more specific answers. I'm building my first retro PC and have come across a lot of issues with Windows 98SE. My goal was to build something that could boot both 98SE and XP. As far as I can tell so far XP seems to be working ok. However 98SE is a whole nother story. I've had a range of issues from freeze ups, freezing during shutdown, freezing during restarting. blue screens during installation, not being able to open DOS programs due to memory issues etc.
I feel like the components I chose lean more towards being good for XP than for 98. I just wanted to make sure it could handle early 2000 games as well as some DOS and 90s games. However, I think this chipset is causing a lot of the issues in 98SE. After installing the chipset drivers that's when I notice the freeze ups and the freezing during shutdown/restart. And I know a lot of my memory issues had to do with me having 3gb of ram installed. Even when I reduced it to 1gb during installation I still had weird blue screens. While I could toil away trying to resolve these issues I thought I'd ask: Am I better off switching to a Pentium 3 / Pentium 4 processor and a different chipset? I was also thinking maybe I should find a motherboard that has ISA slots for more sound card options. Will I be able to find something that works flawlessly with 98 and XP?
Thanks for the reply! According the the article the two goto motherboards are the Asus Cubx and the Microstar BXMaster. I was hoping to use a Tualatin P3 and it looks like its not offically compatible with the Cubx, however, there is some kind of mod (not ideal) or adapter (can't seem to find) to get it to work? Does anyone have experience with a tualatin and 440bx? Would it be better to switch to another chipset (i815ep) or switch to a different cpu?
Your config is very stable under 98SE (even ACPI works flawlessly) and has full driver support.
>RAM: Atech 1GB DIMM DDR PC2700 333mhz x 3
but read about what you have to do with big memory. Few solution exist.
And yes, having 3 equal RAM modules are not optimal on Nforce2.
>some DOS ... games
Nforce2 is not optimal chipset for games under pure DOS. There is not support for ISA DMA emulation over PCI.
I had no trouble with nForce3 chipset drivers, I had a DFI LANparty nForce3 motherboard which previous owner had damaged one IDE controller which was an issue but all else was fine. The IDE driver is easy to update to 2.0.950.3020 date 2003 from VIA. This driver has to be manually chosen as the 98/ME original driver will have a higher version number. Have all your nForce driver infs installed in the windows inf folder. I un-install ACPI and the PCI bus and then install PCI bus first manually. Then install drivers, take a look at what drivers are compatible and choose the nForce ones. Do not force any other driver unless they are shown as compatible. This means that there will be several standard PCI bridges installed. This will ensure the South Bridge PCI to ISA bridge is installed which is an ISA emulator otherwise this ISA emulator will not be detected. The latest drivers from VIA for 98/ME are a good improvement especially the USB and IDE drivers. nForce chips are quality IMO but still can be destroyed, make sure all chips have enough heat-sinking. Getting old hardware that is not damaged would be a challenge, if your board is good then I would persevere with it.
440BX was the first Intel chip to hit 133MHz but it just made it in some cases and the design was mostly an over-clocking approach to the BUS so AGP and PCI cards had to be very good to work. Tualatin's need 133 FSB speed and if an adapter is required I would choose a board that can handle 133MHz FSB natively not just over-clock.
Hey, I'm back again with some more issues. So I'm not sure if I should start an entirely new thread for this but I have changed around my system a bit and am running into issues. For one, it won't post, or atleast, nothing shows up on my monitor.
When I power up, the fans spin on the cpu and the gpu and the led on the mobo lights up. Other than that nothing else works. I have a feeling that the graphics card I'm using isn't compatible with this board? I tried using the Jumperless setting and switching all the dips to off. Still no luck, any thoughts?
Next thing I'll try is a cpu that is actually meant to be used on this board and possibly other gpus. I also ordered some new replacement caps just in case the board needs a completely recap. Most of the caps all look fine but there is one that looks "sunken in" that may need to be replaced.
Ok so I switched out the GPU and now im getting a picture! So far I've been able to get into the bios but I can't load up an OS. It either freezes or restarts. Should I be flashing my bios now and going from there?
Managed to get into 98SE a few times but not very stable. Sometimes on boot it won't read the keyboard. Looks like I should fix up the bios and get the right settings in place before proceeding. Anyone know of a good tutorial on flashing bios?
Asus Cubx-e Rev. 1.01 is not native 133 FSB. This is not acceptable for Tualatin IMO. The CPU seller has not got 440BX as a recommended chip. Have you tried setting to 100MHz FSB or lower? A faster moderner Northbridge often has more sensitive inputting. ASUS CUSL2 motherboard i815E Northbridge I used with the CPU adapter and this works but this board only can work with 512MB of RAM. 768MB would sometimes get to boot screen with the best RAM sticks I had but was unusable. It is best to use a more modern board than Cubx although it is not worth pursuing unless board is inexpensive. There is usually no trouble to get Win98 working with early PCI Express graphic ported boards. How have you got your SSD drive attached? Have you tried setting IDE speed say to PIO mode 1 and DMA mode 1? The sunken capacitor; perhaps someone has pushed in a bulging one and should be replaced. Always replace Caps from CPU outwards and better caps will tend to lower the CPU voltage slightly due to less ESR producing a less noisy output but depends on switch mode's feedback control so test board again in a sequential manner after replacement. A capacitor with lower ESR can stop CMOS from toggling its output further away from supply sources as it acts as increasing the voltage a little. Be very careful of solder splatter and check thoroughly before powering up. If board works properly as designed then there is no need to change the caps too much as a working board may not boot after a long time left unused if cap changes were done unnecessarily. Unless the BIOS update has major improves like RAM control I doubt that flashing BIOS would help. There are sometimes pre-flashed chips available just ready to plug in and therefore easy to go back to original BIOS. Sometimes to squeeze in a more modern feature a BIOS update can make other compromises that may make other ports less likely to function.
795a8134c1