AMD series 8xx driver not found

'PCI\ven_1002&dev_4390&subsys_84431043&rev_40'
Windows 7 X64 SP1
Asus M5A88-M
RAID drivers not found!
IDE drivers not found? What The FUCK??
Asustek MoBo with AMD chipset has not (certified) drivers?
forum.acronis.com/forum/
Using Acronis TI 2011 with Universal Restore to image to the different MoBo (Asus M5A88-M) and as simple ide installation (no RAID in BIOS)
IDE or AHCI Is useless
At the end of the restore:
Device driver 'PCI\VEN_1002&DEV_4390&SUBSYS_84431043&REV_40' for Windows 7 cannot be found.

error 10138: Driver not found during restore
Anyway -Restart and then BSoD 0x00000007b
Acronis Universal Restore instructions 
Windows can not repair that 
error =0x490
I t seems tht a basic IDE driver is not embedded for the SB chipset 880 or 850
Source

This is from the HWID text file:
PCI\VEN_1002&DEV_439C&SUBSYS_84431043&REV_40\3&267A616A&0&A1
    Name: Standard Dual Channel PCI IDE Controller
    PCI\CC_0101

That's IDE emulation mode at BIOS.
A plain XP Installation CD does support this. No need to add drivers

Cebaehren' solution possibilities
support.amd.com/us/gpudownload/windows/Pages/raid_windows.aspx
eventually unpack the exe files with Universal Extractor v 1.6 and use the adecuate cat - inf - sys files to install thedrivers for graphic and SATA (RAID or AHCI)
Don't forget the changes in BIOS!
http://sites.amd.com/us/game/downloads/Pages/downloads.aspx
http://sites.amd.com/us/game/downloads/Pages/radeon_win7-64.aspx 
or try:
www.general-files.com/files-s/sata-amd/3/ 
http://www.x64bitdownload.com/drivers/64-bit-asus-m4a88td-m-usb3-hd-audio-driver-drivers.html
READ
Installing-Windows-7-on-a-new-PC-with-AHCI
after all.is OK.. use OverDrive
http://sites.amd.com/us/game/downloads/amd-overdrive/Pages/overview.aspx 
Perhaps
http://support.amd.com/us/kbarticles/Pages/CatalystAGPHotfix.aspx 

Mozilla Firefox ActiveX error

Source

a. Close all Firefox instances
b. Search for npmozax.exe [this is the plug-in I downloaded earlier today after which my Firefox went out of control]
c. Delete npmozax.exe
d. Search for npmozax.dll
e. Delete npmozax.dll
c:\program files\Mozilla firefox\plugins and delete npmozax.dll

I had the same problem and its due to the plugin for Quality Mercury Center.
I disabled this plug in to get rid of the error message, but how do you access Quality Mercury Center now? The plug in was required to access this program...
1. Click here to download Netscape 6 / Mozilla ActiveX plug-in (self-extract file)
2. Unzip downloaded plug-in into browser plug-in directory.
3. Restart the browser.

Source

These are the Media Player plugin files you should see in your plugins folder, which is located here: C:\Program Files\Mozilla Firefox\plugins

Windows Media Player 9
npwmsdrm.dll
npdrmv2.dll
npdsplay.dll

ActiveX
npmozax.dll

Real Player Version 10.5
nppl3260.dll
nprjplug.dll
nprpjplug.dll

QuickTime Version 6.5.2
npqtplugin.dll
nsIQTScriptablePlugin.xpt
QuickTimePlugin.class

If you don't see similar files like the above in the plugin folders, then copy them from the Media Player Program folders.

When you install a player, you can test it on various files here:
Media Test Pages
Audio, Video, & QuickTime Movies

cebaehren's solution:
Mediaplayerconnectivity

Allow you to launch embed video of website in an external application
with a simple click rn
* Replace the stream by a simple button
* Add a download icon in the status bar
* And/Or add links to right click
* Works with RealMedia, QuickTime, WindowsMedia, Playlists, Flash, background sounds, Nullsoft video, Shockwave
* Allow the use of any capable media player (with command line support)
* Support Media Metafiles (ram, rpm, wmv, wm, wma, asx, asf, ...)
* Activable per media format
* AutoPlay feature : automaticatlly start to play the first media
* Configuration wizard
* SmartPlay : automatically search and choose the best source using metafile ('+' icon) if exist
* List all media links on the webpage
* Use a sidebar for lists
* Multilingual rnrnNote : for OSX users, please use v0.5.6 available with
'Version History' link (on left) or from my website, versions 0.6+
don't works fine with OSX (I don't have a Mac for my tests....).

Win XP x64 SP2 und Domain-Anmeldung

Quelle
by junglelist on Tue Sep 16, 2008

ich habe ein Problem mit dem AntiWPA und einer Domain-Anmeldung. Ich hatte zuerst das Problem, dass Windows nach einiger Zeit bei einem Neustart eine Aktivierung verlangt hat. Davor hatte ich AntiWPA 3.4.7 installiert. Deshalb kam dann auch die Meldung, wenn ich gesagt habe er soll es aktivieren, dass es bereits aktiviert ist.
tasklist /m /fi
"Modules wq antiwpa.dll"
bestätigte mir auch, dass das Modul geladen war/ist und "%systemroot%\system32\oobe\msoobe.exe /a" brachte auch die Meldung, dass es aktiviert sei. Dann habe ich die neue Version 3.4.7b aus dem Beitrag installiert viewtopic.php?f=2&t=1059 und keine Probleme mehr gehabt.
Nun zum eigentlichen Problem. Ich habe nach einer Testphase und nach dem alles funktioniert, meinen Rechner in meine Domain eingebunden. Leider bekomme ich bei der Domain-Anmeldung die  Meldung, dass Windows nicht aktiviert sei und ich es aktivieren soll. Klicke ich ja, bekomme ich ebenfalls die Meldung, dass es aktiviert ist und er meldet sich ab.
Melde ich mich wieder an, kommt wieder das Gleiche. Es passiert dann auch, wenn ich versuche mich Lokal anzumelden. Starte ich den Rechner neu und melde mich zuerst Lokal an kommt die  Meldung nicht. Melde ich mich dann ab und melde mich an meiner Domain an, kommt die Meldung auch nicht. Es passiert aber ab und zu, wenn ich vergesse mich zuerst als lokaler Benutzer anzumelden, dass er mir die wpa.dbl zerschiesst. Dann kann ich mich auch Lokal nicht mehr anmelden und muss erst im "Abgesicherten Modus" die Datei löschen und kann mich dann wieder Lokal anmelden, um mich dann wieder an meiner Domain anzumelden. Der Domain-User ist Lokal in der Gruppe "Administrators" eingebunden.
Habt ihr ne Idee, wie ich das mit der lokalen Anmeldung vor der Domain-Anmeldung abschaffen kann?

---------------

by cw2k on Mon Dec 08, 2008

Wenn du nicht gerade ein 64-Bit System hast versuch mal den Antiwpa Klassiker: Antiwpa2
Das ist ein good old file Patch der aus der winlogon.exe der Aktivierungscheck rauspatched.Fertig.
Ansonsten ändere mal
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\Antiwpa
Logon="onLogon" nach
Startup= "onLogon"
Vielleicht hilft das was.

Operation System: 32-bit or 64-bit (x86 or x64)?

Source
If you want to find out whether the system is installed with a 32-bit or 64-bit (Microsoft labels them as x86 or x64) based operating system, which requires specifically built software application (See x86 or x64 OS)
Windows Vista

Method 1

1. Click Start, then click on Run or Start Search.
2. Type msinfo32.exe and then press Enter key.
3. In “System Information”, review the value for the System Type item:
   • For 32-bit editions of Windows, the value of the System Type item is x86-based PC.
   • For 64-bit editions of Windows, the value of the System Type item is x64-based PC.

Method 2

1. Click Start, type system in the “Start Search” box, and then click system in the “Programs” list.
2. The operating system appears as follows:
   • For a 64-bit version operating system: 64-bit Operating System appears for the “System type” under “System”.
   • For a 32-bit version operating system: 32-bit Operating System appears for the “System type” under “System”.

Method 3

1. Click Start, type system in the “Start Search” box, and then click System Information in the “Programs” list.
2. The operating system appears as follows:
   • For a 64-bit version operating system: x64-based PC appears for the “System type” under “Item”.
   • For a 32-bit version operating system: x86-based PC appears for the “System type” under “Item”.

Microsoft Windows XP Professional

Method 1

1. Click Start, then click on Run or Start Search.
2. Type msinfo32.exe and then press Enter key.
3. In “System Information”, review the value for the System Type item:
   • For 32-bit editions of Windows, the value of the System Type item is x86-based PC.
   • For 64-bit editions of Windows, the value of the System Type item is x64-based PC.

Method 2

1. Click Start, click Run, type sysdm.cpl, and then click OK.
2. Click the General tab. The operating system appears as follows:
   • For a 64-bit version operating system: Microsoft Windows XP Professional x64 Edition Version appears under System.
   • For a 32-bit version operating system: Microsoft Windows XP Professional Version appears under System.

   Note is a placeholder for a year.

Method 3

1. Click Start, click Run, type winmsd.exe, and then click OK.
2. In the details pane, locate Processor under Item. Note the value.
   • If the value that corresponds to Processor starts with x86, the computer is running a 32-bit version of the Windows operating system.
   • If the value that corresponds to Processor starts with ia64 or AMD64, the computer is running a 64-bit version of the Windows operating system.

Microsoft Windows Server 2003

Method 1

1. Click Start, click Run, type sysdm.cpl, and then click OK.
2. Click the General tab. The operating system appears as follows:
   • For a 64-bit version operating system: Microsoft Windows Server 2003 Enterprise x64 Edition appears under System.
   • For a 32-bit version operating system: Microsoft Windows Server 2003 Enterprise Edition appears under System.

Method 2

1. Click Start, click Run, type winmsd.exe, and then click OK.
2. In the details pane, locate Processor under Item. Note the value.
   • If the value that corresponds to Processor starts with x86, the computer is running a 32-bit version of the Windows operating system.
   • If the value that corresponds to Processor starts with EM64T or ia64, the computer is running a 64-bit version of the Windows operating system.