China DOS Union

mrdeadman: Cleaning up these useless things is not enough, I have already tried it. Because the real DOS sound card driver is realized by simulating the SB16 sound card, but this program does not have these simulations, but directly completes it through hardware control. So it is not possible to succeed just by cleaning up these parts, but it is necessary to make the part of the virtual SB16 sound card into a TSR module to stay in memory.

Wengier, Open the attachment
See if this thing is useful. Originally, this thing was in the same compressed package as the via sound card driver. In the program generated by compiling wss.c (originally called sben686.exe, I changed it to ac97.exe when compiling), and this viavol also needs to be run. I forgot it in a hurry. Maybe after modifying this thing, the compiled thing matching that ac97.exe is a perfect driver program.



http://www.cn-dos.net/forum/UploadFile/2004-9/20049974625113.rar

I took a look at this viavol program, and it doesn't seem to be useful to me. It seems like it's just for adjusting the volume of VIA's AC97 sound card.

Hehe, with my level, I'm probably at the end of my rope. To further develop AC97 for DOS, it depends on everyone.

Wengier
mrdeadman
Hello, everyone! These days I've been trying every way to make the sound cards (integrated AC97 and independent SB PCI64) make sounds under DOS, but no matter what, it still doesn't work. Most of the time, it prompts "Sound card not found".
Integrated AC97 situation: (When testing, I didn't unplug the SB PCI64 sound card on the PCI slot. Does this have something to do with it?)
After using WENGIER's AC97.EXE, it keeps "PLAYING.....SAMPLES.....PLAY... WRITE......" (It seems it won't stop...)
After using mrdeadman's AC97.EXE, it prompts that AC97 is found, but there's no sound..
SB PCI64 (ES1370, ENSONIQ audioPCI) situation: (When testing, I disabled the integrated AC97 in BIOS)
The download from the new DOS era can't be done. Then I downloaded the corresponding DOS drivers (FOR SB PCI64, ES1370) from foreign websites, including APINIT.COM (4.26, corresponding to ES1370, 1371, 1373) and SNDSCAPE.INI and other files. According to its instructions, when running the key APINIT.COM, it's always one sentence: "Sound card not found". I tried APINIT (4.36, corresponding to ES1371, 1373) and it's the same...
After running in CWSDPMI, running DMAMEPP also doesn't work.
I'm very depressed. Please, you two take a look and help.
Is there still no simulation program that simulates PCI data into ISA SOUND BLASTER standard (like DIAMOND's SB-EMU)?
To add, the integrated AC97 and the SB PCI64 on the PCI slot have no problems under WINDOWS XP.
Also, my DOS platform is WENGIER's DOS7.10, not the real mode of DOS98. Does this have an impact?
......

Wengier, you say which has a greater chance of continuing that wss.c or working on that ichinit (written in assembly language)

Haha! After going through untold hardships, I finally succeeded in driving my second-hand SB PCI64 (ensoniq audioPCI, ES1370)!!!
Maybe the driver used last time, although it completely corresponds to all models, but perhaps the person who uploaded it made a mistake!!
First of all, although I didn't use the programs of WENGIER and mrdeadman, I still thank the two for their support!
Now I am the happiest person in the DOS forum!!!
I searched hundreds of websites, and finally on GOOGLE, I finally found the world's most complete website for sound card drivers that I encountered
http://www.soundcard-drivers.com/companies/258.htm (However, you need to register, and send the username and password to your email)
Highly recommend it to everyone!!! Don't forget to top it up!!!)
Then you can get whatever you want!! So cool 1!
Haha! I actually spent 20 yuan to buy an Innovation SB PCI64 (ensoniq audioPCI, ES1370)!! And in two days, I realized my dream of DOS sound!!
Under DOS, playing games with it, Jin Yongqun's blind transmission, etc., using the EAPCI2M.ECW sound library is actually better than the EAPCI8M.ECW!! Wonderful DOS music!!
Long lost!! What's that thing simulating SOUND BLASTER 2.0 in XP!! It's simply fooling country bumpkins!!
Just went to a small bar, and now I'm still drinking at home!!
Haha!

GOTOmsdos:First of all, congratulations on the successful sound output of your SB64 PCI sound card! But that soundcard-drivers (that is, the sound card driver part of driverguild) actually doesn't need to be registered because there is a universal password, that is: the username is drivers and the password is all. But there is no driver program for the AC97 sound card of Intel ICH/SiS 7012 in it. I know that running these drivers under MS-DOS 7.10 is naturally no problem. mrdeadman:Actually, if it's only up to us, the hope of making either wss.c or that ichinit into a real SB driver is not very great. Unless there are really高手 in C language or ASM language to help.

Thanks to Head WENGIER! I should have been told the password of that website earlier; it cost me a lot of time!! Mainly because it has many DOS drivers! I read many online articles, and it seems that to drive a DOS sound card, one has to rely on the real mode of WINDOWS, so I suspect that to drive a DOS sound card, one has to install 98? Because many online articles say that it seems that one has to run DOSSTART.BAT? But it's not! Haha! But I'm still a bit curious: How can DOS read SNDSCAPE.INI? This INI file is for WINDOWS to be compatible with old programs from the WIN3.1 era. The result must be that APINIT.COM reads SNDSCAPE.INI, because I intentionally renamed the EAPCI2M.ECW file, and then the sound card driver had an error, and it's SNDSCAPE.INI that records EAPCI2M.ECW! Also, why is the 8M sound bank not as clear and pleasant as the 2M sound bank? (I intentionally replaced it with EAPCI8M.ECW)

DOSSTART.BAT is actually just an ordinary DOS batch file, usually automatically run when Win9x returns to DOS, and has nothing to do with what "Win9x real mode" (actually this is Microsoft's term). SNDSCAPE.INI is the configuration file for the SB PCI sound card driver under DOS, and my configuration file for SB PCI 128 is SBPCI.INI, similar to the SNDSCAPE.INI file. Moreover, the 2M sound library (EAPCI2M.ECW) is also specified in my SBPCI.INI file, not the 8M one.

"DOSSTART.BAT is actually just an ordinary DOS batch file, usually automatically run when Win9x returns to DOS." I knew this. At first, I suspected whether it was necessary to go through the real mode from Windows to Windows to run APINIT.COM? Because I had already run the drivers with exactly the same version number before (including APINIT.COM, etc.), but it failed. Plus some online articles said that actually there are no DOS drivers, and it is necessary to restart Windows to the MSDOS mode. So I had such a suspicion. Now I know those people were half-baked!

Wengier, why can't the program you modified be compiled on my side?

After reading the e-book "DOS Memory Resident Programs and Examples" for a whole day, except for recognizing those words, basically I don't understand anything else. But I did figure out one thing: TSR programs should be as small as possible, preferably not exceeding 64k. However, the one compiled from which wss.c is 190k, heh, the future seems quite dim.

mrdeadman seems to have misunderstood. The so-called TSR program should preferably not exceed 64K means that the resident memory part should preferably not exceed 64K, not that the volume of the program itself cannot exceed 64K. Moreover, I simplified ac97.exe to only 165K, and after compression, it is only 35K. (Note: This program compiles completely without problems on my computer. In fact, I had to modify the source code you uploaded first to make it compile normally; otherwise, there were multiple errors displayed.) In short, there is no problem with the file volume. The key is still the writing of the TSR driver itself. It would be much easier if we could find the source code of DOS drivers for other sound cards.

Wengier, I know why the compilation is having issues. It's because there are some differences in our compiler settings, but the problem is that I don't know how to modify yours. Since I'm using the original compiler provided by the author, initially there doesn't need to be major modifications. And you might have changed something related to the environment, causing the compiler not to recognize it, heh.