|"...i din't know why you were talking about cmi above."|
Oops - regarding the CMI chipset sound - I got this mboard's onboard sound mixed up with the sound card on your MVP3 mboard.
On the other hand, it's possible the soundchip is actually a CMI one, or another brand other than Realtek. Realtek doesn't make their own chips, or, if they do, they are identical to ones originally made by another manufacturer with Realtek labelling slapped on it - sometimes you will see there is no Realtek chip on the mboard; sometimes it's been re-labelled as a Realtek one. Realtek provides drivers for many brands of chips that originally had the maker's own drivers - the *.inf file is often identical to the one provided by the actual maker, except it has been modified to display Realtek labelling in Windows.
Did you use the sound drivers listed on the Intel web site?
Maybe 90% of the time, problems like you are experiencing are caused by you not installing the software properly and/or in the right circumstances.
Maybe 5% of the time, it's caused by there being bugs in the software included on a CD for a device - in that case, loading the latest available software for the device from the manufacturer's web site usually cures the problem because the bugs have likely been eliminated.
This applies to installing ANY software:
" - did you have a minimum of programs running when you installed the software for the printer, including did you DISABLE the resident module(s) of your anti-malware software??"
The software may not install properly if you didn't do those things, yet you may see no error messages or other indication that it did not install properly.
In a small number of cases, even software installed by Windows Updates may not install properly unless you do those things before the software is installed.
I always try to remember to do those things when I install software, and I rarely have problems when I do that.
"- did you follow the proper installation directions?
E.g. you are often required to NOT plug in the printer until AFTER you have installed the software for it."
It is often a BAD idea to point Windows to the location of drivers while booting BEFORE you have installed the software for a device - when Windows finds a device while booting, you allow it to search for drivers and it doesn't find any, and it prompts you to provide the location of drivers - in that case the drivers and associated programs often do not install properly.
When Windows finds a device while booting, you allow it to search for drivers and it doesn't find any, and it prompts you to provide the location of drivers, CANCEL that, let the desktop load, then install the software for the device using the proper software installation program.
If you suspect a previous install of the software might not have installed properly, or if you want to try installing it from scratch, un-install the software for the device BEFORE you try installing it again.
The sound not working at all, or it only partially working, is usually directly related to it's software not having been installed properly. In a small number of cases that may be caused by incompatibility with other software.
"1. my xp had a logon screen. i did 'run' control userpasswords2 and killed that."
Sometimes when you load certain software, you will get a logon screen when you didn't have one before.
E.g. when you load a certain .Net Framework version (2.0?) - in that case, there is an update for the .Net Framework version that gets rid of the logon screen, available on the Windows Updates page on the Microsoft site when you do a Custom search.
"...my keyboard volume knob doesn't work anymore"
Are you sure that was working before? Special buttons and features on keyboards often require you install additional software for the keyboard model.
Even if it was working before, that may be a symptom of the sound software having problems, not the keyboard.
Have you looked in System Information for any indication of what the problem is??
E.g. under Components - problem devices?
Is the sound the only one using a certain IRQ?
Are you sure it isn't sharing an IRQ used by USB controller related devices?