I have an updated driver for the ATI Rage II+ cards as well as a Yamaha YMF715 based soundcard. I'm going to try and post them tonight. Is there anything I should consider before that attempt?

You cannot change a file once uploaded, you can only edit the picture, description, and category. Include in the zip any texts, docs or pictures . Zip it up with 7zip or winzip.
Include a picture of the device or the disks if possible (only need be 800x800 pixels +/- .JPG) and Give a small description...
You can look at some of the other library posts to see what others have done....That is all I can think of.

Uploaded my collection of Reveal sound card drivers. There are a few bad files but also some work arounds....http://www.vogonsdrivers.com/getfile.php?file … 3&menustate=0,0
Due to recent circumstances will be trying to catch up and upload a bunch more..as time allows..

Horun wrote on 2024-03-26, 02:04:

You cannot change a file once uploaded, you can only edit the picture, description, and category. Include in the zip any texts, docs or pictures . Zip it up with 7zip or winzip.
Include a picture of the device or the disks if possible (only need be 800x800 pixels +/- .JPG) and Give a small description...
You can look at some of the other library posts to see what others have done....That is all I can think of.

Its a feature I've requested before. If you have a driver compilation which needs updating and you have good reasons, then Squallstrife can do it behind the scenes, atleast he did for me for the PowerVR driver compilation.

So, I got bored.
Installed 3.11 on Vmware, found out that there's a patching tool for the SVGA driver, figured that was a bit of a pain for your average pleb, bundled the patched driver with an inf file so your average joe can install it like a normal driver.
The main feature is simply that because it is renamed, and has a different name in the inf which clearly defines it as a vmware patched driver, it doesn't interfere with the standard drivers if for whatever reason that is an issue.

I... don't think a patched standard driver would be considered naughty, so here it is.
One thing I don't understand is that it works perfectly WITHOUT network, but goes haywire when the network is enabled.
I didn't make the patch, so I have no idea why this could be except possibly resource conflicts. I'll see if I can figure it out, but for now you've been warned.

Kinda curious how many people care if any.

Here's another couple of utils that would be useful to add.
CD-Open, cd-close (msdos)

Shamelessly created from instructions here:
https://groups.google.com/g/alt.msdos.batch/c … 1WuHhR38A?pli=1

DONALD G. DAVIS wrote:
> >> I wrote a tiny DOS program that will open/close CD-ROM trays by
> >> drive letter, from the command line or batch file. It's fully
> >> functional under MS-DOS and Win9x, but only the "open" function works
> >> under NT/2000/ XP. It's not on Internet sites, but I'll e-mail copies
> >> on request. A Web search will locate several other similar programs.

Here is a (similar?) program (2 actually). I have only one
CD-ROM drive so I don't know how this will work with multiple
drives.

1:: cd-opcl.bat
2@echo off
3if "%1"=="1" goto close
4if "%1"=="0" goto open
5echo. Syntax: %0 0³1
6echo. opens or closes cd-rom tray
7echo. 0 (zero) to open, 1 (one) to close
8goto end
9
10:open cdtray
11echo:`h}aXP5y`P]4nP_XW(F4(F6(F=(FF)FH(FL(Fe(FR0FTs*}`A?+,>%temp%.\cd-open.com
12echo:fkOU):G*@Crv,*t$HU[rlf~#IubfRfXf(V#fj}fX4{PY$@fPfZsZ$:K68$.>>%temp%.\cd-open.com
13echo:.T]6KRw'RmSf/*VtTZ$K+}n\I/~{R'K*X{/wW$Q3;[5:Jl.oh_fRW'[g9'e>>%temp%.\cd-open.com
14echo:0sum5FrT_0rLen$'?qN$$$$$$$$$$$$$$$F7{{/t$fJb$$/)e#>>%temp%.\cd-open.com
15for %%c in (call del) do %%c %temp%.\cd-open.com
16goto end
17
18:close cdtray
19echo:`h}aXP5y`P]4nP_XW(F4(F6(F=(FF)FH(FL(Fe(FR0FTs*}`A?+,>%temp%.\cd-close.com
20echo:fkOU):G*@Crv,*t$HU[rlf~#IubfRfXf(V#fj}fX4{PY$@fPfZsZ$:K68$.>>%temp%.\cd-close.com
21echo:.T]6KRw'RmSf/*VtTZ$K+}n\I/~{R'K*X{/wW$Q3;[5:Jl.oh_fRW'[g9'e>>%temp%.\cd-close.com
22echo:0sum5FrT_0rLen$'?qN$$$$$$$$$$$$$$$F8SC4t$fJb$$/)e#>>%temp%.\cd-close.com
23for %%c in (call del) do %%c %temp%.\cd-close.com
24:end

vetz wrote on 2024-04-02, 07:08:

Horun wrote on 2024-03-26, 02:04:

You cannot change a file once uploaded, you can only edit the picture, description, and category. Include in the zip any texts, docs or pictures . Zip it up with 7zip or winzip.
Include a picture of the device or the disks if possible (only need be 800x800 pixels +/- .JPG) and Give a small description...
You can look at some of the other library posts to see what others have done....That is all I can think of.

Its a feature I've requested before. If you have a driver compilation which needs updating and you have good reasons, then Squallstrife can do it behind the scenes, atleast he did for me for the PowerVR driver compilation.

^^^ This is the best way to do it, presently.

Also, regarding viruses/malware/trojans/etc in the files in the archive: if anybody wishes to bring these to my attention, please do.

However:
1. It's better to post the information in this thread, where multiple people can see and potentially validate the report. Most "infections" I've investigated have been false-positives.
2. At the very least, please include: A link to the download on the site, the name of the infected file within the ZIP/RAR/etc if applicable, and the name of the alleged virus.

henk717 wrote on 2021-04-15, 16:05:

I have a driver to contribute, I have found the official ESS Solo-1 driver online for Windows 3.11 but unfortunately the package […]
Show full quote

I have a driver to contribute, I have found the official ESS Solo-1 driver online for Windows 3.11 but unfortunately the package was awful (wrong folders, random autoexec.bat file) and the installer was broken despite coming from the official archived website.

Attached is a .zip file I put together that contains the official ESS Solo driver, but with an older installer exe taken from the ISA ESS AudioDrive and everything restored to the proper locations. This will allow the driver to install if you first load the ESS Solo dos driver. It provides WAVE and MPU support to Windows 3.11.
I have also included the ESS AudioRack that was part of the ESS AudioDrive driver bundle I took the install exe from.

This should allow other ESS Solo-1 owners to more easily use this card on Windows 3.11 as I am not aware of any other working install packages for this card that support 3.11.
The archive.org link can be found here : https://archive.org/details/essolo-311

Hi,

Thank you for the upload and the general idea on how to fix the ESS Solo-1 (ES1938) Windows 3.1x driver, but, sadly, the .EXE files from another driver break MIDI and FM ("The current MIDI Mapper setup refers to a MIDI device that is not installed on the system. Use MIDI Mapper to edit the setup.").

In order to fix the original factory driver for good, you simply have to move 3 of its own files (ESSSETUP.EXE, ESSLANG.US and ESSSOFT.INI) up one folder, and rename the folder itself to "ESSSET".

When using a MIDI daughterboard, make sure AuxB is enabled in AudioRack, and also that your MIDI Mapper configuration points to ESS AudioDrive MIDI Port Output and not ESS AudioDrive MIDI (otherwise you'll only hear ESFM), like this: