intel D945GCLF BIOS recovery

Page 1 - The Battle of Mini-ITX Platforms 
Page 2 - Intel BOXD945GCLF Motherboard 
http://www.legitreviews.com/article/757/3/

D945GCLF - Download Center

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18947&lang=eng&OSVersion=OS%20Independent&DownloadType=BIOS

Recovery BIOS Update [LF0278P.BIO] - A .BIO file to be used for BIOS recovery process, regardless of operating system. In the unlikely event that a BIOS update is interrupted, it is possible the BIOS may be left in an unusable state. Use the Recovery BIOS update to recovering from this condition. It requires a blank CD or USB flash device.

ISO Image BIOS Update [LF0278P.ISO] - Bootable ISO image BIOS update; this is the recommended method to update the BIOS on systems running Linux*. It requires a blank CD and a read/writeable CD drive.

Iflash BIOS Update / Integrator Toolkit BIOS Files [LF94510J.86A.0278.BI.ZIP] - A DOS-based utility to update the BIOS regardless of operating system. It requires a CD or a USB flash device.  This download also provides the necessary files for Intel® Integrator Toolkit.  Support and FAQs for Intel® Integrator Toolkit areavailable here.

Express BIOS Update [LF94510J.86A.0278.EB.EXE] - Self-extracting Windows*-based update file includes Software License Agreement and the utility for updating the BIOS. It is designed to be used on Windows* systems. This method is the most commonly used.

========================

Read Me (pdf)

Instructions for Recovery BIOS Updates

In the unlikely event that a BIOS update is interrupted, it is possible the BIOS may be left in an unusable state. The 

recovery process requires the chassis to be opened to move the onboard BIOS Configuration Jumper.

WARNING: This process is intended to be performed by a trained technician. 

Recovery with Bootable USB Thumb Drive*Other names and brands may be claimed as the property of others.

Use this method if the recovery file (*.BIO) is too large to fit on a floppy disk or if the desktop board does not include floppy 

drive support.

1. Copy the recovery file (*.bio) to a bootable USB thumb drive.

2. Place the thumb drive in a USB port of the target system.

3. Shut down the system and unplug AC power.

4. Open the chassis and remove the BIOS Configuration Jumper. See the Technical Product Specification for details 

including the location of this jumper. 

5. Power the system on.

6. Wait 2-5 minutes for the update to complete. 

7. System will either turn off when the recovery process is completed or it will prompt you to turn off the system. 

8. Remove the thumb drive from the USB port.

9. Replace the BIOS Configuration Jumper.

10. Restart system.

Recovery with CD-ROM

Use this method if the recovery file (*.BIO) is too large to fit on a floppy disk or if the desktop board does not include floppy 

drive support.

1. Copy the recovery file (*.bio) to a CD. 

2. Place the CD in the CD-ROM drive of the target system. 

3. Shut down the system and unplug AC power.

4. Open the chassis and remove the BIOS Configuration Jumper. See the Technical Product Specification for details 

including the location of this jumper. 

5. Power the system on. 

6. Wait 2-5 minutes for the update to complete. 

7. System will either turn off when the recovery process is completed or it will prompt you to turn off the system. 

8. Replace the BIOS Configuration Jumper. 

9. Restart system.

Recovery with Floppy Disk

Use this method if the recovery file (*.BIO) is small enough to fit on a floppy disk (smaller than 1.44MB) and the desktop 

board includes floppy drive support. Note: The floppy disk does NOT need to be bootable; however, it must be formatted. 

1. Copy the recovery file (*.bio) to a formatted floppy disk. 

2. Place the disk in the floppy drive (drive A) of the target system. 

3. Shut down the system and unplug AC power.

4. Open the chassis and remove the BIOS Configuration Jumper. See the Technical Product Specification for details 

including the location of this jumper. 

5. Power the system on. 

6. Wait 2-5 minutes for the update to complete. When the floppy drive LED is lit, the system is copying the recovery 

code into the FLASH device. 

7. System will either turn off when the recovery process is completed or it will prompt you to turn off the system. 

8. Remove floppy disk from drive A: 

9. Replace the BIOS Configuration Jumper. 

10. Restart system.

NOTE: If the error message "CMOS/GPNV Checksum Bad…Press F1 to Run SETUP" appears during boot after the 

update, press [F1] to go into the "BIOS Setup Utility", press [F9] to load setup defaults, and then press [F10] to save and 

exit. 

=====================

Intel® Driver Update Utility

Download Center

Asus -crashed BIOS

Recovering Crashed ASUS BIOS During Update

POST. BIOS and Troubleshooting

Source

Power On Self Test

• The BIOS determines if the video card or onboard video is working.
• The BIOS verifies RAM.
• It checks for a keyboard and mouse.
• It looks for a PCI bus and then checks the cards that are installed.
• The system information is then displayed on the screen.

POST is determined by the computer's BIOS (Basic Input/Output System)
User settings are made in CMOS (complementary metal oxide semiconductor)
----------------------------------------------------------------------------------------------------------------------
Fault: Computer will not start
Fix: See below
Disperse internal Voltage

• Remove all power (adapter power Cord and Battery (for laptops))
• Hold down the ON button for 30secs (dispersing internal voltage)
• Plug the power cord in only (ie leave battery out, for the moment)
• Turn on

Did it work?
If so, shutdown normally, and fit the battery back in (for laptops)
Continue on as per normal

If not, try removing all externally connected devices, leaving in Power; Video; and Keyboard only 
(even test without Keyboard and mouse plugged in)
Reset CMOS

Many No POST failures are caused by your computer's CMOS settings being corrupt
Resetting the CMOS to defaults will cure this, and possibly allow your computer to POST
By reading your computer's or motherboard's Manual (discussed further down this page)
Locate the CMOS battery and/or the "reset CMOS jumper" on your motherboard
Following the reset CMOS procedure (usually shorting two pins, with CMOS battery out)
Your CMOS settings will be reset, hopefully allowing your computer to startup (or POST)

Hardware issues

Firstly it's always best to download your computer, or motherboard, manual
You can locate your manual, by going to you manufacturer's support page
For convenience (and as an example) Here is Dell's and HP's support info
Make sure to follow all AntiStatic and power recommendations/precautions

On PCs: (ie not laptops)
Re seat the Ram card(s)
Reconnect all internal connections 
All drive data cables can even be fully unplugged
Re seat or remove, all addon PCI cards
Unplug the case fan
Or try Benchtesting the motherboard
On Laptops:
Please note, it is also a good measure to re seat the Ram card(s) and also the Harddrive for laptops
You may need to locate your disassembly guide, at Google, not all manufactures provide this guide.
As an example, here is a good Toshiba laptop disassemble guide
Removing Dust
Dust and debris, is usually the biggest factor on computers that will not start
Using High compressed air, or a vacuum cleaner, remove all dust from the computer
With special attention on all Fans; the CPU; the Ram; and the Power Supply Unit
Here's an excellent guide to clean your computer
Power Supplies

Note: Although this subject has been discussed in the "Benchtesting" link above,
Just because some lights come on, does not mean your Power Supply is working properly.
It is also possible that your actual power switch is faulty
Or even the Display off micro button is faulty, (on laptops)
In most cases, it's a matter of testing with a known working Power Supply
Here's an excellent link on Power Supply information and Troubleshooting

Some more helpful links
Read the original No Post Tutorial
Beep Codes
Ultimate Boot CD
Reseating your CPU
An excellent Flowchart
Windows Repair Guide
Manufacture Drivers
Drive Diagnostics
Memtest

If you still require support with No POST, please create a New Thread
Stating what you have tried (or reply to your own existing related thread)
Making sure that you put System Specs information in your Profile

ZOTAC: CMOS Checksum Bad

zotac.com forum
Did you REALLY clear the CMOS?
1. Pull the power cord out the back.
2. Pull EVERYTHING off the motherboard including internal usb headers, RAM and all power cables so all your left with is the motherboard with attached processor.
3 Pull All Power Cables so absolutely nothing is attached to the power supply
2. Remove CMOS battery.
3. Clear CMOS with Jumper
4. Let Computer sit overnight just to be absolutely sure any capacitors are discharged.
5. Replace CMOS battery
6. Replace CMOS jumoer.
7. Replace RAM and attach power cables to motherboard. Nothing else should be plugged in or attached to the power supply at this point.
8. Attach known working keyboard. (I've had trouble booting previously because my wireless keyboard was running out of batteries)
9. Plug power cord back in press power
...........................................................
How-to POST Test a Motherboard - POWER ON SELF TEST Guide

• How to Bench Test Your System
  
• PCI PC Diagnostic Card

Recovery method for errors in the BIOS update
If the system doesn't power on and there is no display.
1) Download BIOS.
2) Copy file to USB Flash drive and rename to AMIBOOT.ROM
3) Connect USB Flash drive to USB port.
4) Power on system, press keyboard keys CTRL + HOME and continue to hold keys for 10-15 seconds.
5) When the USB Flash drive LED flash release keys.
6) Wait few minutes and the system will shutdown.
7) The system will turn on and function normally.
........................................................
You can flash the BIOS by using AFUDOS. Here are some steps on how to set it up.
* Use this utility to download FreeDOS and install onto USB drive.
* Copy AFUDOS and the BIOS to the USB drive
* Restart
* Load FreeDOS LiveCD with HiMEM + EMM386
* Change drive to B:\
* Flash the BIOS
Make sure you look at the Readme.txt for the AFUDOS command line. Copy exactly what is in the Readme file. 
..................................................
zotacusa.com/downloads/?cat=124
http://www.computerbase.de/forum/showthread.php?t=745029

Program all Blocks
Destroy CMOS checksum

hab mit afuwin laut zotac homepage mein Bios auf die neueste Version geflasht und vergessen Destroy CMOS Checksum anzuhacken.

Wenn ich jetzt boote schreibt er mir: CMOS Checksum Bad

Soweit so gut, ich hab dann auf F1 ins Setup - Alles auf Default gesetzt und neu gebootet.

Dann hab ich versucht mittels Jumper nen Cmos Reset zu machen. (Umgejumpert, gewartet, zurück gejumpert...noch immer das selbe Problem.

Dann habe ich die Batterie entfernt und ne Zeit lang gewartet...nach dem Wiedereinsetzten meinte er zwar das Uhrzeit/Datum nichtmehr stimmen und ich die einstellen müsste, aber danach wieder der CMOS Checksum Bad Fehler.

Hab dann versucht mit nem bootfähigem USB Stick mittels Afudos nochmal neu zu flashen, das Problem ist nur der USB Stick wird nicht als Bootable Device gefunden (es gibt kein Write Protection im Bios, dass konnte ich mal ausschließen). Mir ist aufgefallen, dass ich ja trotz änderungen im BIOS und mittels F10 speichern und verlassen trotzdem immer wieder die alten Settings geladen werden...

Stick wurde mittels http://www.biosflash.com/bios-boot-usb-stick.htm#Update erstellt

Possible solutions

Probieren mit 

http://www.biosflash.com/bios-boot-cd.htm

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

This problem arises when the step to load the default BIOS settings after the flash is not taken. To fix the issue load the default settings in BIOS and perform a reboot. If the problem persists, attempt a re-flash or CMOS reset and then load the default settings and reboot.

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

Reflash the BIOS. I had this issue when I did the upgrade because the default check box for BIOS Image apparently doesn't flash the full BIOS update to the chip. I tried it a second time and checked all the boxes and everything worked great.

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

Use AFUDOS vs. AFUWIN (at least it seemed easiest and worked for me).

Make a DOS bootable USB flash drive and copy AFUDOS.exe and the appropriate .rom file to the flash drive.

After booting to the flash drive, you can use the command line:

AFUDOS xxxxxx.rom /B /P /N /X /C

Where xxxx is your boards .rom file name.

The next re-boot should indicate the CMOS checksum is bad, and ask to reset with defaults. Go ahead and do so.

If the next boot does not start without some sort of checksum error, I expect you have a hardware problem.

Also make sure you did not accidentally leave the CMOS reset jumper in the reset position.

To explain a little from the information I got from your post, there are two seperate issues you are dealing with here.

First is your version of ROM BIOS, which is flashed into a flash memory device somewhere in the motherboard electronics.

The functionality of the BIOS is configured using CMOS memory. I gather that you are able to go into the BIOS and change things (like boot order to boot from the flah drive). If this is true, at least part of your BIOS been re-flashed OK, but you are still getting CMOS checksum errors. While I was re-flashing I also noticed there was something called NVRAM being cleared, which may also be part of your checksum error. 

The organization of CMOS/NVRAM could change from version to version of the BIOS. This could change the checksum validly, so it sounds like you have changes the BIOS, and not the CMOS/NVRAM versions.

The command line options have something to do with the resetting the CMOS, NVRAM and other re-flashing options.

You can determine the meaning of each by typing AFUDOS /? after booting from the flah drive and read the options. I got the options directly from the readme file in the .zip file from Zotac.

Anyway, I would not worry about the memory issue until you get the CMOS reset and working properly. This shows 960M memory size shows up in a number of posts, and is apparently also assoiciated with CMOS memory. Once you get the checksum... fixed this should go away and show the memory correctly again.

Problemas de arranque en Linux

Fuente 16 DICIEMBRE 2009

Algunas de las opciones disponibles:
acpi=off

Esta opción desactiva la ACPI, corrige diversos problemas de arranque en varias máquinas. ACPI es responsable de supervisar la carga de la batería, ajuste la frecuencia del procesador y de muchas otras funciones importantes, por lo que se debería dejar para desactivar en último caso.

acpi=ht

(ht de “hyper-thread”). Hace que se desactiven todas las configuraciones ACPI excepto las que necesita un procesador hyper-threading. Lo que sea que causa el problema, aparentemente no es necesario para un procesador de este tipo.

acpi=noirq 

Esta es una versión más ligera de la opción “acpi = off” que, en lugar de deshabilitar por completo el soporte para ACPI, sólo desactiva la asignación dinámica de direcciones, que es la causa de la mayoría de los problemas relacionados con ACPI .

Esta opción corrige problemas en la detección de la tarjeta de red, tarjeta de sonido y tarjeta inalámbrica en varios laptops de Acer, y posiblemente otros fabricantes, así como con la placa base con chipset SiS, debido a errores en la asignación de direcciones de la BIOS .

Una observación importante es que incluso aunque corrija problemas en algunas tarjetas de sobremesa y laptops, esta opción plantea problemas para la detección de componentes y conflictos en otros, causando que no se detecte la tarjeta inalámbrica o periféricos USB. Se debería utilizar sólo como una manera de resolver los problemas, no como una opción de rutina.

noapic

La APIC es una característica utilizada en los micros modernos para asignar direcciones IRQ, evitando conflictos entre los dispositivos. Muchas computaras utilizan BIOS que contienen varios bugs, dando como resultado que algunos periféricos no son detectados por el sistema, por ejemplo la tarjeta de sonido o tarjeta de red.

El uso de esta opción resuelve el problema en muchos casos.

La mayoría de las veces la mejor manera de solucionar de forma definitiva este tipo de problemas esactualizar la BIOS de la placa base, con una versión actualizada se pueden solucionar los problemas directamente.

Muchos fabricantes, como Asus, ofrecen un buen soporte con respecto a esto, vale la pena comprobar si hay una actualización disponible para la tarjeta. Normalmente, la actualización de la BIOS se realiza mediante el uso de un disquete o CD-ROM grabado con una imagen descargada de la página del fabricante. La actualización de la BIOS es potencialmente peligrosa, así debemos asegurarnos de leer las instrucciones del fabricante y comprobar si el archivo descargado corresponde a nuestra placa.

nolapic

El LAPIC (local APCI) es una variante de APIC que se utiliza en las máquinas con los procesadores dual-core o quad-core. Como el “noapic”, el “nolapic” se utiliza para resolver problemas relacionados con el arranque o la detección de los periféricos. Aunque ambos pueden ser utilizados juntos, por lo general sólo se necesita uno.

nosmp

En máquinas con procesadores de doble núcleo, esta opción deshabilita el segundo núcleo, que resuelve muchos problemas de arranque. Naturalmente, sin un núcleo la potencia de la máquina va a ser inferior, pero sirve como una solución temporal hasta que encuentre una solución al problema, que puede ser una actualización de la BIOS, o simplemente, una versión actualizada de la distribución en uso.

pci=biosirq

Esta es otra opción que resuelve los problemas de detección de la tarjeta de red o de sonido en algunas máquinas. Hace que el sistema siga la configuración de las direcciones definidas por el BIOS, en lugar de utilizar el procedimiento normal de detección.

pci=bios

Otra opción para la compatibilidad, esta vez para evitar problemas con la placa base del controlador PCI. Aunque es raro, es necesario utilizarla completar el arranque, en algunos portátiles.

pci=nommconf

Los problemas con MMCONFIG pueden ser debidos a problemas en el núcleo o problemas en el BIOS, o una discrepancia en la interpretación de las especificaciones.

No es necesario en la mayoría de los casos pero puede resolver algunos problemas si la BIOS contiene bugs. Los kernels más modernos parece que son capaces de trabajar con una mala configuración MMCONFIG en la BIOS

La función que utiliza MMCONFIG añade otra forma de describir la configuración de los dispositivos PCI en el sistema operativo.

Utilizar pci=nommconf no puede causar ninguna diferencia notable en las características o el rendimiento.

pci=nomsi

Se utiliza para la instalación, si la máquina tiene un disco duro SATA y al iniciar la instalación no se reconoce el disco duro.

pnpbios=off

Desactiva el soporte para plug-and-play en BIOS de la placa base, dejando que el núcleo se encargue de la detección de todos los componentes. Esta es una opción que soluciona problemas de compatibilidad en algunas placas.

irqpoll

Esta opción cambia la forma en que el sistema detecta los dispositivos de la máquina, corrigiendo problemas en PCs y laptops recientes, especialmente cuando se utiliza conjuntamente con distribuciones antiguas, anteriores a 2008. Necesaria para que el adaptador inalámbrico funciona en algunos portátiles Acer con tarjetas Broadcom, resuelve los problemas con la tarjeta de sonido o tarjeta de red en diversos entornos y soluciona un problema relacionado con la detección de HD SATA en las tarjetas basadas en el chipset K8T890 (como la Asus A8V-E), entre otros. Esta opción causa pocos efectos secundarios en comparación con las otras.

reboot=b

Esta opción hace que sea usada una función alternativa para reiniciar el micro vía software, resolviendo en algunos casos que no se reinicie la máquina usando el comando “reboot”.

all-generic-ide

Esta opción aborda los problemas de compatibilidad con el controlador IDE o SATA de algunas placas base, sobre todo en placas con el chipset SiS 761GX/965L (para utilizar un HD SATA). Esta opción se debe utilizar en los casos en que el sistema no puede detectar el HD de la micro (impide acceder a los archivos, imposibilitando la instalación).

Al utilizar esta opción de arranque, el sistema utiliza un modo genérico para el acceso a los discos duros, que resuelve el problema en la mayoría de los casos.

Esta opción causa una reducción significativa en el rendimiento del sistema, por lo que debe usarse sólo cuando realmente sea necesario.

Una peculiaridad es que el sistema detecta el HD SATA como “/ dev / hde” y no “/ dev / sda” como sería habitual. A pesar de eso, la instalación del sistema transcurre de manera normal.

En algunas placas con chipset VIA puede que sea necesario combinarla con la opción “irqpoll”, solucionando también un problema con la asignación de direcciones.

La mayor parte del artículo es una traducción libre del original de Carlos Morimoto

Una guía de parámetros del Kernel aquí

Motherboard & Bios

wimsbios.com/chipset/

wimsbios.com/biosupdates.jsp

biosagentplus.com/exe
_________________________ 
driverscollection.com/?H=VT8235&By=VIA
driversymanuales.com.ar/
cmedia.com.tw/EN/DownloadCenter
http://www.cmedia.com.tw/EN/DownloadCenter_Detail.aspx?pserno=0&dtype=ALL
Via Chipsets drivers
SIS.com/download/
global.aopen.com/download.aspxl
download.biostar.com.tw/.../support/index.php
nodevice.com/driver/company/DFI
global.dficlub.com
pcchipsusa.com
pcchips.com.tw/PCCWebSite/Downloads/
msi.com/...liveupdate
MSI (USA) live update

How to use?

NOTES: MSI Live Update Online must use Microsoft® Internet Explorer 5.0 and above versions, OS requires Windows® 98SE/ME/2000/XP/Vista/7 32bit. MSI Live Update Online uses Microsoft® ActiveX technology, please modify your ActiveX settings to ensure the proceeding of the automatic analysis and download. If your browser has installed Toolbar plug-ins, which might affect the normal operation of MSI Update Online. Please check your Toolbar-related settings to ensure the proceeding of the update service

motherboard.cz/driver/mbdriver.htm 
Uniflash 
UniflashRE ver. 1.47re build 09

Uniflash 2.00 (SPI support)

Uniflash 2.0b04, 2009.09.09
Uniflash 2.0b05, 2009.09.22

Phoenix flash utility:

• 2.1 Phlash (DOS)
  
  
  
  
  
  
  • 2.1.1 Phoenix Phlash16 Utility Version 1.4. Build 59a
  • 2.1.2 Phoenix Phlash16 Utility Version 1.6.5.4
• 2.2 WinPhlash (Windows)
  
  
  
  
  
  
  • 2.2.1 WinPhlash 1.50.55

biosagentplus.com/?ref=1

Welcome to BIOSAgentPlus! Home of the largest BIOS directory on the internet!

Get instant access to all major BIOS Firmware with BIOSAgentPlus: Phoenix Technologies, Award Software, American Megatrends.

Extend the life of your computer with a BIOS Update! BIOSAgentPlus is a small FREE program that helps you quickly identify and update your BIOS.

Desktop BIOS Updates

Available for all Makes and Models: Desktops and Laptops! FREE BIOS SCAN! Click here to download BIOSAgentPlus!

Laptop BIOS Updates

FREE Bios Report!

BIOSAgentPlus^® makes it easy...
It's easy to update your computer BIOS. In 2 Minutes or less, BIOSAgentPlus scans your computer and finds exactly the right updates. No other program does this as accurately or as quickly. 
 www.cmedia.com.tw/e_download_01.htm
 http://www.pcchips.com.tw/PCCWebSite/Downloads/ProductsDetail_Download.aspx?detailid=19&DetailName=New&DetailDesc=M758LT+%20%20(V5.2)&CategoryID=1&MenuID=82&LanID=3
http://www.megaupload.com/?d=9J8L84K0
http://www.pcdriverupdate.com/sound/PC_Chips/
http://sound-drivers.org/?id=16734&comp=C-Media&model=CMI8738,%20Version:%202.81&fname=AudioRack281.r00 
http://www.latinrank.com/buscadriver/placasdesonido/955.htm
http://descargardrivers.es/descargar.php?file=SiS%20Corporation%20SIS%20530%20Chipset%20Chipset

UEFI

Unified Extensible Firmware Interface A standard programming interface for setting up and booting a computer from the UEFI Forum (www.uefi.org). It evolved from the EFI interface developed by Intel, which was first used in Intel's Itanium line. UEFI also provides runtime services, which are used to access the drivers that were loaded in the pre-boot environment. For example, when booting from the network, the operating system can continue to use the same network protocols used to download it in the first place.
The Legacy BIOS
The BIOS dates back to the IBM PC in 1981, when the machine operated in 16-bit mode, and BIOS code was jammed into unused blocks within the first 1MB of memory. BIOS enhancements remain limited to the original 16-bit architecture (see PC memory map).
BIOS Compatibility
UEFI provides compatibility with legacy PCs by providing BIOS compatibility. UEFI-enabled PCs use UEFI routines to perform the test and configuration phases and then load a compatibility system module (CSM) that sets up legacy BIOS interfaces (interrupts) for use by the system software. In 2006, more than 12 million PCs shipped with EFI/UEFI booting and the CSM, but without making the EFI/UEFI interface available. See BIOS.
Windows support for UEFI started with the 64-bit versions of Windows Server 2008 and Windows Vista Service Pack 1 (SP1). In addition, Apple's Intel-based Macs are also EFI/UEFI compliant.

DMI Boot CD for Award-AMI-Intel BIOS

Source (Add SLP1.0 w/o modding) 

Last edited by 911medic; 03-11-2010

This is the original cd as posted here..credit goes to Suicide Solution..

Originally Posted by Suicide Solution

Here is a bootable CD ISO i threw together that will tattoo most all Award-AMI-Intel bios with the Hewlett-Packard string. It has a menu with options and shows keys needed with each HP Windows version. Can also exit to DOS so it can be ran manually if needed.
Manual Commands are:
DMI /SM "STRING HERE"
INTEL /SM "STRING HERE"

I have added teh core8 AMI bios tools and DMI tools. DMICFG is included in this cd. It is bootable and can be used to insert any string valid in the dmi area, as well as change manufacturer strings, serials, asset tags, version numbers, model type, etc. It can be an extremely viable alternative to flashing a mod. I have actually never had it not work.
To see how the DMI utility works..hit "4" on boot to escape the tattoo program, then type dmi at the prompt. The options will be shown..
See Images....
ScanCode made a SATA happy version here...http://forums.mydigitallife.info/showthread.php?t=14443 For USB sticks..very strong work!!!!
Mirror for the tools, with usb tool included..HERE...
first link..http://slics.myftp.org/Tools/HP_AMI_...HP_AMI_DMI.iso
second link...http://www.fileden.com/files/2008/8/...HP_AMI_DMI.iso
OEMBIOS FILES = http://forums.mydigitallife.info/showthread.php?t=9795
OEMBIOS Changer..http://slics.myftp.org/Tools/911%20M...0installer.exe
Alternate changer link...http://slics.myftp.org/OEMBIOS changer installer.exe
thread for changer-----http://forums.mydigitallife.info/showthread.php?t=6077
Just a script tool(s) to CAB or Uncab the oembios files as necessary..Handy for either preparing for the OEMBIOS changer or adding to CD..http://slics.myftp.org/OEMBIOS cab preps.rar..Contains a read me and "what goes here" tags..
The second one does not contain the dmicfg.exe..

Attached Thumbnails

       

BIOS modification to SLIC 2.1

BIOS description 
Modificación de BIOS
a. AMI Mod Tool  (aplicaciones, certificados, los SLIC 2.1 y los SLP)  
http://www.mediafire.com/?3z2yzynxizm

http://rapidshare.com/files/264764210/AMI_Slic_Tool_1.31.rar[/b][b]

www.megaupload.com/?d=EQC5COTI

b. Award Mod Tool (aplicaciones, certificados, los SLIC 2.1 y los SLP)  

http://www.mediafire.com/?0bmt0zwqmty

http://rapidshare.com/files/264763952/Award_Tool_1.15.rar

http://www.megaupload.com/?d=9IZ9IFIH

PHOENIX hace 3 versiones todos y cada uno tiene su propia manera de hacer las cosas. 

Descargar el BIOS directamente desde el sitio web del fabricante dela placa madre.
more at source
---------------------
Properly intentification of OEM certificates
Source
Complete package (2009-12-12) DLDit
Content:

• AMITool 1.42 ? to modify AMI BIOS
• AwardTool 1.29 - to modify AWARD BIOS
• PhoenixTool 1.00 ? to modify Phoenix, Insyde and Dell BIOS
• SlicInfo 1.0.0.5 ? shows information in the Slic file (.bin)
• PubKeyCompare 1.0.0.5 - compares identification of the OEM certificate (.xrm ms) with that of the BIOS Slic file (.bin)
• SLIC 2.1 und 2.0 BIN Files + Certs - all up-to-date available Slic files + matching certificates:

BIOS modification Tools and Methods
How to Modify Your Own Bios Using AMI Mod Tool and Award Mod Tool 

By

flipflapowski

 This is Only for Those Who Have AMI or AWARD Bios. 

 These Tools will not work with Phoenix Bios.

Quote:There are 3 major components which are required to activate a Microsoft Operating System as an OEM (Original Equipment Manufacturing)
1. A SLIC version which matches the particular Windows Operating System installed (Ex. - SLIC v1.0 or 1.1.0 for Windows XP, 98, ME OR SLIC v2.0 for Windows Vista OR SLIC v2.1 for Windows Vista and Windows 7).
2. An OEM SLP Product Key that matches the version of Windows installed - Retail Keys, Volume Licensing Keys will not work. Instead it ALWAYS MUST BE an OEM SLP PRODUCT KEY.
3. A Matching License or Certificate.
ALL 3 of these elements must meet in harmony or else you will fail in activating windows as OEM. One cannot exist without the other or it fails.
To help you understand the Differences of the various forms of bios, there are basically 3 type of bios: AMI - Award - Phoenix.

Phoenix makes all 3 versions and each has its own way of doing things.

- Download AMI and AWARD Mod Tools below. Each folder is in rar and includes how to for each tool in Microsoft Word.
- Download the Appropriate Bios Directly from your Motherboard's Manufacturer website. Do not trust or use third party websites. Only download directly from the motherboard manufacturer's website. Trust me, you will regret going through many third party websites.

Quote:NOTE - If you see a BIOS which has both 64 BIT and 32 BIT, ALWAYS choose 64b though your machine is only 32 BIT - Of course if there is a link to download the Windows 7 Bios, choose this link but always choose Windows 7 64 BIT though your machine is 32 BIT

- You need WinRar to unzip files
- Assuming you have downloaded all the elements above and have unzipped your bios file in Bio2Ami or Winrar, if needed, open your Mod Tool by right clicking on it and RUN AS ADMINISTRATOR.
For the Award Mod Tool, right click on AWARDTOOL.EXE. For AMI Mod Tool, right click on AMITOOL.EXE

The Tools Look Like This When Opened

1. Click the button by ORIGINAL BIOS and navigate to your bios file and click it.
2. Next, choose the manufacturer....if your manufacturer does not show, choose OTHER.
3. Choose SLIC. For those who only want to activate Windows Vista, choose SLIC v2.0. For those who want to activate Windows Vista and Windows 7, choose a SLIC v2.1
For those who choose DELL, open the folder SLICS 2.1 and inside is a SLIC DELL_QA09.BIN. I strongly suggest you choose this SLIC if you want to activate Windows 7 using DELL SLIC v2.1. Match the DELL_QA09.BIN SLIC with the DELL SLP. Be Careful and Do not choose SLIP DELL SYSTEM. If You choose DELL SYSTEM, this will cause you not to be able to activate Windows 7.
4. Choose SLP. If you choose a DELL SLIC, also choose a DELL SLP. This can be left blank.
5. Next, choose the certificate. The BIOS and the Certificate have to match. The tools will let you know if they do match or if they do not match.
6. As far as METHOD is concerned, let the tool choose default method.
For those who have ASROCK AMI bios, the AMI Mod Tool will automatically default to SSV3 when you choose ASROCK from the MANUFACTURER drop down menu. Before modifying, click the ADVANCED button. Once the Advanced window opens, find SSV3 Options and put a check mark by ADJUST SLIC IN DIFFERENT LOCATION.
For those who have an ECS AWARD Bios, EVGA AWARD Bios, MSI AWARD BIOS (NOT MSI AMI) and for those who have an AWARD Bios by HP or COMPAQ, use the ISA method to modify the bios. The Award Mod Tool defaults to 0+2 but ECS AWARD BIOS, EVGA AWARD BIOS, MSI AWARD BIOS, and AWARD Bios by HP or COMPAQ already have a SLIC inserted in the ACPITBL. The 0+2 method only adds a second SLIC and could cause problems with the computer or activation of windows. ISA will replace the OLD SLIC with the NEW SLIC.
7. Click GO and let the tool do its work.
8. After it finishes it will say it is successful or not and if you want to verify the successful modifications, click VERIFY. For those who have AWARD BIOS, this will show a checksum error. This is natural and do not let it bother you.
9. Now flash your bios according to the suggestion of your motheboard manufacturer's recommendations-

Quote:THIS IS IMPORTANT
- Uninstall any cracks, loaders, bios emulators, patches before flashing your bios.
A tool to uninstall any of these use VOATK 2.5 STAND ALONE TOOL

10. For those who wish to know what is the meaning of SSV, SSV2, SSV3, ISA, PubKey, Dynamic, 0+2, OEM7 or MMTool, download AMI or AWARD Mod Tool and inside there is a file explaining the various methods for modifying a bios.
I suggest you download the HOW_TO_FILES
Here is a Basic Understanding from ZORT of the Type of Methods of which One Uses to Modify a Bios

Quote:SLP = SLP 1.0
A text string that is added to the bios for XP, Win2003, and WHS activation. Corresponding oembios.* files must be installed in Windows.
SLIC = SLP 2.0 / 2.1
Public key/marker code is added to the bios. A certificate (.xrm-ms file) must be installed in Windows that matches the SLIC in the bios. A SLP 2.0 SLIC will activate Vista and Win2008. A SLP 2.1 SLIC will activate Win7 and Win2008 R2, as well as Vista SP1+ and Win2008.
First, SS stands for super static. We call it that because the memory address where the SLIC will be doesn't change. In some older ways of modding the SLIC would be at a different address depending how much RAM was in the computer, so a mod would work for one person but not another.
SSV (or SSV1): A new, uncompressed module is added to the bios that contains SLIC code. This is the way all mods were done originally. For Award bios, OEM and 0+2 methods are SSV1.
SSV2: The slic is written over FF bytes in the bios file, and the slic is not part of a module. This only works for AMI BIOS, not Award.
With SSV2 the system module is usually kept the same size, so all the modules in the bios remain in their original position. Most MSI AMI bioses require this method. If a bios has trouble booting to an onboard raid or other device it could be because of shifted offsets of the bios modules so try SSV2 in that case.
SSV3: The SLIC is written inside the system module. This makes the compressed system module much bigger. That means a lot of the modules will have their offsets (location in the bios file) shifted to make room for the expanded system. It usually works fine with Asus bioses, but can brick an MSI (w/AMI bios) motherboard. For Award bios to prevent all the modules from shifting we black out the EPA logo which makes it highly compressible. This way all the modules below the EPA logo will still remain at their original offsets. SSV3 works well with most bioses. For Gigabyte Award bios it's usually the best choice.
Pubkey: Only applies to Award bios. SLIC code is added to the bios as two parts (public key + marker). The only brand it works reliably with is Asus. It is safer than most methods because it doesn't change any existing modules. To flash it you have to use bios built in flash utility (EZ-Flash) because awdflash.exe will say "invalid Windows license". AMI bios has something similar in the form of a Fx module which is covered in the Dynamic option of the AMI Tool.
0+2: For Award. A "nocompress" (uncompressed) module is added to the end of the bios. The system module (module "0") is shrunk by the same amount that acpitbl (usually module "2") increases. This keeps the offsets the same for all the modules under acpitbl. This is a good option for Award bioses that don't have an active SLIC in their acpitbl already. For ones that do it will add a second SLIC and won't activate.
ISA: For Award. An ISA module with a special program is added to the end of the bios. The program replaces the SLIC in RAM with a new one, or adds a SLIC if one isn't present. This is a good choice for bioses that already have an active SLIC. It is also safer than most methods because it doesn't modify any existing modules. It doesn't work with most newer Gigabyte bioses.
Dynamic: Existing SLIC is overwritten with the new SLIC. For a bios with a SLIC that isn't enabled this won't do anything unless the configuration lock can be removed. (Fortunately for Asus AMI bios we can remove the config lock.) For Award bioses, this method is hit and miss. It has worked well sometimes (ex: Asus with lock removed) but on some occasions bricked motherboards (ex: a Shuttle and an EVGA, but there were some other Shuttles that worked)
OEM: For Award. SLIC is added as an uncompressed "OEM" module. The OEM module usually takes the location in the bios that the EPA or ACPITBL was using, and the EPA or ACPITBL is then readded at the end. This works well for older Award bioses like Abit. This is an ok option for Award bioses that don't have an enabled SLIC in their acpitbl already. For ones that do it will add a second SLIC and won't activate.

Just to be clear - all above is not my work I just repackaged those information for our use.
Hope You will like and play with it
I did not see an option where I could attach files within this thread
But you can google for needed files
flipF
MORE (SLIC collection)
All MoBos 
Foro Darkreloader.com
Todos estan con slic 2.1 Dell, SLP Dell y certificado Dell,
NF4ST-A9

http://www.mediafire.com/?zzmwyzmyzj2

Fatal1ty AN9 32X

http://www.mediafire.com/?uw3gmiztqmy

AM2V890-VSTA

http://www.mediafire.com/?mnzhbnryivh

4CoreDual-SATA2

http://rapidshare.com/files/279048529/4CoreDual-SATA2_2.10_.rar

P.D: Si quieres los 3 o 4 que te faltaron no hay problema. pasamelos y los modifico.
customer MoBo 
P4M900-M4 (Archivo de BIOS)
-http://www.biostar.com.tw/app/en/biosdl.php?BID=1224
Información y descarga
-http://www.biostar.com.tw/app/en/mb/bios.php?S_ID=283
BIOS modificados para modelos: NF4ST-A9(SLIC 2.1 ACER Y CERTIFICADO ACER 2.1)
A8N SLI Deluxe(SLIC 2.1 ACER Y CERTIFICADO ACER 2.1)
P4M900-M4(SLIC 2.1 ACER Y CERTIFICADO ACER 2.1)
K9NBPM2-FID(SLIC 2.1 DELL Y CERTIFICADO DELL)modificadas al 100% y verificadas sin ningun error. la del modelo K9NBPM2-FID tienes que leer lo siguiente ya que si lo flasheas de otra manera podrias darle error, te dejo esto:
Durante mucho tiempo, hemos estado recomendando no switch con flash. Si el SLIC es localizado en una zona NAVRAM, los conmutadores deben estar en el flash ..

Cita:

afudos /i [/n] [/p[n][c]
/n -don't check ROM ID
/pbnc -
b - Program Boot Block
n - Program NVRAM
c - Destroy System CMOS

Yo recomendaría no usar el switch B.
El archivo debe ser hecho como este ..
afudos /iROMNAME.ROM /n /pnc
Intenta esto para los flashes BIOS a partir de ahora, bueno se da en este modelo.
Paquete de bios modificados

http://rapidshare.com/files/285361765/bios_mod.rar

--------
P4M900-M4 - rev. 6.x - Ver. P490m828.bs : Award
slic = Asus, http://www.box.net/shared/mbh84pfggo
hard_drive, please give feedback
slic=Asus, tested Buzywoman, arm_bhy ver. 2008-12-12
http://slics.myftp.org/Biostar_P400M9_ASUS_OEM.rar
---
P4M900-M4 - ver. P490M117.BS : Award
slic=Asus mod Fzeven, tested chuckles, V-FrIeNd, please give feedback
http://www.box.net/shared/5ut8yoah1y
MyMobo
ASRock N68-S ver. 1.40 : AMI
slic=Dell, slp=Dell, method=ssv3, mod Busykid508
http://www.box.net/shared/v26ogzem3l
-----
N68-S - ver. 1.30 : AMI
slp/SLIC : ASUS mod urie, tested gastrico
http://rapidshare.com/files/23482123..._SLIC.zip.html
-----
N68-S - ver. 1.40 : AMI
slp/SLIC : ASUS mod?, tested ImpetuousRacer
http://www.box.net/shared/zu968hqv5y
-----
N68-S-1.40-DELL_SLIC21_DELL_SLP
http://www.box.net/shared/v26ogzem3l