I thought I had this ironed out, but apparently not. This is continuing on a post I made a week ago: Windows 95/98 "Too Much Information" Sound Blaster 16 Configuration Glitch (No help needed)

It seems that Asus motherboards seem to be susceptible to this, since I've tried two (a P2B in the past, and a P3B-F in the present) and gotten similar results.

Has anyone had problems with certain DOS games crashing back to Windows if the Sound Blaster resources are not changed between sessions in Device Manager? i.e. You need to add or take away any parameters, like A220 I5 D1 H6 P330 T6 becomes A220 I5 D1 or any combination. And after a restart, the OS doesn't hold onto the ability to operate the DOS sound properly without crashing, even if it did work without problems in the previous session.

It gets tiresome, and I'd like to be able to play DOS games without having to reset any parameters.