D
Dan
This is an incorrect presumption. The problem can still
occur due to how different drivers are written, different OS
works with them or has other things installed.
This also does not matter, as the only thing it tells you is
there is no application loading (later) that is interfering,
but it was not expected there would be an application
causing the problem.
We are taking opposing views on troubleshooting, I am
enumerating known reasons why it may happen rather than
trying for forsee unknown interactions. The problem with
trying to forsee the unknown, is that it's unknown.
Having the information that the sound plays wrong at login,
we can rule out audio players but not the other variables.
Ok, but I was not reading the whole thread, rather providing
a list of all things at once.
?? Are we talking about the same thing?
There is no reason to use APM instead of ACPI on Win2k
unless there is a specific problem using ACPI. Using APM
means the processor can't HALT-Idle as well so it uses more
power, higher running temps most of the time.
Using APM mean specifically chosing not to use ACPI, if the
board supports ACPI. It means that in Device Manager there
will not be an ACPI entry under "Computer", nor any under
"System Devices" category. Perhaps this is what you meant -
I'm only clarifying.
I couldn't disagree more, a problem like this is going to be
noticable to practically everyone with a PC in a home
environment. There is a fix for this, it can work, there is
nothing particularly proprietary about that system that
would interfere with it working unless the only sound driver
is very buggy for Win2k/XP, or a sever bios bug but that
isn't so likely since it doesn't happen in Win9x and Win2k
can run in a compatible legacy mode for APM.
Noted. Thanks. If something works out (before I dump the box for
something better) I'll post. This was a healthy troubleshooting, and
I've learned a number of things that may come handy in different
situations.