-
I tried that, too. No change.
I do have a driver problem with the CMI audio on this board. It says this device cannot start. I have the right driver for it, downloaded from PCChips. By the way, it says on their page that it will work for WinXP, but upon unzipping there is no XP folder. it does install, just gives that error message.
Could this all be caused by a previous driver from the original motherboard? I cannot uninstall the previous modem driver, nor the previous Ethernet driver. Under AddRemove programs - It acts like it is going to, then it just puts it back on the screen, with no messages.
I could use a good "old driver" cleaning program or utility.
-
Funny how one's brain fails to recognize things - you said you replaced the motherboard BUT repaired the OS.
It is my understanding that major changes to hardware affect the capability of using an existing Windows install - chipsets being the major issue. And I also have read the MS$ doesn't like people 'upgrading' their systems and using 'old' software purchases from them to do it.
-
I understand your point, but I do not accept the fact that just b/c my motherboard failed, I have to purchase another Windows/License. I already have a valid license key on this machine.
the problem is that E-Machines uses sub-par components that fail regularly.
just my .02 c. But thanks for the help...
-
All you have to do is remove the sound drivers from add/remove programs and reinstall after a swift reboot... but before you do that, ensure you have installed the chipset drivers.
-
I tried that already. The previous sound card drivers show to be uninstalled. The C-Media shows to be installed, but it will not work for some reason.
-
For what it is worth, I have also heard that a number of people have called MS$ after a failure of components that they changed and had no major problem in getting 're-authorized'.
:)
-
OK... what cmedia chipset is it and have you installed the motherboard drivers?
-
Method 2: Locate the installation log file on your computer
Most operating system updates use Package Installer for Windows (Update.exe). The installation creates a default log file that records successes and failures in the %systemroot%\KB######.log file.
Note ###### is the number of a Microsoft Knowledge Base article.
For example, if the package that is described in Microsoft Knowledge Base article 12345 is not successfully installed, click Start, click Run, type %systemroot%\KB12345.log, and then click OK to troubleshoot the problem.
Note Operating system service packs create the %systemroot%\Svcpack.log file during installation.
What does the log say?
-
Just a question, but, do you have to have Administrator priviledges?
-
Yes, I have admin privs.
The motherboard is a M963GV R5.0. The audio is C-Media, according to their web site. I Have downloaded and installed their driver - it is the one that is not working (see above posts).
As far as the logs files of each update, here is the log file for one of them:
[KB835409.log]
2.547: ================================================== ==============================
2.547: 2007/07/12 03:10:58.375 (local)
2.547: C:\WINDOWS\SoftwareDistribution\Download\4bc2cf39b dd0ad1e68a3c3449f58e28d\update\update.exe (version 6.2.29.0)
2.547: Hotfix started with following command line: /si /ParentInfo:ec33242cf5e5de4e9e9efb9aec369975
3.406: DoInstallation: CleanPFR failed: 0x2
3.406: SetProductTypes: InfProductBuildType=BuildType.IC
3.406: SetAltOsLoaderPath: No section uses DirId 65701; done.
3.453: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB835409$
3.453: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed: 0xe0000102
3.453: ref tag c:\windows\system32\sp4.cab does not exist
3.453: ref tag c:\windows\system32\sp3.cab does not exist
3.453: ref tag c:\windows\system32\sp2.cab does not exist
3.453: ref tag c:\windows\system32\sp1.cab does not exist
3.453: ref tag c:\windows\system32\driver.cab does not exist
3.469: ref tag c:\windows\system32\fp40ext.cab does not exist
3.469: ref tag c:\windows\system32\fp40ext1.cab does not exist
3.469: ref tag c:\windows\system32\wms4.cab does not exist
3.469: ref tag c:\windows\system32\wms41.cab does not exist
3.485: ref tag c:\windows\system32\ims.cab does not exist
3.485: ref tag c:\windows\system32\ims1.cab does not exist
3.485: ref tag c:\windows\system32\ins.cab does not exist
3.485: ref tag c:\windows\system32\ins1.cab does not exist
3.485: Starting AnalyzeComponents
3.485: AnalyzePhaseZero used 0 ticks
3.485: No c:\windows\INF\updtblk.inf file.
3.485: OEM file scan used 0 ticks
3.485: AnalyzePhaseOne: used 0 ticks
3.485: AnalyzeComponents: Hotpatch analysis disabled; skipping.
3.485: AnalyzeComponents: Hotpatching is disabled.
3.485: FindFirstFile c:\windows\$hf_mig$\*.*
4.016: KB835409 Setup encountered an error: The update.ver file is not correct.
4.047: KB835409 Setup encountered an error: The update.ver file is not correct.
4.047: KB835409 Setup encountered an error: The update.ver file is not correct.
4.047: KB835409 Setup encountered an error: The update.ver file is not correct.
4.063: KB835409 Setup encountered an error: The update.ver file is not correct.
4.156: AnalyzeForBranching used 78 ticks.
4.156: AnalyzePhaseTwo used 0 ticks
4.156: AnalyzePhaseThree used 0 ticks
4.156: AnalyzePhaseFive used 0 ticks
4.156: AnalyzePhaseSix used 0 ticks
4.172: AnalyzeComponents used 687 ticks
4.172: Downloading 0 files
4.172: bPatchMode = TRUE
4.172: Inventory complete: ReturnStatus=0, 719 ticks
4.172: Num Ticks for invent : 719
4.172: [dumpDownloadTask] We have all necessary files for the package to install. Return STATUS_READY_TO_INSTALL
4.172: dumpDownloadTask returned 0xf201 (ready to install)
4.203: KB835409 installation did not complete.
4.203: Update.exe extended error code = 0xf201
the svcpack log is very large. It is dated yesterday, and I have tried updating several times today. It "appears" to be relevant to the SP2 install, which installed correctly.
Right now I am running system file checker to see if it finds any probs.
-
While we are on the topic. What is the correct procedure for maintaining a working Windows XP install - before and after a motherboard install?
thanks,
AW
-
I am not entirely sure what you mean - Noo Noo is much better at these things generally (like 99% of the time) BUT the key in a case like yours is to install the exact same motherboard.
Another thing I have learned is that partitioning can protect valuable data since, if the OS crashes tragically, the data remains in the other partition (normally) and the OS can be repaired or even reinstalled without wiping out everything.
The last major thing I have learned is in 2 parts: backup valuable data FREQUENTLY and run GOOD antvirus and antispyware programs routinely.
Pretty much my best advice.
:)
-
just thought I'd post what fixed it.
I ran CCleaner thru several times.
Then ran a nifty little problem called dial-a-fix (found it on another tech forum post with the same problem).
Everything is working now but the C-Media audio. I got all 79 updates installed. Yes! Now for the ding ding...
-
One thing you can try is to boot into Safe Mode, and remove any "phantom" or "ghost" sound driver installations that appear in the Device Manager. Safe mode will reveal if any previous failed or incorrectly removed installations are still hanging about, possibly causing problems. Then reboot and re-install the correct sound drivers.
(A good registry/system cleaner may achieve the same results, but I think it's always best to try Windows' own way first, safer... )
-
Thanks for that advice - I will check it shortly....
Another question - This system has several DLLs left on it concerning hardware that is not currently used or installed - ie ATI video card DLLs, etc....
Are those safe to delete? If the program is listed under add/remove, it does not work. Or there is no program listed at all for these DLLs. These may be causing my audio driver problem?
Or does Windows keep some common hardware devices loaded up even if they are not physically installed?
