cPC DMI for Field-Vista

cPC

Flex-Unit Repair & Recovery Updated for Vista

Rev 2.0

cPC CES/CPE Consumer PC GBU

Hewlett-Packard Company, Cupertino, CA

HP CONFIDENTIAL

Hewlett-Packard Confidential—Need to Know Required Copyright © 2004 Hewlett-Packard Company. All rights reserved. This document contains

information proprietary to Hewlett-Packard. (hp). Use or disclosure without written permission of an officer of HP is expressly forbidden.

cPC Flex-Unit Repair & Recovery Process

HP Confidential i Rev 1.5

TABLE OF CONTENTS

1 FLEX-UNIT RECOVERY .........................................................................................................................................1 1.1 CUSTOMER CREATED RECOVERY CD/DVD SET..................................................................................................1 1.2 SUPPORT-SENT RECOVERY CD/DVD SET...........................................................................................................1

2 FLEX-UNIT REPAIR PROCESS...............................................................................................................................2 2.1 NEEDED INFORMATION ....................................................................................................................................2 2.2 CONTENTS OF AGENCY & FLEXBUILD PRINTED LABELS ...............................................................................2 2.3 FIELD SUPPORT PROCESS ...................................................................................................................................5

3 CHANGES WITH FLEXBUILD 1.5 ........................................................................................................................5 3.1 BUILD ID ..........................................................................................................................................................5 3.2 MULTI-LANGUAGE BUILDS.................................................................................................................................6 3.3 DMI CHECKSUM ..............................................................................................................................................6

4 CHANGES WITH FLEXBUILD 2.0 ........................................................................................................................7

5 CPC_DMI PROGRAM ...........................................................................................................................................7 5.1 CPC-DMI FILES ................................................................................................................................................7 5.2 CPC_DMI START-UP OPTIONS..........................................................................................................................7 5.3 CPC_DMI USAGE ............................................................................................................................................7

5.3.1 Flexbuild 1.0/1.5 .................................................................................................................................7 5.3.2 Flexbuild 2.0 .........................................................................................................................................8

5.4 DMI.INI FILE ....................................................................................................................................................9 5.4.1 Flexbuild 1.0/1.5 .................................................................................................................................9 5.4.2 Flexbuild 2.0 .........................................................................................................................................9

5.5 DMI.LIB FILE.....................................................................................................................................................10 6 ERROR CODES ...................................................................................................................................................10

7 FLEXBUILD & LEGACY SW BUILDS TERMS & GLOSSARY ..............................................................................14

8 SAMPLE PICTURES..............................................................................................................................................16


HP Confidential 1 Rev 1.5

1 Flex-Unit Recovery Beginning with the Spring-Refresh 05 cycle, there is a new tattoo program being implemented to coincide with the introduction of Flex-Units. Flex-Units are PC’s which have the software build loaded based on the FlexBuild process. FlexBuild Process involves a set of roles, tools and procedures.

• for efficient, flexible, timely and automatic generation of per retail-sku and per cto-unit sw build image on the factory floor

• for enabling re-generation of sw image in field from Support-sent FlexRecovery CD/DVD set comprising a set of Base Recovery CDs/DVDs and a Supplemental CD/DVD

1.1 Customer Created Recovery CD/DVD set • Just like today

o Is a snapshot of the recovery partition

o Is quicker when recovering from CD as it only has the software for that model

o Is the result of the FlexBuild process, the bits have been “cooked”.

1.2 Support-sent Recovery CD/DVD set • Just like today

o Is 1 CD/DVD set per Language-Country Set-OS-Brand combo

o Is sent by Support Organization: sent if and when replacing failed HDD

o Recovers ALL SKUs in the cycle; i.e. is multi-SKU CD/DVD set

• DIFFERENT than today

o Is essentially a Mini FlexBuild Process on the CD/DVD set

o Takes > 120 minutes to re-build the image

o May requires the need to send a Supplemental CD/DVD

Supplemental CD/DVD’s

• Supplemental CD/DVD can or will contain

o ALL accumulated post-PR factory updates (formerly aka factory patches)

o These updates are exclusive of CPE updates

• PLUS

o All TTM drivers and non-huge apps released mid-cycle during a major business cycle

• Supplemental CD/DVD can be maximum one CD or DVD

o depends on quantity and size of updates & TTM SW



Page 262004-10-31 : FlexBuild OVERVIEW CPC FlexBuild Tools Team

FlexBuild : RECOVERY CONCEPTS

TTM Build 2TTM Build 1Base Build Build Type >>>

Base Recovery CDs

51Sup2(ATI, TurboTax)

51Sup1(ATI)

Supplemental CD

Base Build-ID

Factory Build-ID

51BLU151BLU151BLU1TurboTax

ATIATI

QuickenQuickenQuicken

Intel UMAIntel UMAIntel UMA

Win XP HEWin XP HEWin XP HE

51BLU351BLU251BLU1

BASE Build

2 Flex-Unit Repair Process The new tattoo, called cPC-DMI, will support both Flex-Units and Legacy-Units starting with Spring 05. It will not support units before this time. The only difference between the two types of units is with the feature bytes, which will be explained later. Only certain units in North America will be Flex-Units for Spring 05, all WW units will be Flex-Units beginning Spring Refresh 05.

2.1 Needed Information DMI information is provided for each unit, whether it is a retail unit or a CTO unit. This information is:

Is stored on a printed label affixed on the bottom of the unit’s chassis

Is visible to 3rd party ASP repair engineers

Contains BID (Build ID) information, legacy feature byte code and flexbuild feature byte information

This label is in addition to the existing agency label.

Additionally, this information can be found on Traceability for CTO units.

2.2 Contents of Agency & FlexBuild Printed Labels

Item Name Original Legacy AGENCY LABEL

Additional New FEATURE-BYTE LABEL

Example

Serial Number YES NO MX12345678

Legacy NO** YES 0qr121100



FeatureBytes; fixed length (10 bytes)

FlexBuild FeatureBytes;

Variable length in 2 character multiples

NO YES 2q12 12ws 34er 2345 56ty 76yh

Checksum NO YES (beginning Spring Refresh ‘06)

a3

Factory & Base Build-IDs (FlexBuild 1.0)

NO YES 51NAheBLU2, 51NAheBLU1

Factory Build-IDs (FlexBuild 1.5)

NO YES 62NAheBLA1

62FRheBLA1, 62NLheBLA1

RIN NO** YES NA51

Location Rear of Unit or Bottom of Chassis

Bottom of Chassis

** The Legacy FeatureBytes will NOT be printed on the AGENCY label for units made w/ FlexBuild process. This will help distinguish Legacy-Units from FlexBuild-units. This will enable Field Engineer to know when to use legacy repair process & when to use FlexBuild repair process for installed base.

The RIN moves from the agency label, where it was called the SW BOM, to the new Feature Byte label.

The new FlexBuild FeatureByte label will be in the following format:

12 FlexBuild Options 20 FlexBuild Options BID=51NAheBLU2,51NAheBLU1FeatureByte=0qr121100. 2q12 12ws 34er 2345 56ty 76yh RIN=NA44

BID=51NAheBLU2,51NAheBLU1FeatureByte=0qr121100. 12ws 34re 56ty 67yh Rt56 67yh ji90 nm67 3e2w 4r5k RIN=NA44

Changes with the introduction of FlexBuild 1.5, described in Section 3

FlexBuild 1.0 FlexBuild 1.5 BID=51NAheBLU2,51NAheBLU1 FeatureByte=0qr121100. 12ws 34re 56ty 67yh Rt56 67yh ji90 nm67 3e2w 4r5k RIN=NA51

BID=62NAheBLA2 FeatureByte=0qr121100. 12ws 34re 56ty 67yh Rt56 67yh ji90 nm67 3e2w 4r5k .a3 RIN=NA62



Changes with the introduction of FlexBuild 2.0, described in Section 4

FlexBuild 1.5 FlexBuild 2.0 BID=62NAheBLA2 FeatureByte=0qr121100. 12ws 34re 56ty 67yh Rt56 67yh ji90 nm67 3e2w 4r5k .a3 RIN=NA62

BID=71NAv3PrA2 FeatureByte=2S2U 3233 3E3K 3N3Q 3R3T 3V3X 3b3m 3u3w 464b 4c4m .GB

Sample of these labels:

Agency Label on Flex-Unit Agency Label on Legacy Unit

Feature Byte Label on Flex-Unit



2.3 Field Support Process Field Engineer needs to repair/replace non-working motherboard:

Uses

o New cpc_DMI tool

o contents of the new FlexBuild Feature Byte Label affixed on the unit’s chassis

o contents of Agency label affixed on the unit’s chassis

Flashes replacement motherboard’s BIOS DMI area with unit’s sw configuration.

Uses Support-sent Recovery CD/DVDs to recover original image, or alternatively the customer created CD’s, including any optional software purchased by the end-user and shipped with the unit.

Does additional tests to ensure the repaired & recovered unit is functional

If needed, synchronize with HDD DMI flag by running HDD_DMI utility.

Includes a note to the end-user advising the end-user that they may need to, after checking, install any (DIB) CD-DVD-based SW originally shipped with the unit.

Returns working unit to end-user customer.

3 Changes with FlexBuild 1.5 FlexBuild 1.5 brings these changes which need to be watched:

• Major/Minor Build ID’s

• No need for Base Build ID in DMI

• Change in usage for Multi-Language SKU’s

• DMI Checksum on the Feature Byte

All changes require the use of cPC_DMI v3.13 or greater. This version is backwards compatible with earlier versions.

3.1 Build ID With FlexBuild 1.5, the Factory Build, Base Build concept is dropped, there will only be a factory build.

To deal with changes that might require a change to the factory build but are not required for Support Sent Recovery, the concept of Major/Minor Builds in introduced.

A MAJOR Build-ID is any build for which there is Recovery-CD offering

• be it a BASE Recovery-CD/DVDset only

• or a BASE Recovery-CD/DVDset with a Supplemental-CD/DVD.

A minor Build-ID is any build for which we are not delivering a Supplemental Recovery-CD offering. Units w/ a minor Build-ID are to be recovered with a previously released MAJOR Build. A minor build might be one where a desktop icon is contractually required for first boot, but not after a recovery.

The next to last character position indicates whether the build is major or minor.

• Major Build-IDs use A

• Minor Build-IDs use b..z (lower cased as a reminder that it’s a Minor Build-ID)



Released Builds Released Recovery-CDs Released

Supplemental CD/DVDs

Units RECOVERED using

62NAheBLA1

none

62NAheBLb1 none none

62NAheBLc1 none none

62NAheBLA2 none sup1 + S1

62NAheBLb2 none none + S1

62NAheBLA3 none sup2 + S2

Please Note: All cases are referring to recovery from Support-sent Recovery-CDs / Supplemental-CD/DVDs. Recovery from the recovery partition or recovery using user-created Recovery-CDs will always recover the system they originally received on their hard drive regardless of major/minor build, if the hard drive is as-delivered. If a customer recovers from Support-sent Recovery-CDs, the recovery partition is re-imaged to contain the earlier Major Build-ID, so any partition or user-created- Recovery CD operations will then restore the previous Major Build-ID.

3.2 Multi-Language Builds As the need for the Base Build ID has been removed from the DMI, Multi-Language ID’s are now identified in the DMI.

Example: BID=62ITheBLA2,62FRheBLA1,62DEprBLA1

• When a customer boots this SKU, they are prompted for their desired language: Italian, French or German.

• The first Build-ID specified in DMI is the default language

• If the customer selects one of the non-default languages, as before, a new recovery partition is put in place and recovered.

• Support-sent Recovery-CDs for any of these three builds could be sent to the customer and recovery is seamless. As with FlexBuild 1.0, they do not need to enter Build-IDs for non-default languages.

3.3 DMI Checksum To better validate user input during motherboard repair, a checksum is now part of the FeatureByte code. It is included on the Feature Byte label.

If the Build-ID you’re specifying is 62 or greater, a FeatureByte checksum is required. Otherwise, it is not.



4 Changes with FlexBuild 2.0 FlexBuild 2.0 brings these changes:

• Removal of RIN (SWBOM)

• Removal of Type 1 fields

o Channel and Option codes now in Type 11 fields

• Removal of HWBOM

• Motherboard name no longer required

5 cPC_DMI Program

5.1 cPC-DMI Files The cPC-DMI program can be found on the internet at http://www.techport.info/

It will be in two formats:

• as an .img file for use with a floppy

• as an .iso file for use with a CD.

The floppy version is sent as an .img file. It is contained in a zip file along with copydisk.exe, which creates the bootable floppy, and a batch file to run copydisk.

The CD and floppy versions work as previous flash programs did, except you now have the option to produce the variable file, called the dmi.ini file, externally.

5.2 cPC_DMI Start-up Options When the cPC-DMI program starts, you are presented with the following:

\\CPC-DMI /? CPC_DMI SYNTAX CPC_DMI runs utility with default settings. CPC_DMI (path)(ini File) runs utility with specific ini file. CPC_DMI /read Retrieves Type 1 and Type 11 DMI strings. CPC_DMI /ver Displays utility version. CPC_DMI /? Displays help.

More information on using default settings or a specific ini file follows. To use the default settings, create a file called dmi.ini based on the format in section 3.4 and place it in the root of the disk. Alternatively, you can create multiple ini files based on the format in section 3.4 of different names which can be placed anywhere on the disk.

5.3 cPC_DMI Usage

5.3.1 Flexbuild 1.0/1.5 The usage of the cPC_DMI program is very similar to the previous HPtattoo program. When you boot into the program, if there is no dmi.ini file, you will be prompted to enter:

• Enter (F)eatureByte: from FlexBuild Feature Byte Label, ex: 0qr121100. 292c 2d2j 2n2s 2w2z 2C2G 2M2P.a3

o Please note that spaces are not required, the program will actually disregard them



o Please Note that the Feature Byte is case sensitive

o If doing a Legacy Unit, then enter the Feature Byte from the Agency Label – listed as HWBOM – without the “.”

• Enter BuildID from FlexBuild Feature Byte Label, ex: 51NAheBLU2,51NAheBLU1

o Enter the Build ID as it is displayed on the label

o If doing a Legacy Unit, then no Build ID is needed

• Enter (S)erialNumber: on agency label

• Enter (H)WBOM: can use the default values

• Enter (R)IN: from FlexBuild Feature Byte Label or from Agency Label, ex: NA51

• Enter (P)roductNumber: on agency label as System Number

• Enter (L)anguageCode: this is not on the agency label, except for SE-Asia countries; this code will be constant for a country. The current list is in Table 2.

• Enter Mo(d)elNumber: on front or side of unit

• Enter (C)hannel: more information is in Table 1, RE is default.

• Enter the (O)ptionalCode: using the default, if you are doing a refurbished unit, mainly in NA, you need to change the from 0 to 1

• (M)otherboard: enter the motherboard name; if the name is not known or provided, it can be found at TechPort. Enter either the long or short name. The current list is in Table 3.

• Enter (F)eatureByte: from FlexBuild Feature Byte Label, ex: 0qr121100. 292c 2d2j 2n2s 2w2z 2C2G 2M2P.a3



o If doing a Legacy Unit, then enter the Feature Byte from the Agency Label – listed as HWBOM – without the “.”

Please note that the Feature Byte is the main differentiator between Flex-Units and Legacy-Units. On Legacy-Units, only the 10 digit code on the left of the dot is needed. This code is on the agency label as the HW BOM. If there is a HW BOM code on the agency label in this format, then there is no Feature Byte label and it is a Legacy-Unit. If there is no HW BOM and there is a Feature Byte label, it is a Flex-Unit.

5.3.2 Flexbuild 2.0 The usage of the cPC_DMI program is very similar to the previous HPtattoo program. When you boot into the program, if there is no dmi.ini file, you will be prompted to enter:

• Enter (F)eatureByte: from FlexBuild Feature Byte Label, ex: 3F3K3N3Q3S3T3V3X45.QR



• Enter (P)roductNumber: on agency label as System Number

• Enter Mo(d)elNumber: on front or side of unit

• Enter (S)erialNumber: on agency label

• Enter (L)anguageCode: this is not on the agency label, except for SE-Asia countries; this code will be constant for a country. The current list is in Table 2.

• Enter BuildID from FlexBuild Feature Byte Label, ex: 71NA3eMLAa

o Enter the Build ID as it is displayed on the label



5.4 DMI.INI file

5.4.1 Flexbuild 1.0/1.5 You can produce a DMI.ini file externally for use with the program. It is a text based file in the following template, the variable entries are bolded. This file can be on any drive, floppy or thumb. [DMIinfo] ;Feature Byte - case sensitive FeatureByte=267121110.292c 2d2j 2n2s 2w2z 2C2G 2M2P.a3 ProdNum=D5468AT Model=a123n Serial=US10101010 Motherboard=GIOVANI LanguageCode=ABA RIN=NA10 HWBOM=101 Channel=RE OptionCode=0

BuildID=51NAheBLU2,51NAheBlU1 (FlexBuild 1.0)

or= 62NAheBLA1 (FlexBuild 1.5)

As an additional feature, you can produce sku specific DMI.ini files. In this case all of the variable entries except the Serial Number would be present, as the following shows. You could call this file a123n.ini and use it with any model a123n. When you load the program with this ini file, then the only prompt you will receive is for the Serial Number. [DMIinfo] ;Feature Byte - case sensitive FeatureByte=267121110.292c 2d2j 2n2s 2w2z 2C2G 2M2P ProdNum=D5468AT Model=a123n Serial= Motherboard=GIOVANI LanguageCode=ABA RIN=NA10 HWBOM=101 Channel=RE OptionCode=0

BuildID=51NAheBLA2,51NAheBlA1

5.4.2 Flexbuild 2.0 You can produce a DMI.ini file externally for use with the program. It is a text based file in the following template, the variable entries are bolded. This file can be on any drive, floppy or thumb. [DMIinfo] ; DMI information for cPC_DMI.exe FeatureByte=3F3K3N3Q3S3T3V3X45.QR ProdNum=RS489AA Model=s7620n Serial=CNA6451234 LanguageCode=ABA



BuildID=71NA3eMLAa As an additional feature, you can produce sku specific DMI.ini files. In this case all of the variable entries except the Serial Number would be present, as the following shows. You could call this file a123n.ini and use it with any model a123n. When you load the program with this ini file, then the only prompt you will receive is for the Serial Number. [DMIinfo] ; DMI information for cPC_DMI.exe FeatureByte=3F3K3N3Q3S3T3V3X45.QR ProdNum=RS489AA Model=s7620n Serial= LanguageCode=ABA BuildID=71NA3eMLAa

5.5 dmi.lib file The dmi.lib file is the one variable which will require being updated, possibly at least once a cycle. This file will be found on the internet at http://www.techport.info/. There are a few ways to implement this update.

• Simply download and overwrite the file on your floppy disk

• Download and use the newer iso file. These files are backwards compatible unless otherwise stated.

• If using an older CD image, place the dmi.lib file on a thumb drive and boot with the thumb drive attached while the CD boots. At the DOS prompt before starting the program, simply copy the dmi.lib file from the thumb drive to the RAM drive where the program is running.

6 Error Codes The following is list of error codes found in cpc_dmi. Bolded texts are possible errors generated cpc_dmi, right beneath it is the explanation of occurrence. dmi.lib not found! dmi.lib file can not be found at current working directory Invalid LIB file dmi.lib file is corrupted UNKNOWN PC Type. Writting process has terminated. Error in type-1 feature byte, PC brand is not hp pavilion or Compaq Presario bios is not supported bios is not AWARD or AMI BIOS doesn't support Type-11 Strings Writing. BIOS doesn't support Type-11 strings Error: One or more values in FeatureByte were not recognized. Please check your FeatureByte and be sure you have the latest dmi.lib.



Error in feature byte or dmi.lib is out of date CRC value is incorrect or missing. The provided checksum value is correct or missing from the FeatureByte string. Incorrect BuildID format. Provided BuildID string is not in this formate: BuildID1,BuildID2 Note each buildID must be 10 characters At input prompt, cpc_dmi loops the prompt if invalid data is inputted and no error message is generated. Please refer to “Field Specification” section 3.1 for input specifications. Staring revision 3.13, one the following exit code/errorlevel is set if error occurred.

Exit Code (errorlevel) Error Message

1 Invalid LIB file 2 bios is not supported. 3 BIOS doesn't support Type-11 Strings Writing. 4 One or more values in the FeatureByte are not recognized. 5 Type-11 string has excessed 1024 characters 6 UNKNOWN PC Type. Writting process has terminated. 7 Verifying SMBIOS Data [01] ..... FAILED! 8 Verifying SMBIOS Data [11] ..... FAILED! 9 ExtendOpt buffer over run. 10 System BIOS is not Windows Vista ready.

Table 1 – Channel Designations Codes

Codes Where Used CT CTO CO Corsair GN Gaming PC, no RAID GR Gaming PC, with RAID LR Living Room PC (DEC) LX All FreeDOS and Linux products NR No recovery partition included PP People PC TG Target WM Walmart RE All other units, is the default The Channel Code controls features of the BIOS; i.e. LR and NR prevent the “F10 for Recovery” message from appearing at startup.

Table 2 - Language Codes Product Suffix Region Product Suffix Region A2K Philippines ABU UK AB0 Taiwan ABV Middle East AB1 Korea ABX Finland AB2 China ABY Denmark



AB3 Thailand ABZ Italy AB4 Singapore, Malaysia AC4 Brazil AB5 Hong Kong ACJ India AB8 Turkey ACP Austria AB9 Portugal AK8 Sweden/Finland ABA USA and/or Canada AKV Chile ABC Canada AKW Middle East ABD Germany AR6 Indonesia ABE Spain ARS PAPE English ABF France B14 Belgium ABG Australia, New Zealand B1U Sweden/English ABH Holland B1V Norway/Denmark ABJ Japan UUB Hong Kong, Taiwan ABM Mexico UUC Vietnam ABN Norway UUW Scandanavia



Table 3 - Motherboard Names

Motherboard Name

CPC_DMI Name

Motherboard Name

CPC_DMI Name

Agena AGENA Grafito GRAFI Agena2 AGEN2 Graphite GRAPH Ahi AHI Grouper Group Albacore ALBAC Guppy GUPPY Amberine AMBER Gypsum GYPSU AmberineM AMBEM Harold HAROL Amethyst AMETH Harry HARRY AmethystM AMETM Kamet2 KAME2 Anchovy ANCHO Kelut KELUT Asterope ASTER Kungur KUNGU Asterope2 ASTE2 Limestone LIMES Bailey BAILE Limestone2 LIME2 Banyan BANYA Lithium LITHI Basswood BASSW Lithium2 LITH2 Birch BIRCH Nagami NAGAM Buckeye BUCKE Nash NASH Cobra COBRA NashM NASHM Diablo DIABL Neon2 NEON2 Dom DOM Nodus NODUS Durango DURAN NodusM NODUM Echo ECHO Onyx ONYX Emery EMERY Onyx2 ONYX2 Enstatite ENSTA Opal OPAL Explorer EXPLO Oxford OXFOR Explorer2 EXPL2 Piranha PIRAN Explorer4 EXPL4 Puffer PUFFE Focus FOCUS Puffer2 PUFF2 Gamilla GAMIL PufferM PUFFM Gamilla2 GAMI2 Salmon SALMO Ganges GANGE Snapper SNAPP Giovani GIOVA Stingray STING Giovani2 GIOV2 Xenon3 XENO3 Glendale GLEND Xenon4 XENO4 Goldfish Goldf Xtreme XTREM Goldfish2 Gold2 Yellowstone YELLO Goldfish3 Gold3 Yukon YUKON



7 FlexBuild & Legacy SW Builds Terms & Glossary

• Base Build: A software Build used as a “Base” for developing a TTM Software Build.

See also Base Build, Base Build-ID, Base Recovery CD/DVDs, Factory Build-ID,

Supplemental CD/DVD and TTM Build.

• Base Recovery CD/DVDs: Set of RCDs corresponding to a Base Build. . See also Base Build, Base Build-ID, Base Recovery CD/DVDs, Factory Build-ID and Supplemental CD/DVD.



• Build: Sometimes interchangeably used for “SW Image” or simply “Image”; technically and more accurately, many images can be and are created from a single SW Build definition. Physically represented as a set of Recovery CDs or DVDs.

• Build-ID: e.g. 51NAheBLU1: A 10 alpha-numeric identifier string that is unique to a software build and is encoded to capture information about the build’s year, quarter, region-language, operating system-type, brand, ODM and iteration letter or digit.

• Cooking: aka post-processing in commercial units, whereas software is pre-installed or pre-loaded on units HDD on the factory floor.

• CTO: Configure To Order: aka “Direct”: See also Direct. A PC (Hardware & Software) built to a specific end-user’s purchase order and configuration. Usually sold via Direct channels like “HP Shopping” website or Kiosks in major retail stores.

• Cycle: The 4 business cycles used by cPC to launch new retail SKUs or desktop models. The nomenclature generally follows 4 seasons in northern hemisphere. The business cycles follow the retail selling cycles in NA and are

• Spring ~January On-Ad

• Spring-Refresh ~April On-Ad

• Summer Back-to-school ~July On-ad

• Fall Holidays ~October On-Ad

• Direct: See CTO. Refers to the “Direct” channel for PC distribution, as opposed to the “Retail” channel.

• DMI: Desktop Management Interface, an industry standard. Generic PCs applications use DMI area in BIOS to “manage” the PC.

• DMI setting: see DMI flag.

• Factory Build-ID: A Software Build-ID used by Factory for generating a shipping Image. Both factory build-ID & Base Build-ID are flashed into the UUT’s BIOS DMI Type11 Area.



• FIO: Factory Installed Option. See Option.

• FlexBuild: The term given to this revised Build Process.

• FlexTools: Collective name for the tools used in FlexBuild process.

• FlexRecovery: Act of performing a flexible recovery using the concept and tool of Base Recovery CD/DVDset and the new Supplemental CD/DVD.

• FlexUnit: A PC, either a retail product or CTO product, which has a software build created by the FlexBuild process.



• ODM: Original Design Manufacturer: cPC hardware design and manufacturing partner; in software build process context, ODMs are provided tested software blocks and ML (material list) files from which they create software builds and test these with the hardware SKUs they are responsible for.

• RCD: abbr. See Recovery CD/DVDs.

• Recovery CD/DVDs: A set of CDs or DVDs delivered by R&D and used by end-users to recover the PC’s HDD to its factory-shipped state.

• Released Build: e.g. 51NAHeBLU5. The final “Released” SW Build. Released to the factory to start PR (Pilot Run). Ends in assigned digit of 1-9, as opposed to Release Candidate Builds, which end in an alphabetic character e.g. 51NAheNLUb. Formally and officially released as a Factory Build-ID to the factory for beginning production and as a set of Recovery CD/DVDset to field for support purposes.

• System: aka PC or Desktop or Desktop PC or Unit

• Supplemental CD/DVD: A CD or DVD that supplements Base RCDs; contains the additional software components that are introduced with new TTM Software Builds.

Image generated using [ Factory Build-ID ]

= Image generated using [ Base Build RCDs + Supplemental CD/DVD ]



• SKU (traditional cPC usage): Stock Kitting Unit, generic industry usage; In cPC usage, aka Model Number; e.g. a730n or “HP Pavilion PC Model a730n”.

• Tattoo: a legacy software build term; act of setting Optional software flags in the DMI area. See DMI flag.



8 Sample Pictures

Figure 1 - Program Options

Figure 2 - DMI Read



Figure 3 - Input Samples – Spring 05 Legacy Unit

Figure 4 - Final Values – Spring 05 Legacy Unit



Figure 5 - Input Values - Flex-Unit

Figure 6 - Final Values – Flex-Unit

cPC DMI for Field-Vista

Documents

Transcript of cPC DMI for Field-Vista