Assembling The 2005.05.14 Standard Workstation: A8V-ASUS-0213.ROM
Assembling The 2005.05.14 Standard Workstation: A8V-ASUS-0213.ROM
HCL Infosystems Ltd is one of the pioneers in the Indian IT market with its origins in 1976. For
over quarter of a century, we have developed and implemented solutions for multiple market
segments, across a range of technologies in India. We have been in the forefront in introducing
new technologies and solutions.
HCL vision is 'Together we create the enterprises of tomorrow'. HCL's mission is to provide
world-class information technology solutions and services to enable our customers to serve their
customers better.
HCL certified initially to ISO 9002:1994 by Bureau VERITAS Certification in 1994 and later on
to ISO 9001:1994 in 1997. As of now, all our manufacturing units are certified by Bureau
VERITAS Certification as per ISO 9001:2000 and ISO 14001: 2004.
HCL provides products Computing Products, Display Products, Storage Solutions, Software
Licenses, Networking Products, and Software Solutions.
HCL services are System Integration, IT Infrastructure Consultancy, ERP Consulting &
Services, Managed Services, HCL CDC, Strategic Outsourcing, Networking Infrastructure and
Facilities Management.
The UATA hard drive (and cable) have been replaced by a SATA hard drive (cable
included with the motherboard). Effects on assembly: the hard drive uses a different cable
from the one shown below, and plugs into a different spot on the motherboard.
The Zalman fan has been replaced by a three-speed Antec fan with a 4-pin power
connector. Effects on assembly: the fan plugs into main power instead of the
motherboard; the power-supply fan plugs into the motherboard.
The video card and DVD-ROM drive are different. Effects on assembly: none, but
slightly different pictures.
The 2005.08.23 standard workstation has more changes. There turns out to be a serious bug in
the motherboard BIOS in the 2005.08.23 workstation, and fixing that bug requires the following
extra steps once the computer has beeped:
On a working computer, download the file A8V-ASUS-0213.ROM from the Asus A8V
download page. This file has MD5 checksum 9c44e207cb3e37a6dc797aa6e1b99f5e.
On a working computer, rename the file as A8VB.ROM and burn that file to a CD.
On the standard workstation, as soon as the initial boot screen appears, press Alt-F2 to
enter the BIOS EZ Flash utility, and then insert the CD. The EZ Flash utility will read
A8VB.ROM from CD, erase the system's BIOS, and copy A8VB.ROM to the system's BIOS;
don't turn the computer off while this is happening!
After reboot, don't worry about the bad-checksum message; simply press F2 to continue.
Desktop refers to the surface of a desk.
The term has been adopted as an adjective to distinguish office appliances (such as photocopiers
and printers) which can be fitted on top of a desk, from larger equipment covering its own area
on the floor.
A laptop (also known as a notebook)[1][2] is a personal computer designed for mobile use.
[3][4][5]
A laptop integrates most of the typical components of a desktop computer,
including a display, a keyboard, a pointing device (a touchpad, also known as a trackpad,
and/or a pointing stick) and speakers into a single unit. A laptop is powered by mains
electricity via an AC adapter, and can be used away from an outlet using a rechargeable
battery. A laptop battery in new condition typically stores enough energy to run the
laptop for three to five hours, depending on the computer usage, configuration and power
management settings. When the laptop is plugged into the mains, the battery charges,
whether or not the computer is running, with the exception of some laptops.
Portable computers, originally monochrome CRT-based and developing into the modern
laptop, were originally considered to be a small niche market, mostly for specialized field
applications such as the military, accountants and sales representatives. As portable
computers became smaller, lighter, and cheaper and as screens became larger and of
better quality, laptops became very widely used for all purposes.
Reliability testing
A Reliability Sequential Test Plan
The purpose of reliability testing is to discover potential problems with the design as early as
possible and, ultimately, provide confidence that the system meets its reliability requirements.
Reliability testing may be performed at several levels. Complex systems may be tested at
component, circuit board, unit, assembly, subsystem and system levels. (The test level
nomenclature varies among applications.) For example, performing environmental stress
screening tests at lower levels, such as piece parts or small assemblies, catches problems before
they cause failures at higher levels. Testing proceeds during each level of integration through
full-up system testing, developmental testing, and operational testing, thereby reducing program
risk. System reliability is calculated at each test level. Reliability growth techniques and failure
reporting, analysis and corrective active systems (FRACAS) are often employed to improve
reliability as testing progresses. The drawbacks to such extensive testing are time and expense.
Customers may choose to accept more risk by eliminating some or all lower levels of testing.
It is not always feasible to test all system requirements. Some systems are prohibitively
expensive to test; some failure modes may take years to observe; some complex interactions
result in a huge number of possible test cases; and some tests require the use of limited test
ranges or other resources. In such cases, different approaches to testing can be used, such as
accelerated life testing, design of experiments, and simulations.
The desired level of statistical confidence also plays an important role in reliability testing.
Statistical confidence is increased by increasing either the test time or the number of items tested.
Reliability test plans are designed to achieve the specified reliability at the specified confidence
level with the minimum number of test units and test time. Different test plans result in different
levels of risk to the producer and consumer. The desired reliability, statistical confidence, and
risk levels for each side influence the ultimate test plan. Good test requirements ensure that the
customer and developer agree in advance on how reliability requirements will be tested.
A key aspect of reliability testing is to define "failure". Although this may seem obvious, there
are many situations where it is not clear whether a failure is really the fault of the system.
Variations in test conditions, operator differences, weather, and unexpected situations create
differences between the customer and the system developer. One strategy to address this issue is
to use a scoring conference process. A scoring conference includes representatives from the
customer, the developer, the test organization, the reliability organization, and sometimes
independent observers. The scoring conference process is defined in the statement of work. Each
test case is considered by the group and "scored" as a success or failure. This scoring is the
official result used by the reliability engineer.
As part of the requirements phase, the reliability engineer develops a test strategy with the
customer. The test strategy makes trade-offs between the needs of the reliability organization,
which wants as much data as possible, and constraints such as cost, schedule, and available
resources. Test plans and procedures are developed for each reliability test, and results are
documented in official reports.