У Вас проблем не было с обнаружением SATA устройств, при FSB >133 MHz ?

Если сможете прошить, то мать нормально работать не будет

Сам биос открыл в Hex-редакторе.

Каким образом там можно найти что-либо похожее на ID процев?

Для этого надо изучить структуру модуля микрокодов

на сайте нашол 2 версии биоса под DOS и под Win. Какую надо скачать и как его перепрошить правельно

You can launch EZ Flash 2 by two methods.
(1) Isert the floppy disk/USB flash disk that contains the BIOS file to the floppy disk drive or the USB port. Press <Alt>+<F2> during POST to display following. (показана картинка)
(2) Enter BIOS setup program. Go to the Tools menu to select EZ Flash 2 and press <Enter> to enable it.

Microcode updates are composed of a multi-byte header, followed by encrypted data and then by an optional extended signature table. The header is 48 bytes. The first 4 bytes of the header contain the header version. The update header and its reserved fields are interpreted by software based upon the header version. An encoding scheme guards against tampering and provides a means for determining the authenticity of any given update. For microcode updates with a data size field equal to 00000000H, the size of the microcode update is 2048 bytes. The first 48 bytes contain the microcode update header. The remaining 2000 bytes contain encrypted data. For microcode updates with a data size not equal to 00000000H, the total size field specifies the size of the microcode update. The first 48 bytes contain the microcode update header. The second part of the microcode update is the encrypted data. The data size field of the microcode update header specifies the encrypted data size, its value must be a multiple of the size of DWORD. The optional extended signature table if implemented follows the encrypted data, and its size is calculated by (Total Size – (Data Size + 48)).

Microcode Update Field Definitions

Field Name-----Offset (bytes)-----Length (bytes)-----Description


Header Version-----0-----4-----Version number of the update header.

Update Revision-----4-----4-----Unique version number for the update, the basis for the update signature provided by the processor to indicate the current update functioning within the processor. Used by the BIOS to authenticate the update and verify that the processor loads successfully. The value in this field cannot be used for processor stepping identification alone. This is a signed 32-bit number.

Date-----8-----4-----Date of the update creation in binary format: mmddyyyy (e.g. 07/18/98 is 07181998H).

Processor Signature-----12-----4-----Extended family, extended model, type, family, model, and stepping of processor that requires this particular update revision (e.g., 00000650H). Each microcode update is designed specifically for a given extended family, extended model, type, family, model, and stepping of the processor. The BIOS uses the processor signature field in conjunction with the CPUID instruction to determine whether or not an update is appropriate to load on a processor. The information encoded within this field exactly corresponds to the bit representations returned by the CPUID instruction.

Checksum-----16-----4-----Checksum of Update Data and Header. Used to verify the integrity of the update header and data. Checksum is correct when the summation of all the DWORDs (including the extended Processor Signature Table) that comprise the microcode update result in 00000000H.

Loader Revision-----20-----4-----Version number of the loader program needed to correctly load this update. The initial version is 00000001H. Processor Flags 24 4 Platform type information is encoded in the lower 8 bits of this 4-byte field. Each bit represents a particular platform type for a given CPUID. The BIOS uses the processor flags field in conjunction with the platform Id bits in MSR (17H) to determine whether or not an update is appropriate to load on a processor. Multiple bits may be set representing support for multiple platform IDs.

Data Size-----28-----4-----Specifies the size of the encrypted data in bytes, and must be a multiple of DWORDs. If this value is 00000000H, then the microcode update encrypted data is 2000 bytes (or 500 DWORDs).

Total Size-----32-----4-----Specifies the total size of the microcode update in bytes. It is the summation of the header size, the encrypted data size and the size of the optional extended signature table.

Reserved-----36-----12-----Reserved fields for future expansion.

Update Data-----48-----Data Size or 2000-----Update data.

Extended Signature Count-----Data Size+48-----4-----Specifies the number of extended signature structures (Processor Signature[n], processor flags[n] and checksum[n]) that exist in this microcode update.

Extended Checksum-----Data Size+52-----4-----Checksum of update extended processor signature table. Used to verify the integrity of the extended processor signature table. Checksum is correct when the summation of the DWORDs that comprise the extended processor signature table results in 00000000H.

Reserved-----Data Size+56-----12-----Reserved fields.

Processor Signature[n]-----Data Size+68+(n * 12)-----4-----Extended family, extended model, type, family, model, and stepping of processor that requires this particular update revision (e.g., 00000650H). Each microcode update is designed specifically for a given extended family, extended model, type, family, model, and stepping of the processor. The BIOS uses the processor signature field in conjunction with the CPUID instruction to determine whether or not an update is appropriate to load on a processor. The information encoded within this field exactly corresponds to the bit representations returned by the CPUID instruction.

Processor Flags[n]-----Data Size+72+(n * 12)-----4-----Platform type information is encoded in the lower 8 bits of this 4-byte field. Each bit represents a particular platform type for a given CPUID. The BIOS uses the processor flags field in conjunction with the platform Id bits in MSR (17H) to determine whether or not an update is appropriate to load on a processor. Multiple bits may be set representing support for multiple platform IDs.

Checksum[n]-----Data Size+76+(n * 12)-----4-----Used by utility software to decompose a microcode update into multiple microcode updates where each of the new updates is constructed without the optional Extended Processor Signature Table. To calculate the Checksum, substitute the Primary Processor Signature entry and the Processor Flags entry with the corresponding Extended Patch entry. Delete the Extended Processor Signature Table entries. The Checksum is correct when the summation of all DWORDs that comprise the created Extended Processor Patch results in 00000000H.

Т.е. CPUID всех процессоров находится в явном виде (как он указан в техописании проца) в файле биоса?

Как нужно искать?

Вытащить что-то из самой микросхемы у меня возможности нет.

Но разве там может содержаться что-то, что не содержится в файле биоса, по интересующему нас вопросу?

Попробовал прошить с помощью AFUWIN

При загрузке выпадает error CMOS CheckSum - предлагается нажать F1 для входа в биос или F2 для сброса настроек на дефолт и продолжения загрузки.
Что я не так делаю???

Из под DOS прошивать не пробывал - флоп не купил.

Как прошить с:\test\ afud408 a7250nms.170
Это все? или надо еще какие то ключи указывать, как я понял а налогичные галочкам в закладке setup виндверсии

afudos /i<ROM filename> [/o<save ROM filename>] [/n] [/p[b][n][c]]
[/r<registry_path>] [/s] [/k[N]] [/q] [/h]
/n - don't check ROM ID
/pbnc -
b - Program Boot Block
n - Program NVRAM
c - Destroy System CMOS
/r - registry path to store result of operation
(only for Windows version)
/k - Program all non-critical block only
/kN - Program N'th non-critical block only
(Example: k0/k1/k3 upto k7)
/c - Skip non-critical blocks
/s - leave signature in BIOS
/q - silent execution
/h - print help
/t - Display ROM ID string
/c - Program Main Bios and all Non-critical blocks
/cN - Program Main Bios and N'th Non-critical block
(from c0 up to c7)
/d - Compare ROM file (skips flashing)
/u<filename> -Display ROM ID

Адрес 127788h я кое-как разобрал. Это надо найти строку Offset 00127780, в столбце 0 будет часть кода 0F, а в столбце 8 часть кода 62, так?

В итоге, по какому принципу искать другие коды? ....... Есть какая-то закономерность?

Кстати, у E6750 и Q6600(G0) один и тот же CPUID - 06FBh. И вообще, у всех процессоров одного степпинга он идентичен! Как это понимать? И как же тогда идентифицировать конкретный проц в биос?

В Offset 00129780 я нашел в столбце 9 код 06, а в столбце E - код FB. В этой же строке в столбцах 4-7 указаны коды 07-20-08-03, что можно интерпретировать как дату 8 марта 2007 года? В итоге, это то, что мы ищем - CPUID 06FBh??

All OS и DOS что это значит?

зайти в BIOS и сбросить настройки на дефолтные не пробовал ? зашел в BIOS -> Load Optimized Defaults -> Save & Exit Setup

afudos /i<ROM filename> [/o<save ROM filename>] [/n] [/p[b][n][c]]
[/r<registry_path>] [/s] [/k[N]] [/q] [/h]
/n - don't check ROM ID
/pbnc -
b - Program Boot Block
n - Program NVRAM
c - Destroy System CMOS
/r - registry path to store result of operation
(only for Windows version)
/k - Program all non-critical block only
/kN - Program N'th non-critical block only
(Example: k0/k1/k3 upto k7)
/c - Skip non-critical blocks
/s - leave signature in BIOS
/q - silent execution
/h - print help
/t - Display ROM ID string
/c - Program Main Bios and all Non-critical blocks
/cN - Program Main Bios and N'th Non-critical block
(from c0 up to c7)
/d - Compare ROM file (skips flashing)
/u<filename> -Display ROM ID