no-mbr
03-19-2002, 10:16 PM
Hi,
I have a Chain-Tech Integratd Mobo, using a AMD K500, with an onboard Video, SIS 530, IDE and ESS solo sound chip.
After using the CT supplied drivers CD I installed the video, ide and sound chip drivers.
Everything works fine, no errors in device manager, no problems in msinfo reports etc....
The ess solo driver loads a DOS command in the config.sys and autooexec.bat. No matter what I do I can't figure out where it comes from.
Actually the autoexec is replaced if you delete it.
I've checked, run keys, startup groups, "load" commands in ini files. Nothing in dosstart.bat or winstart.bat. The only thing that defeats this "loading" in renaming an ESS driver dll. (while at command prompt before loading)
Does anyone know how these "auto start" behaviors are written and passed to the OS and start files? I think the "code" or content for the DOS DRIVER COMMANDS is in the windows directory in *.dat file.....
Thanks.
I have a Chain-Tech Integratd Mobo, using a AMD K500, with an onboard Video, SIS 530, IDE and ESS solo sound chip.
After using the CT supplied drivers CD I installed the video, ide and sound chip drivers.
Everything works fine, no errors in device manager, no problems in msinfo reports etc....
The ess solo driver loads a DOS command in the config.sys and autooexec.bat. No matter what I do I can't figure out where it comes from.
Actually the autoexec is replaced if you delete it.
I've checked, run keys, startup groups, "load" commands in ini files. Nothing in dosstart.bat or winstart.bat. The only thing that defeats this "loading" in renaming an ESS driver dll. (while at command prompt before loading)
Does anyone know how these "auto start" behaviors are written and passed to the OS and start files? I think the "code" or content for the DOS DRIVER COMMANDS is in the windows directory in *.dat file.....
Thanks.