Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Friday, June 29, 2012

extracción de la lista raíz de terceros del archivo .CAB

Error en la extracción de la lista raíz de terceros del archivo .CAB actualizado automáticamente: con el error: Un certificado requerido no se encuentra dentro del periodo de validez cuando se ha realizado la comprobación con el reloj de sistema actual o con la marca de tiempo en el archivo firmado
Comprobar si la tarjeta de red tiene fallas ... usar otra  o actualizar los  controladores
Descargar WinSockFix 1.2 Manual de WinSockFix 1.2
Descomprimí y ejecuta WinSockFix de acuerdo a tu sistema, si tu sistema es Vista/Seven antes de ejecutarlo hace clic derecho y ejecutalo como administrador.

Ejecutá OTL.exe

 Realiza lo siguiente:

Ejecute OTL.exe:
  1. Haga click en el botón Limpiar.
  2. Se desintalarán las herramientas usadas durante el proceso de desinfección.
  3. Sea paciente mientras se realiza la desinstalación.
  4. Al terminar reiniciará el sistema

 Descarga Glary Utilities y lee el manual usalo para reparar y optimizar la PC.

En modo normal

Descarga la herramienta  ComboFix.exe y guárdala en el escritorio.
  • Desactiva temporalmente el Antivirus y/o Antispyware.
  • Cierra todas las ventanas abiertas.
  • Haz doble clic al archivo ComboFix.exe para continuar. Es Importante Importante instalar Recovery Console si es solicitado por ComboFix.
  • Cuando termine, generará un registro en C:\ComboFix.txt.
  •  *Nota* Mientras CF este trabajando no mover el mouse ya que pararía su proceso.
  •  *Nota* ComboFix puede reiniciar automáticamente el PC para completar el proceso de eliminación.
Atención!! No use ComboFix a menos que se le haya indicado específicamente en su mensaje por un integrante de nuestroStaff. Es una herramienta de gran alcance destinada por su creador a ser usada bajo la orientación y supervisión de un experto, no para uso privado. El uso de ComboFix incorrectamente podría generar problemas en su sistema. Por favor, lea las "Negaciones de la Garantía" de ComboFix.
  • Reinicia y pega el reporte de C:\ComboFix.txt en este mismo mensaje.




Source a
Source b
Save these instructions so you can have access to them while in Safe Mode.
Please click here to download AVP Tool by Kaspersky.

  • Save it to your desktop.
  • Reboot your computer into SafeMode.
    You can do this by restarting your computer and continually tapping the F8 key until a menu appears.
    Use your up arrow key to highlight SafeMode then hit enter
  • Double click the setup file to run it.
  • Click Next to continue.
  • Accept the Licence agreement and click on next
  • It will by default install it to your desktop folder.Click Next.
  • It will then open a box There will be a tab that says Automatic scan.
  • Under Automatic scan make sure these are checked.
  • Hidden Startup Objects
  • System Memory
  • Disk Boot Sectors.
  • My Computer.
  • Also any other drives (Removable that you may have)
Leave the rest of the settings as they appear as default.
  • Then click on Scan at the to right hand Corner.
  • It will automatically Neutralize any objects found.
  • If some objects are left un-neutralized then click the button that says Neutralize all
  • If it says it cannot be Neutralized then chooose The delete option when prompted.
  • After that is done click on the reports button at the bottom and save it to file name it Kas.
  • Save it somewhere convenient like your desktop and just post only the detected Virus\malware in the report it will be at the very top under Detected post those results in your next reply.

    Note: This tool will self uninstall when you close it so please save the log before closing it.
Source c
1. We need to reset system restore to prevent your computer from being accidentally reinfected by using some old restore point(s). We'll create fresh, clean restore point, using following OTL script:

  • Under the Custom Scans/Fixes box at the bottom, paste in the following:
  • Then click the Run Fix button at the top
  • Let the program run unhindered, reboot the PC when it is done
  • Post resulting log.
2. Now, we'll remove all tools, we used during our cleaning process
Clean up with OTL:
  • Double-click OTL.exe to start the program.
  • Close all other programs apart from OTL as this step will require a reboot
  • On the OTL main screen, press the CLEANUP button
  • Say Yes to the prompt and then allow the program to reboot your computer.
If you still have any tools or logs leftover on your computer you can go ahead and delete those off of your computer now.
3. Make sure, Windows Updates are current.
4. If any Trojan was listed among your infection(s), make sure, you change all of your on-line important passwords (bank account(s), secured web sites, etc.) immediately!
5. Download, and install WOT (Web OF Trust): It'll warn you (in most cases) about dangerous web sites.
6. Run Malwarebytes "Quick scan" once in a while to assure safety of your computer.
7. Run Temporary File Cleaner (TFC) weekly.
8. Download and install Secunia Personal Software Inspector (PSI): The Secunia PSI is a FREE security tool designed to detect vulnerable and out-dated programs and plug-ins which expose your PC to attacks. Run it weekly.
9. (optional) If you want to keep all your programs up to date, download and install FileHippo Update Checker.
The Update Checker will scan your computer for installed software, check the versions and then send this information to to see if there are any newer releases.
10. (Windows XP only) Run defrag at your convenience.
11. When installing\updating ANY program, make sure you always select "Custom " installation, so you can UN-check any possible "drive-by-install" (foistware), like toolbars etc., which may try to install along with the legitimate program. Do NOT click "Next" button without looking at any given page.
12. Read How did I get infected?, With steps so it does not happen again!:

100 bugs in Open Source C/C++ projects

This article demonstrates capabilities of the static code analysis methodology. The readers are offered to study the samples of one hundred errors found in open-source projects in C/C++. All the errors have been found with the PVS-Studio static code analyzer.
Picture 1

rundll32.exe info

What can I use instead of rundll32.exe to run 64-bit DLL?
There are two versions of the rundll32.exe program in 64-bit versions of Windows-family operating systems:
64-bit version: %WinDir% \System32\rundll32.exe
32-bit version: %WinDir% \SysWOW64\rundll32.exe
A 64-bit application can use the 64-bit version of rundll32.exe located in %WinDir% \System32\ to load 64-bit DLL. But 32-bit programs addressing %WinDir%\System32\ are redirected into %WinDir% \SysWOW64\ for compatibility purposes and therefore they will use the 32-bit version of rundll32.exe.
If you need to address the %WinDir%\System32 folder from a 32-bit program launched in a 64-bit Windows, you may use the virtual directory %windir%\Sysnative (redirection is not used for it) or use the Wow64DisableWow64FsRedirection function to disable the redirection mechanism.


Windows could not start the firewall

FIX: Windows could not start the Windows Firewall on Local Computer
In this article I’ll suggest a few tip to resolve this problem.
Step 1:
This step is standard to fix most of the Windows related issues. Yes we have to run SFC Scan to see if Windows could fix it by itself.
  1. Go to Start under search type in CMD
  2. Right Click and Run as administrator
  3. Then type in SFC /SCANNOW and press Enter.
For further details check this article System File Checker.
Step 2:
If there is permission related issue we have to give enough permission to those key.
  1. Go to Start under search type in Regedit
  2. If it prompt for administrator password type it in
  3. There go to Computer and Right click and Click on Export
  4. Under File name type in Regbackup and click on save
Then you have to give permission to the following keys:
  • Right click the key, and click Permissions.
  • Click on Add
  • In the “Enter the object names to select field, type “NT SERVICE\mpssvc“. Then click “Check name.”
2 FIX: Windows could not start the Windows Firewall on Local Computer
  • Click OK.
  • Then click on Add again
  • Type in Everyone then click OK.
  • Then select the account which appears in the list, and add the proper permission for it.
  • Under the Allow section put a check mark on Full control
3 FIX: Windows could not start the Windows Firewall on Local Computer
  • When this is done, click OK and restart your Computer.
If you’re getting access denied, Turn Off UAC via your Control Panel and try it again.
Step 3:
Sometime Malware infections can cause the service to fail. So I would recommend that you run a full scan of your anti-malware. You may also download a second stand-alone scanner like freeware Malwarebytes, Emsisoft or the new Microsoft Safety Scanner and run a complete system scan in Safe Mode, to get a second opinion.
Step 4:
If your system fails to find any infection the last thing left to do is to run a Repair Install on Windows most one or more system files might have corrupted. Follow this post on how to run a Repair Install on Windows 7.
These links may also interest you:
If you have liked this post, you might want to check out some more, on topics like , .

About ShyamS@TWC

Shyam aka “Captain Jack” is a Microsoft MVP and a Windows Enthusiast whose area of expertise is Crash Dump Analysis and Advanced Windows troubleshooting. He has developed Windows based Tools like SF IE Restorator for troubleshooting Internet Explorer issues and SF Diagnostic Tool for collecting Crash dump files for troubleshooting purpose. He blogs at

Monday, June 25, 2012

GEARAspiWDM.sys incompatible

Se bloqueó la carga de \SystemRoot\SysWow64\Drivers\GEARAspiWDM.sys por una incompatibilidad con este sistema
GEAR Software disc copying service installed with iTunes and other CD / DVD burning software file.
The process CDRom Class Filter Driver or CD/DVD Class Filter Driver or CD DVD Filter or Filter Driver for (version 2k and XP) or GEAR ASPI Filter Driver or iTunes
belongs to the software GEAR.wrks or iTunes or GEAR CDRom Filter or GEAR ASPI Filter Driver or CD DVD Filter or GearDrvs or Norton Ghost or GEAR driver installer for (version x86) or GEARAspi by GEAR Software (
Description: GEARAspiWDM.sys is located in the folder C:\Windows\System32\drivers. Known file sizes on Windows 7/XP are 14,408 bytes (34% of all occurrence), 15,664 bytes and 14 more variants.
The driver can be started or stopped from Services in the Control Panel or by other programs. The program is not visible. GEARAspiWDM.sys is not a Windows system file. File GEARAspiWDM.sys is a Verisign signed file. The file has a digital signature. There is no detailed description of this service. You can uninstall this program in the control panel. GEARAspiWDM.sys seems to be a compressed file. Therefore the technical security rating is 9% dangerous, however also read the users reviews.
If you run into problems with GEARAspiWDM.sys, you can also visit the Apple support page, update the program to the latest version or uninstall iTunes or GEAR 32bit Driver Installer software via Windows Control Panel/Add or Remove Programs (Windows XP) or Programs and Features (Windows 7/Vista).

An inside look at Apple's sneaky iTunes 8 upgrade,_removing,_64_bit_versions,_etc
OTL by OldTimer is like HijackThis — on steroids. OTL scans your system for malware, and produces detailed logs. It’s primarily a malware diagnostic tool, but has advanced removal abilities. It is used alone, or with other tools to  remove malware completely.
OTL is a flexible, multipurpose, diagnostic, and malware removal tool. It also has some curative ability.

Modern malware will hide all, or most of itself from detection in a HijackThis log. HijackThis (HJT) is very popular, and if malware can hide from it, it has a better chance of survival. But mostly HJT fails to detect malware because, with the exception of some bug fixes and minor updates, it has not been updated in a long time.
A brief history lesson… Merijn Bellekom is the creator and developer of HJT. He sold it to Trend Micro in March, 2007. Trend added an “Analyze This” button to collect data, updated HJT to be compatible with Windows Vista/7, and fixed a few bugs. While malware has evolved much since March 2007, HJT has not.
The need for a more powerful diagnostic tool that is updated often spurred developers to create their own pseudo versions of HJT. Among them DDS by sUBs, RSIT by random/random, and of course OTL by OldTimer Of them, OTL is the most robust, and has the most advanced ability to remove malware.
The most common use for OTL is to post a log in a malware removal forum for analysis by an expert. However, it’s also a good idea to run an OTL log as a baseline before running any advanced removal tools. In the event those tools don’t completely remove the malware, the OTL log can offer valuable information to remove the remainder.
A complete and detailed OTL tutorial has just been made public. It has been available to experts and forum helpers for some time. While most people will never use all the features of OTL, or only use it to create a log, others will find all the information offered in the tutorial helpful.
One of the most powerful features of OTL is its ability to run custom scans. This allows the log output to be modified very easily, and quickly adapt to the latest malware threats. An always up-to-date custom scan recommendation can be found in our Malware Cleaning Guide.
Following is a “Quick Start” Guide to creating an OTL log:
  1. Simply Download OTL.exe (alternate mirror) to your desktop, download folder, or other convenient location. In the event malware is blocking OTL.exe from running, alternate versions are available as either .com (mirror), or .scr (mirror).
  2. OTL doesn’t need to be installed, simply run it by clicking the icon (approve any UAC warnings on WIndows Vista or 7).OTL_icon
  3. First paste custom scan information (if any). Second, click the “Quick Scan” button.
4. When the scan completes, it will open two windows in Notepad. OTL.txt, and Extras.txt. They are saved in the same location as OTL.exe. Copy the contents and paste to a forum for help, or if you’re an advanced user and have read the tutorial, analyze the output.

Sunday, June 24, 2012

Acronis True Image Echo + Universal Restore

Acronis True Image Echo Enterprise Server v. 9.7.8398
Acronis True Image Enterprise Server es más efectivo con el complemento Acronis Universal Restore.
La versión actualizada de Acronis True Image Echo Enterprise Server incluye características y funciones nuevas y mejoradas, entre las cuales están las siguientes:
Compatibilidad con todas las plataformas principales de virtualizaciónLos productos Acronis True Image Echo ya son compatibles con las máquinas virtuales y los formatos de archivo de Citrix® XenServer, sumándolo a la compatibilidad ya existente, y que se había incluido recientemente, con las plataformas VMware®, Microsoft® y Parallels®. Esta actualización proporciona a los usuarios de Acronis la libertad de elegir entre plataformas de virtualización sin tener que aventurarse fuera del ámbito de las copias de seguridad y recuperación de Acronis.
Copia de seguridad de destino dualLos clientes pueden realizar una copia de seguridad de un servidor en una imagen en dos ubicaciones, incluyendo una unidad de red compartida o Acronis Secure Zone. Las copias de seguridad de destino dual ayudan a proteger tanto los servidores físicos como los virtuales de fallos de software y pueden ser su salvación en caso de que el equipo sufra daños físicos.
Integración de Acronis Recovery for Microsoft ExchangeLos usuarios de Acronis® Recovery™ for Microsoft Exchange ya pueden acceder a las funciones específicas de Exchange desde Acronis True Image Echo Management Console. Esta característica acelera las restauraciones o las migraciones de servidores Exchange, incluso en máquinas que deben restaurarse desde cero, al reducir la carga de trabajo de gestión general en el entorno Exchange.
Para sistema de recuperación de desastres y migración en los dos entornos físicos y virtuales, Acronis ® True Image Echo Server para Windows ofrece una mayor flexibilidad y valor para las pymes y oficinas remotas / oficina. ¿Está ejecutando una organización con la misión crítica de Microsoft ® Windows ® servidores en un solo lugar y la escasez de personal de TI? ¿Cuánto negocio usted perdería si estos servidores bajó? Acronis ® True Image Echo ™ Server para Windows ofrece una protección del sistema y la recuperación de servidores de Windows y le permite volver a las empresas y minimizar el tiempo de inactividad. Acronis True Image Echo Server para Windows le permite crear una exacta imagen de disco de servidor de Windows, incluyendo el sistema operativo, bases de datos y aplicaciones; migrar sus sistemas entre los servidores físicos y virtuales rápida y fácilmente.
Después de una caída del sistema Acronis True Image Echo Server para Windows le permite llevar a cabo todo un servidor restablecer en tan sólo unos minutos, no horas o días. Restauración completa del sistema se puede realizar a un sistema existente oa un nuevo sistema con diferente hardware, así como a un servidor virtual. Basado en exclusiva tecnología Acronis Drive Snapshot, Acronis True Image Echo Server para Windows le permite crear copias de seguridad sin interrumpir las operaciones del servidor, proporcionando 24 x 7 x 365 disponibilidad.

Add-ons / Acronis ® Universal Restore
Acronis ® Universal Restore le permite devolver a hardware diferente o una máquina virtual, que completa la recuperación de desastres. Acronis ® Universal Restaurar prepara incluso para los más imprevistos. Con Acronis Universal Restore, sistema completo de recuperación se puede lograr a partir de una imagen, sin la reinstalación del sistema operativo, aplicaciones o cualquier individuo o reconfiguraciones de archivos y carpetas restauradas. Dado que Acronis True Image Echo Enterprise Server crea una imagen transportable que desvincula los datos del hardware subyacente, la recuperación puede ser aplicado a un sistema existente, a un nuevo sistema con hardware diferente, o para un servidor virtual.

Puede restaurar una imagen a un nuevo sistema en 5 sencillos pasos:
• Paso 1: Inicie su sistema de sustitución con el arranque de los medios de comunicación que ha creado y seleccione en la recuperación de Acronis ® True Image menú
• Paso 2: Seleccione la imagen para restaurar y el Acronis ® Universal opción Restaurar
• Paso 3: Restaurar Acronis ® Universal inicia el proceso de restauración
• Paso 4: Acronis ® Universal Restaurar detecta el hardware e instala los controladores
• Paso 5: La máquina se reinicia

Principales características:

»Restaurar un servidor Windows en cuestión de minutos después de cualquier acontecimiento imprevisto
»Acronis Universal Restore - restituir a hardware diferente o en un servidor virtual
»Imagen de copia de seguridad de cifrado
»De múltiples instantáneas de volumen - Permite que usted copias de seguridad de datos ubicados en varios volúmenes
»Convertir archivos de imagen a VMDK o VHD para el instante de virtualización
»Dinámica del disco
»Más amplio de compatibilidad de hardware, incluidas las unidades de apoyo de SAS
»Mejorar la programación y Notificaciones
»Monte imágenes en lectura / escritura y el modo de aplicar los cambios directamente
»Arrancar desde una imagen utilizando Acronis ® Active Restaurar
»Mejora de la base de datos de apoyo
»De verificación automática de la imagen
»Copias de seguridad diferenciales - Disminuye el número de copias de seguridad a manejar
»Archivo y carpeta de copias de seguridad basadas en
»Excluir archivos de copias de seguridad
»Registro de sucesos de Windows y soporte SNMP
»Scripts antes / después de las copias de seguridad
»A la regulación de control de velocidad de escritura del disco duro de red y uso de ancho de banda
»Crear CDs con imágenes de inicio, paquetes PXE y medios de comunicación de arranque de recuperación ISOs

Saturday, June 23, 2012

Free Copy Protection for HTML Web Pages

Put this code in your HTML page
Try it out by right clicking on this document. Use Ctrl-C to copy the code snippet as the right click will not work.

This code snippet is really easy as you just embed it within the HTML that you wish to protect. I have had people asking me how to protect their HTML and JPEG pictures on their web sites. This is one method to help protect your web pages and pictures but it is pretty hard to completely protect everything.

HALs and halmacpi.dll

Error restoring a True image backup to a new hardware:
file halmacpi that is required for installation of device multiprocessor ACPI  id:(standard pc) in windows XP professional  can not be found
SysPrep Guide: Hardware Abstraction Layer (HAL)
The hardware abstraction layer (HAL) is a kernel level driver that provides an interface between the operating system and the system architecture. There are several HALs that Windows can use and they impact available features and performance depending on which systems they are used on. You can find the list below and some comments about them. Some of the HALs allow Windows to work on very different hardware, but now that x86 is the universal architecture for Windows computers the choice for a HAL is simplified a great deal. I will go into more detail after you browse through the HALs below.
 Available Hardware Abstraction Layers (HALs) 
Standard PC
DLL: hal.dll
Kernel: ntoskrnl.exe
PAE: ntkrnlpa.exe
This is the most primitive HAL and it supports all computers that are compatible with Windows 2000 and Windows XP. It does not support the advanced the programmable interrupt controller (APIC) architectures and does not provide APCI features including the configuration management and the advanced power management. You can use this on any computer, but at the cost of performance and features. More than likely you will never use this HAL.
Standard PC with C-Step i486 This is a primitive HAL that provides support for C-stepping on 486 processors. I am not sure what that is, but I am pretty sure it's old and I severely doubt you will ever use it.
Advanced Configuration and Power Interface (ACPI) PC
DLL: halacpi.dll
Kernel: ntoskrnl.exe
PAE: ntkrnlpa.exe
I find that this HAL is the best selection for an image that you want to be compatible on as many computers as possible. It should be noted that multiprocessor computers can use this HAL, however they will only make use of a single processor. This HAL can also be used with hyperthreading without any problem, but it will effectively disable hyperthreading because it is only designed for a single processor system.
ACPI Uniprocessor PC
DLL: halaacpi.dll
Kernel: ntoskrnl.exe
PAE: ntkrnlpa.exe
This HAL is designed for single processor computers that are not compliant with the multiprocessor system specficiations. This HAL will run on computers that are fairly new systems, such as all Pentium 4 based systems. However, I have found problems with duplicating this HAL onto some older Pentium 3 based systems. You can read about the ACPI standards by reading this and you can read about the core architecture modules here.
ACPI Multiprocessor PC
DLL: halmacpi.dll
Kernel: ntkrnlmp.exe
PAE: ntkrpamp.exe
This HAL is designed for multiprocessor computers that are not compliant with the multiprocessor system specficiations. It is rumored that you will receive about a 15% performance gain from using this HAL over the standard ACPI HAL when you have a hyperthreaded system, but I have not tested this yet. You can read about the ACPI standards by reading this and you can read about the core architecture modules here.
MPS Uniprocessor PC
DLL: halapic.dll
Kernel: ntoskrnl.exe
PAE: ntkrnlpa.exe
This HAL is designed for multiprocessor systems that have a single processor. You can read about the MPS standards by reading this. As far as I know this is only used by older Xeon based systems with a single processor.
MPS Multiprocessor PC
DLL: halmps.dll
Kernel: ntkrnlmp.exe
PAE: ntkrpamp.exe
This HAL is designed for multiprocessor systems that have multiple processors. You can read about the MPS standards by reading this. As far as I know this is only used by older Xeon based systems with multiple processors.
Compaq SystemPro Multiprocessor or 100% Compatible PC Designed for Compaq SystemPro multiprocessor systems. You will most likely never use this HAL.

Choosing a HAL

Control Panel -DEvice Manager -Computer -ACPI Multiprocessor PC -Driver -update driver
That should do it to make it a uniprocessor PC again. But I am not sure if that cures the sluggish behavior as it may not be the only cause.
change the acpi in the bios back to disabled/off?
HAL options after Windows XP or Windows Server 2003 Setup
should tell you how to force a reinstall of windows with a differetn hal.
Another way that may work is to create another hardware profile and get it to boot to that at the start, it should then auto detect everything and you'll have a backup profile just in case
by the way, you did try the normal method of going to
Device Manager -> ACPI multiprocessor PC and then using the update feature (tried selecting your own ? Advanced -> let me choose...). Since that way should work.
Windows won't start (I think) if you just delete those files. The feature to change the HAL in Device Manager in XP is deliberately disabled by Microsoft - it works for previous versions of Windows but not for XP.
See troubleshoot HAL from Microsoft. Below you'll find the names of the relevant files for easier access.
You need to replace three files in the system32 folder then restart Windows. The best set of files can be found in the cab files from the XP redistributable SP2 (yes I know it's big) found at Microsoft. You can also use the files (already expanded) found in Windows/ServicePackFiles/i386 - this would be best if you have that folder and it contains the proper files.
It is still problematic to change these 3 files because they can have been updated by regular Windows updates. If you get Windows running after you change these 3 files it is best to manually run the Windows update process to see if MS will detect if these 3 files need further updating.
The article refers to Win2000 but it should apply equally to XP.
Folder winnt/system32 is changed to Windows/system32 for XP.
You can change these filenames from the Recovery Console - at the command prompt (at least I think you can). You need to be able to run Recovery Console from a Win install CD or have installed Recovery Console into Windows. Be sure you can successfully run the Recovery Console before you begin. Windows (online) help file has more info on how to run it or install it.
To make this easier you need to find the files with your operating copy of Windows first and put the files in place in the system32 folder with a changed name such as, you'll be able to find them quicker. Be sure you know how to get the files extracted/expanded out of the .cab first, either with a built-in extractor such as that in the 7-zip app or by using the Windows provided extract/expand utility. I mention this because it is possible to end up with an un-expanded copy of the file. Check the extracted files with File|Properties in Explorer - good files will show the version info.
Just to be safe, copy your existing 3 files and keep them in case this process fails.
An alternative to hunting down the files from the cab files is just to find another running version of Windows with the uniprocessor files and then just copy them (like on a floppy).
The following is extracted from the url above:
 2. After you log on to your computer, from the %SystemRoot%\System32 folder of your original Windows 2000 installation,
use the command console to copy and rename the following files as noted in the following lists.
First determine which HAL and kernel files your computer requires by using the following list of supported computer types:
NOTE: Those marked with an asterisk character are Standard computer types (non-ACPI).
(You need only one of the following!)

i386 source file: i386\\halmacpi.dll
Computer type: ACPI Multiprocessor PC
Copy to this folder: winnt\System32
Rename to this file name: hal.dll

i386 source file: i386\\halaacpi.dll
Computer type: ACPI Uniprocessor PC
Copy to this folder: winnt\System32
Rename to this file name: hal.dll

i386 source file: i386\\halacpi.dll
Computer type: Advanced Configuration and Power Interface (ACPI) PC
Copy to this folder: winnt\System32
Rename to this file name: hal.dll

i386 source file: *i386\\halsp.dll
Computer type: Compaq SystemPro Multiprocessor or 100% Compatible
Copy to this folder: winnt\System32
Rename to this file name: hal.dll
i386 source file: *i386\\halapic.dll
Computer type: MPS Uniprocessor PC
Copy to this folder: winnt\System32
Rename to this file name: hal.dll
i386 source file: *i386\\halmps.dll
Computer type: MPS Multiprocessor PC
Copy to this folder: winnt\System32
Rename to this file name: hal.dll
i386 source file: *i386\\hal.dll
Computer type: Standard PC
Copy to this folder: winnt\System32
Rename to this file name: hal.dll
i386 source file: *i386\\halborg.dll
Computer type: SGI mp
Copy to this folder: winnt\System32
Rename to this file name: hal.dll

3. As indicated in the following table, copy all the appropriate kernel files common for your system (Uniprocessor vs. Multiprocessor)
and the appropriate HAL file based on your computer supported computer type from the Windows 2000 CD-ROM (i386\
or installed service pack to the corresponding folder listed in the table under your original Windows 2000 installation,
and then rename them (if required) to Ntoskrnl.exe and Hal.dll, respectively.
Common Multiprocessor kernel files Copy to the following directory Rename to the following filename
i386\\ntkrnlmp.exe winnt\System32 ntoskrnl.exe
i386\\ntkrpamp.exe winnt\System32 ntkrnlpa.exe
(following 4 files are the same - don't need to copy )
(i386\\kernel32.dll winnt\System32 kernel32.dll )
(i386\\ntdll.dll winnt\System32 ntdll.dll )
(i386\\win32k.sys winnt\System32\drivers win32k.sys )
(i386\\winsrv.dll winnt\System32 winsrv.dll )
Common Uniprocessor kernel files Copy to the following directory Rename to the following filename
i386\\ntoskrnl.exe winnt\System32 ntoskrnl.exe
i386\\ntkrnlpa.exe winnt\System32 ntkrnlpa.exe
(following 4 files are the same - don't need to copy )
(i386\\kernel32.dll winnt\System32 kernel32.dll )
(i386\\ntdll.dll winnt\System32 ntdll.dll )
(i386\\win32k.sys winnt\System32 win32k.sys )
(i386\\winsrv.dll )
So, for computer type: ACPI Uniprocessor PC
i386\\halaacpi.dll -> windows\System32\hal.dll
i386\\ntoskrnl.exe -> windows\System32 ntoskrnl.exe
i386\\ntkrnlpa.exe -> windows\System32 ntkrnlpa.exe
The additional 4 files may or may not need to match, you may need to extract them also from the SP2 cab file. This is usually unnecessary.
Good luck! 
I think you are suggesting that Windows XP should detect that the CPU is now a single processor and then install and use the proper HAL.
I'll repeat: that function (reinstalling a different HAL) is deliberately disabled in XP. The only way to change the HAL is by manually installing the proper fileset or by wiping the disk and doing a full install. WinXP will never change the currently installed HAL no matter what CPU is detected and no matter what the BIOS says.
The Compaq BIOS may well be dumbed down and may be partly what has led to the current problem. While the motherboard may have been originally intended to support a multiprocessor, Compaq may have deliberately disabled that feature on the board supplied with that particular computer package in order to save costs.
Any XP install CD can be used to install XP. All that changes is the XP key and the key is not recorded on the disk. You can borrow any XP install CD and use it with your genuine XP key. You can use a 'burned' CD copy as well as an original CD. You do not violate your license by using a different XP install CD no matter the source.
Then how come I can select different HAL's if I do it on my Windows XP computer ?
And in the link I gave some posts up it says WindowsXP can (a limited choice in WinXP as opposed to any in Win2K)

You cannot switch between ACPI and non-ACPI in device manager in WinXP.

Extracted from the MS post:
4. On Windows XP and later versions, the ACPI Uniprocessor HAL and the MPS Uniprocessor HAL recognize the existence of more than one processor and report the MP ID. Plug and Play detects that the computer devnode's hardware ID list has changed and moves the devnode back through the "found new hardware" detection process. Therefore, when you add a second processor, the MP files (HAL and kernels) are automatically installed, and you do not have to manually update the driver in Device Manager
This has just not been my experience - XP SP2 will not do what item #4 says that it will. I believe that the article applies to (original release) vanilla XP and that XP SP2 changes this behavior - such that SP2 disables that feature more or less completely. I can testify that when I changed my processor from single to dual, XP SP2 did NOT change the HAL automatically nor was there an option to do so in Device Manager.
References to 'forcing' a particular HAL are only relevant when installing a fresh copy of Windows and possibly relevant when doing a 'repair' install.
There may still exist the ability to change the HAL if you started with a current 'Standard PC' HAL, although I can't verify that.
You do need WinXP SP2 for dual core's to work properly.
It a very current KB (Jul 2006) and is in refrence to all WinXP and Win2003.
Also I believe Bad Penguins initail try at running the X2 auto changed. It also auto detect for many other people. You do need WinXP SP2 for dual core's to work properly.
Though we are onto single cores now :-)
Bad Penguin, on the off chance you could try (if not already) putting AMD latest Sempron driver on from,,30_182_871_11686,00.html
The the other way is to setup boot.ini to load with a different HAL(used for testing normaly) though often used for this purpose: 
SysPrep Guide: Hardware Abstraction Layer (HAL)
amdcpusetup.exe is known as Microsoft® Windows® Operating System and it is developed by MS .============================
Microsoft Knowledge Base Article - Q309283
El Administrador de dispositivos de Windows XP y la lista del Administrador de dispositivos de Windows Server 2003 limitaban las opciones para cambiar el tipo de HAL al hacer clic en Actualizar controlador. El Administrador de dispositivos de Microsoft Windows 2000 le permite seleccionar cualquier tipo de HAL. Si selecciona una HAL incorrecta, es posible que no pueda iniciar Windows 2000 o que tenga otros problemas. Aunque las selecciones son limitadas, sólo debe cambiar la HAL si sabe con seguridad que la HAL seleccionada funciona en su sistema. Las opciones que se presentan aquí se sabe que son compatibles con la mayoría de los sistemas. No obstante, algunos sistemas pueden experimentar problemas.

Al instalar las siguientes HAL en un equipo basado en Windows XP o en Windows Server 2003, aparecen las siguientes opciones de HAL del Administrador de dispositivos:

"PC estándar ", HAL PIC no compatible con ACPI (Hal.dll)
PC estándar

"Equipo monoprocesador MPS", HAL UP APIC no compatible con ACPI (Halapic.dll)
PC estándar
Equipo monoprocesador MPS
Multiprocesador MPS

"Equipo multiprocesador MPS", HAL MP APIC no compatible con ACPI (Halmps.dll)
PC estándar
Multiprocesador MPS
"Interfaz avanzada de configuración y energía (ACPI)", HAL PIC ACPI (Halacpi.dll)
PC estándar
Equipo con Interfaz avanzada de configuración y energía (ACPI)

"Monoprocesador ACPI de PC", HAL UP APIC ACPI (Halaacpi.dll)
PC estándar
Equipo con Interfaz avanzada de configuración y energía (ACPI)
Monoprocesador ACPI
Multiprocesador ACPI

"Equipo multiprocesador ACPI", HAL MP APIC ACPI (Halmacpi.dll)
PC estándar
Equipo con Interfaz avanzada de configuración y energía (ACPI)
Multiprocesador ACPI
Multiprocesador MPS


  1. Un síntoma común al implementar la imagen incorrecta en un equipo es que la imagen de Sysprep deja de responder al reiniciar o informa del mensaje de error siguiente:
    Stop 0x0000007b
  2. Si se fuerza una HAL incorrecta durante la instalación o al utilizar una imagen de preparación del sistema (Sysprep), sólo podrá ver la lista correcta de HAL si realiza una nueva instalación de Windows XP o de Windows Server 2003. No puede cambiar a una HAL que no aparezca en el Administrador de dispositivos.
  3. El Administrador de dispositivos no permite el cambio de una HAL no compatible con ACPI a una HAL ACPI. Debe llevar a cabo una instalación nueva de Windows XP o de Windows Server 2003 para realizar este tipo de cambio. Cambie sólo de una HAL ACPI a una HAL no compatible con ACPI para solucionar problemas.
  4. En Windows XP y en versiones posteriores, la HAL monoprocesador ACPI y la HAL monoprocesador MPS reconocen la existencia de más de un procesador e informan del Id. del MP. Plug and Play detecta que la lista de identificadores de hardware de devnode ha cambiado y mueve el devnode hacia atrás a través del proceso de detección "Nuevo hardware encontrado". Por tanto, al agregar un segundo procesador, los archivos de MP (HAL y núcleos) se instalan automáticamente y no es necesario actualizar el controlador manualmente en el Administrador de dispositivos.
  5. Microsoft no admite la ejecución de una HAL distinta de la que instala normalmente el programa de instalación de Windows en el equipo. Por ejemplo, no se admite la ejecución de una HAL PIC en un equipo APIC. Aunque puede parecer que esta configuración funciona, Microsoft no la ha probado y es posible que tenga problemas de rendimiento e interrupciones. Microsoft tampoco proporciona soporte técnico para intercambiar los archivos que usa la HAL con el fin de cambiar manualmente los tipos de HAL.
  6. Microsoft recomienda que sólo se utilice el intercambio de HAL para solucionar problemas de hardware o de otro tipo.
  7. Al crear una imagen Sysprep, la imagen debe contener el tipo de HAL correcto para el equipo de destino. En la lista siguiente se describen los equipos en los que se puede implementar una imagen Sysprep concreta según el tipo de HAL del equipo de origen:
    • Puede implementar una imagen Sysprep creada en un equipo que utiliza PC estándar, HAL PIC no compatible con ACPI (Hal.dll) en un equipo que utilice los tipos de HAL siguientes:
      • PC estándar, HAL PIC no compatible con ACPI (Hal.dll)
    • Puede implementar una imagen Sysprep creada en un equipo que utiliza Equipo con Interfaz avanzada de configuración y energía (ACPI), HAL PIC ACPI (Halacpi.dll) en un equipo que utilice los tipos de HAL siguientes:
      • Equipo con Interfaz avanzada de configuración y energía (ACPI), HAL PIC ACPI (Halacpi.dll)
    • Puede implementar una imagen Sysprep creada en un equipo que utiliza Equipo monoprocesador MPS, HAL UP APIC no compatible con ACPI (Halapic.dll) en un equipo que utilice los tipos de HAL siguientes:
      • Equipo monoprocesador MPS, HAL UP APIC no compatible con ACPI (Halapic.dll)
      • Equipo multiprocesador MPS, HAL MP APIC no compatible con ACPI (Halmps.dll)
    • Puede implementar una imagen Sysprep creada en un equipo que utiliza Equipo multiprocesador MPS, HAL MP APIC no compatible con ACPI (Halmps.dll) en un equipo que utilice los tipos de HAL siguientes:
      • Equipo multiprocesador MPS, HAL MP APIC no compatible con ACPI (Halmps.dll)
      • Equipo monoprocesador MPS, HAL UP APIC no compatible con ACPI (Halapic.dll)
    • Puede implementar una imagen Sysprep creada en un equipo que utiliza Monoprocesador ACPI de PC, HAL UP APIC ACPI (Halaacpi.dll) en un equipo que utilice los tipos de HAL siguientes:
      • Monoprocesador ACPI de PC, HAL UP APIC ACPI (Halaacpi.dll)
      • Equipo multiprocesador ACPI, HAL MP APIC ACPI (Halmacpi.dll)
    • Puede implementar una imagen Sysprep creada en un equipo que utiliza Equipo multiprocesador ACPI, HAL MP APIC ACPI (Halmacpi.dll) en un equipo que utilice los tipos de HAL siguientes:
      • Equipo multiprocesador ACPI, HAL MP APIC ACPI (Halmacpi.dll)
      • Monoprocesador ACPI de PC, HAL UP APIC ACPI (Halaacpi.dll)
Nota: actualmente, las opciones del Administrador de dispositivos no muestran una versión de APIC de la HAL al cambiar la HAL en un sistema APIC. Aunque la HAL PIC que está instalada puede funcionar, puede seleccionar la versión de APIC preferida después de instalar una revisión para los equipos que ejecuten Windows Server 2003 con el Service Pack 1.

Para obtener más información acerca de la revisión para el Service Pack 1 de Windows Server 2003, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base:
923425  No puede bajar de nivel a una capa de abstracción de hardware que esté configurada para utilizar una controladora programable avanzada de interrupciones de un solo procesador cuando intenta cambiar el tipo de equipo utilizando el Administrador de dispositivos en Windows Server 2003
299340  Cómo forzar una Capa de abstracción de hardware durante una actualización o una instalación nueva de Windows XP
The article referenced above Q309283 states the following:
HAL Options After Windows XP or Windows Server 2003 Setup
When you install the following HALs on a Windows XP-based or Windows Server
2003-based computer, the following device manager HAL options appear: (List
of 5-6 HAL types including the following:)
"ACPI Multiprocessor PC", ACPI APIC MP HAL (Halmacpi.dll)
Standard PC
Advanced Configuration and Power Interface (ACPI) PC
ACPI Multiprocessor
MPS Multiprocessor
Several choices are listed. The ACPI MP PC HALL noted above is my interest.
EACH HAL type listed has a unique .dll file associated with it.
The ACPI Mulitprocessor PC, ACPI APIC MP HAL above is 'Halmacpi.dll.'
Note: A Standard PC HAL is Hal.dll
Question: After a clean install of XP and forcing the ACPI MP PC HAL type
listed above, the XP Device Manager Driver Information indicates that
Halmacpi.dll is NOT install. Rather Hal.dll is installed. The Hal.dll is
installed when XP, again during a clean install, is allow to read the
system and select the correct HAL.

Concern 1 : IS the KB article incorrect? IF specific .dll files associated
with specific HALs are listed why are they not installed?
BIG Concern : Could it be that the .dll file installed has something to do
with WindowsXP NOT recognizing certain devices associated with the Intel
875P chipset; namely the link between the "Processor and the I/O
Controller" OR the link of "Processor to I/O Memory Interface - 257E"

Acronis Drive Monitor

Determine the health of your hard disks
There are three unavoidable certainties in life: Death, Taxes and Hard Disk Drive Failures.
Acronis does not have a solution for the first, we leave that to a higher authority; however, we can make sure that your financial records, photos, videos and other items of sentimental or monetary value are protected so that you can cherish the memories and pay your taxes on time!
Computers have become a necessary part of our daily lives and we have become dependent on instant access to the data stored on the hard drives inside our PCs. Just about everyone has either experienced a disk failure or knows someone that did. It's unavoidable as all disks eventually fail. This is why Acronis developed Acronis Drive Monitor as a free tool for the community at large.
Early warning to save your data
Acronis Drive Monitor can help predict when a hard drive is about to fail, giving you the chance to backup your data before disaster strikes. When Acronis Drive Monitor identifies a problem, it generates an email or onscreen alert describing the specific finding. It offers a simple and easy to understand explanation of the alert guiding you to the steps you need to take to remedy the issue. A color coded summary provides an overview of the disk's health at a glance and weekly reports summarize the findings.
Integrates with Acronis Home products for greater data safety
Users of the latest versions of Acronis True Image Home 2012 and Acronis Backup and Security 2011 PC backup and recovery software can take advantage of Acronis Drive Monitor's ability to trigger an immediate, automated backup if any disk shows signs of imminent failure.

* Click here to learn more about how Acronis Drive Monitor integrates with the latest Acronis Home and Business products.

Acronis Snap Deploy for PCs

TechRepublic web site
Imaging is common practice in many IT shops today and has been around for quite some time. The concept of creating a master system and using an image of that system to quickly get other systems to your organization’s standard configuration (or a custom configuration) is a great help to the IT staff in charge of desktop systems.
The concept is the same regardless of the size of organization or the application you choose to manage your images. Recently I started down the path of imaging in my current organization and came across Snap Deploy from Acronis and found it to be very user friendly and straight forward. In this spotlight I am going to look at Acronis Snap Deploy for PCs which is used solely to image workstations.
To use Acronis Snap Deploy for PCs you will need to create a master image of a system. This computer should contain all of the standard applications used by your organization to create a “golden image” for use company-wide.
Creating an image for mass deployment is very simple. The Snap Deploy management console (or bootable media) allows you to create images online and offline when the master system is configured as needed. Using offline mode, when booted to Acronis media, simply select the location to store your image and the application handles the rest.
Supported operating systems:
  • Windows 98
  • Windows 2000
  • Windows ME
  • Windows XP
  • Windows Vista
  • Windows 7
Who’s it for?
Acronis Snap Deploy is for busy systems administrators or IT departments who need to get new workstations provisioned quickly for new staff or refresh older PCs with minimal effort. The Snap Deploy deployment process greatly reduces repeat system deployments and can be configured to image multiple systems all at the same time or work through a list of waiting PCs one at a time.
What problem does it solve?
Repetitive installations are very tedious and time-consuming to complete. Consider the following example:  the sales department in an organization brings on three new field representatives who will be starting in a week. When they come in for orientation they will need laptops configured with the organization’s sales application and email. For an IT department with multiple staff or nothing going on, it would be no problem to individually build these systems, but with constant support and questions, the workday of the IT department is rarely so calm.
Snap Deploy alleviates this by allowing a master image to be built containing all the applications needed by the sales team. When the image is ready, the workstations can be targeted by booting from media or a PXE server (which ships with the application). Once booted ,the PC will connect to a host system which handles the deployment; the administrator simply creates a template for sales, which tells the server where the master image is and includes any storage drivers needed. Once the deployment begins, the IT staff is free to move on to other tasks.
Standout features
Snap Deploy allows templates to be saved on the deployment server. These templates contain the information needed to get the deployment finished. The following are specified in a template:
  • Image location
  • Storage drivers
  • Additional files to copy to the target system
  • Network credentials for joining the domain
  • Multicast/Unicast deployment: Allows the deployment to use all available switch bandwidth to speed up deployment when in multicast mode. Unicast mode allows the deployment to communicate directly with the target system at rate determined by the administrator.
Note: Be very careful when using Multicast mode. If you are imaging across a production network, using this method may cause other nodes within your environment to drop.
Additional File Copy: This setting allows you to specify additional files that should be copied to the target system as part of the imaging process. When a file is pulled from the network, it is copied following the application of the image to a directory you specify.
Scheduled or event driven image deployment: In addition to the “do it right now” manual deployment option, you can configure Snap Deploy to push images out on a set schedule, so a system can be imaged overnight and ready for login the next morning. You can also use event driven image deployment so an image can be pushed to the target system following an event, in which case a system would connect to deployment server and wait. Once a preconfigured number of systems connect (or the time out value is reached) the deployment begins.