HP Omnibook 800csct Service Manual

							83Appendix B - Hewlett-Packard Password
Removal Policy
If the user forgets the system password, there is a master password that will
unlock the OmniBook.  The user  calls Technical Support to determine this
master password as follows:
1. Support will tell the user the keys to type at the password entry screen:
[Alt][Shift][f10]
2. The OmniBook generates and displays an encoded master password.
This is displayed under the normal password entry area.  At this point, this
is the only password that will unlock the OmniBook unless the user
presses [ESC] to remove the encoded master from the password entry
screen.  Then the users stored password can be entered.
3. The user reads the encoded master password to Support.
4. Support runs a program that decodes the encoded password, and reads
the decoded password (alphanumeric) to the user.
5. The user types in the decoded password.
6. OmniBook decodes the encoded master password it generated and
compares it to the decoded password typed in by the user.
7. If the two passwords match, the OmniBook is unlocked.  The forgotten
password is automatically erased.  Support can then guide the user
through the process of entering a new  password.
8. If the two passwords do not match, the previous sequence must be
repeated until the user correctly enters a master password.
The encoded master password is an eight-character alphanumeric sequence
that the OmniBook generates at random every time the appropriate keys are
pressed in the password entry screen.  Because it is generated randomly, a
master password can only be used to unlock the OmniBook once.  If the user
forgets the password at another time, it will require another call to Support.  (If
the user presses the appropriate keys by mistake, pressing [ESC] will allow
entering the stored password.)
The password descramble programs for the HP OmniBook Notebook PCs  are
protected as HP Company Private information.  They may not be copied,
backed-up, printed or distributed.  There are only six official copies of each
program.
In addition to the program being protected, its use is also controlled.  Hewlett-
Packard and authorized support providers must ensure with written evidence
that the OmniBook that is being descrambled is actually in the hands of the
units actual and current owner.  This requires a sales receipt showing the unit
serial number and owners name, or a written statement from the owner
attesting that he or she is the owner of the unit.  The statement can be a fax
copy of the document.  The fact that the unit is in the hands of an HP
representative on behalf of the customer is not evidence of ownership.  In
addition, HP will not descramble a unit for any non-owner, even if it involves 
						

							84law enforcement agencies.  If you receive such a request, you should notify
management and HP Corporate Legal immediately.  (These requests may
require a court order prior to our participation.)
Further, you must log the name, serial number and date of the running of the
descramble program, and file the written backup with the log. The log and
backup are subject to standard record retention process and review.
The final issue relating to descramble of passwords is that HP cannot provide
information to users that would assist them in improperly descrambling a
password and opening a unit. 
						

							85Appendix C - Hewlett-Packard TFT Display
Quality Statement
TFT display manufacturing is a high precision but imperfect technology and manufacturers
cannot currently produce large displays that are cosmetically perfect.  Most, if not all, TFT
displays will exhibit some level of cosmetic imperfection.  These cosmetic imperfections may be
visible to the customer under varying display conditions and can appear as bright, dim or dark
spots.  This issue is common across all vendors supplying TFT displays in their products and is
not specific to the HP OmniBook display.
HP OmniBook TFT displays meet or exceed all TFT manufacturers’ standards for cosmetic
quality of TFT displays.  HP does not warrant that the displays will be free of cosmetic
imperfections.  TFT displays may have a small number of cosmetic imperfections and still
conform to the display manufacturers’ cosmetic quality specifications.
Here are some guidelines to use in determining what action to take on customers’ complaint of
cosmetic imperfection in their TFT display:
1. The unit should be viewed in the customers normal operating condition.
This means if the customer uses the unit predominately in DOS, or Windows, or in some
other application or combination of applications, that is where the determination shall be
made.  Self test is not a normal operating condition and is not a sufficient tool to interpret
display quality.
 
2. In the customers normal operating mode:
a) If 4 or more variant pixels appear clustered in the area approximated by a
thumbprint on the display surface, then the display should be considered for
replacement.
b) On OmniBook 4000CT models, if more than 30 total pixels  anywhere on the display
are bad, then the display should be considered for replacement.  On OmniBook
600CT, OmniBook 800CT, OmniBook 5000CT, OmniBook 5500CT, and OmniBook
5700CT models, if more than 15 total pixels anywhere on the display are bad, then
the display should be considered for replacement.
These are the only conditions in this guideline that may call for a replacement due to a defect in
material or workmanship based on the HP Limited Warranty Statement.
3. If a display is considered for replacement, it should be clear to the customer that cosmetic
variations on the replacement display may also exist, and may require the customer to
use a work-around to obscure the cosmetic imperfection.
 
4. Customers with cosmetic-based complaints only, that do not conform to the above
conditions and tests will not normally be considered for display replacement.  It will be left
to the judgment of the HP-responsible person working with the customer, to identify work-
arounds that are reasonable and appropriate for the individual customer.  Customers who
must have a more perfect display solution should consider switching to an OmniBook with
a DSTN display.
We expect over time that the industry will continue to improve in its ability to produce displays
with fewer inherent cosmetic imperfections and we will adjust our HP guidelines as the
improvements are implemented. 
						

							86Appendix D - OmniBook Diagnostics BIOS
Checksums
When running the OmniBook diagnostics program, these checksums can be specified on the
command line with the -c option.
Table 27 - OmniBook F1171 - F1175 BIOS ChecksumsROMDATEC_F-C1Altera-C2Boot-C3Total SUM9608083E55DC8CC600A0E1960910258FDC8C1900DB1B960917D040DC8C190085CC9610093C32DC8C0900E1BE9610114024DC8C0900E5B09610185091DC8C0900F61D9610253E93DC8C3500101F9610283E93DC8C3500101F9610319743DC8C350068CF9611117690DC8C3500481C96112739C9DC8C35000B559612095B2ADC8C16000DB69612193F4ADC8C1600F1D69612312911DC8C1600DB9D970107C12BDC8C160073B7970110952BDC8C160047B7970113E558DC8C160097E4970121B738DC8C160069C4Table 28 - OmniBook F1360 BIOS ChecksumsROMDATEC_F-C1Altera-C2Boot-C3Total SUM961018DC97DC8C09008223961025CA99DC8C35009C25961028CA99DC8C35009C259610312349DC8C3500F4D5961111C19BDC8C3500932796112784D4DC8C35005660961209A635DC8C160058C19612192CF6DC8C1600DF8296123116BDDC8C1600C949970107AED7DC8C1600616397011047D2DC8C1600FA5E97011397FFDC8C16004A8B9701216A45DC8C16001CD1 
						

							87Appendix E - OmniBook Diagnostics Error
Messages
The following are messages that may appear when running the OmniBook diagnostics program.
Hewlett-Packard supplied test messages
The following test messages were supplied by Hewlett-Packard.
CPU
   XXXMHz CPU, speed=XXX (failed).
BIOS flash roms
   OK C-F=XXXX Altera=XXXX Boot=XXXX
   FAIL C-F=XXXX#YYYY ...
PCMCIA CARDS (SyCard supplied)
   Failed: no extender card
   Failed: no SyCard
   Voltage Sense 1 (VS1) Error - Stuck Low
   Voltage Sense 1 (VS1) Error - Stuck High
   Voltage Sense 2 (VS2) Error - Stuck Low
   Voltage Sense 2 (VS2) Error - Stuck High
   Error - INPACK failure
   DMA Write Error - expected XX, received XX
   DMA cycle did not complete:
      Timeout error
      Read Data error
      Missing TC error
      Premature TC error
      Write Data error
      Unknown DMA error
      on DMA channel X
   DMA Status Check Error - XXXX
   DMA Not Complete - 8237A Status = XX
   ERROR - Texas Instruments PCI-1130 not found on PCI Bus
   Socket control r/w error -  wrote XX, read back XX @ offset XX
   Databook Socket control r/w error 2 -  wrote XX, read back XX @ offset XX
   Basic 8 bit I/O read/write failure, wrote XX, read XX
   Basic 16 bit I/O read/write failure, wrote XXXX, read XXXX
   Basic 16 bit common memory R/W failure, wrote XXXX, read XXXX
   16 bit memory read error, wrote 4321, read XXXX
   Data Error, expected XXXX, received XXXX
   Vcc tolerance error (3.3V) = N.NN)
   Vcc tolerance error (5V) = N.NN)
   Vpp2 tolerance error (12V) = N.NN)
   Vpp1 tolerance error (3.3V) = N.NN)
   Vpp1 tolerance error (5V) = N.NN)
   Vpp2 tolerance error (3.3V) = N.NN)
   Vpp2 tolerance error (5V) = N.NN)
   Vpp1 tolerance error (0V) = N.NN)
   Vpp2 tolerance error (0V) = N.NN) 
						

							88   Vpp2 tolerance error (12V) = N.NN)
   Card Vpp2 12V  = N.NN (XX)
   Vpp2 tolerance error (3.3V) = N.NN)
   Vpp2 tolerance error (3.3V) = N.NN)
   Vpp2 tolerance error (5V) = N.NN)
   Vpp1 tolerance error (12V) = N.NN)
   -REG bit error - stuck high
   -REG bit error - stuck low
   Address miscompare, access = XXXXXXXX, latched = XXXXXXXX
   Address miscompare, access = XXXXXXXX, latched = XXXXXXXX
   Error - Wait bit has no effect
   BVD1/-STSCNG (Pin 63) error - stuck low
   BVD1/-STSCNG (Pin 63) error - stuck high
   BVD2/-SPKR (Pin 62) error - stuck low
   BVD2/-SPKR (Pin 62) error - stuck high
   WP/-IOIS16 (Pin 33) error - stuck low
   READY/-IREQ (Pin 16) error - stuck low
   Reset error - stuck low
   Reset error - stuck high
   Card Detect Error -CD1 stuck high
   Card Detect Error -CD1 stuck low
Disk Drives (SCSI HD / internal HD / Floppy)
   Internal Diag error: not enough memory for disk buffer.
   Failed: no scsi or dock connection.
   Error X resetting drive.
   Error reading drive parameters.
   Failed: no formatted Floppy in drive.
   Failed: disk is write protected.
   Error: data read does not match data written.
   (Note: when the above error occurs, the status window will report the
   offset where the mismatch occurred and four bytes of expected and actual
   data as follows: Data ERROR offset NNN wrote:XX-XX-XX-XX read:XX-XX-XX-XX)
   Error X at track T, head H, sector S.
   1.4Mb/813Mb/1.4Gb Ok SeekRetries=N, ReadRetries=N, WriteRetriees=N
   The codes reported translate to the following errors:
   0x00 successful completion
   0x01 invalid function in AH or invalid parameter
   0x02 address mark not found
   0x03 disk write-protected
   0x04 sector not found/read error
   0x05 reset failed (hard disk)
   0x06 disk changed (floppy)
   0x07 drive parameter activity failed (hard disk)
   0x08 DMA overrun
   0x09 data boundary error attempted DMA across 64K boundary or >80h sectors
   0x0A bad sector detected (hard disk)
   0x0B bad track detected (hard disk)
   0x0C unsupported track or invalid media
   0x0D invalid number of sectors on format (PS/2 hard disk) 
						

							89   0x0E control data address mark detected (hard disk)
   0x0F DMA arbitration level out of range (hard disk)
   0x10 uncorrectable CRC or ECC error on read
   0x11 data ECC corrected (hard disk)
   0x20 controller failure
   0x31 no such drive (Compaq)
   0x32 incorrect drive type stored in CMOS (Compaq)
   0x40 seek failed
   0x80 timeout (not ready)
   0xAA drive not ready (hard disk)
   0xBB undefined error (hard disk)
   0xCC write fault (hard disk)
   0xE0 status register error (hard disk)
   0xFF sense operation failed (hard disk)
Battery
   Battery type = None (OK), LiIo (OK), NiMH (OK), ERROR (BIOS not sure)
   Charge state = NA (no bat), NC (no charger), FC (fast charge),
      TC (trickle charge), EC (error charging), WC (waiting to charge)
   B%=100 (percent of battery charged)
   Vb=8.57 (battery voltage)
   Ta=37.9 (Ambient temperature)
SCSI loopback test
   Failure: X Register Read/Write Error
   Failure: NO CABLE, Couldnt find SCSI controller #N
   Failure: X Pin #N (X) is stuck low.
   Failure: X Pin #N (X) is stuck high.
   Failure: X Interrupt line problem
   Failure: X cant Bus Master
   Failure: X cant issue interrupt
HP mouse
   Unable to prepare internal mouse for i/o.
   Failed: X bumper ON while moving X.
   Failed: X bumper and movement X at the same time.
   Failed: (one or more of LEFT RIGHT UP DOWN TOP BOTTOM IN OUT)
   Failed: HMICKEYS or VMICKEYS
   Failed: Vertical calibration lost
   Failed: Horizontal calibration lost
Docked device
   Ok: NOTHING
   Ok: 800 DOCK
      Failed: Red LED
      Failed: Green LED
      Failed: Dock Lock
   Ok: SCSI CABLE
   Error: UNCLEAR
Dock PS2 mouse
   Failed: no dock connected for PS2 mouse.
   Failure code N (X while enabling external PS2 mouse.
   Failed: (one or more of LEFT RIGHT UP DOWN) 
						

							90Dock EEPROM
   FAILED at XXXX: wrote XX read XX.
System hardware configuration (invoked with Ctrl+H)
 Cpu speed (CPU=100 133)
 Display type (DSP=DSTN or TFT)
 Hard disk size (HD=814M .. 1.3G)
 L2 Cache (L2=000 or 256), On or Off
 Op Sys Version (OS=0.04.09...)
 Ram memory (RAM=08 .. 80)
 Volume ID (VOL=1ORID14ABA...)
Watergate Software supplied test messages
The following test messages were supplied by Watergate Software.
CPU test responses
General Register TestAX, BX, CX, DX   --  FAILED
EAX, EBX, ECX, EDX -- FAILEDIndex Register TestSI, DI -- FAILED
ESI, EDI -- FAILEDPointer Register TestBP, SP -- FAILED
EBP, ESP -- FAILEDSegment Register TestDS, ES, SS -- FAILED
FS, GS -- FAILEDFlag Register TestCF, PF, AF, ZF, SF, IF, DF, OF -- FAILEDSimple ArithmeticADC, ADD, DEC, DIV, IDIV, IMUL, INC, MUL,
SBB, SUB -- FAILED
ADC32, ADD32, DEC32, DIV32, IDIV32, IMUL32,
INC32, MUL32, SBB32, SUB32 -- FAILEDLogical OperationsAND, NOT, OR, XOR -- FAILED
AND32, NOT32, OR 32, XOR 32 -- FAILEDString OperationsLODSB, MOVSB, SCASB, STOSB -- FAILED
LODSW, MOVSW, SCASW, STOSW -- FAILED
LODSD, MOVSD, SCASD, STOSD -- FAILEDShift/RotateRCL, RCR, ROL, ROR,SHL,SHR -- FAILED
RCL32, RCR 32, ROL32, ROR 32,SHL32,SHR 32 --
FAILEDInterruptsINT XXXH FailedExceptionsDivide, InvOpCode,CoProc -- FAILEDCo-CPU test responses
Register StackRegisters, ST-Pointer
FLDLZ,FLDPI,FLDLN2,FLDLG2,FLDL2T,FLDL2E,FLD
1 -- FAILEDExceptionsInvOp, DenOp, ZeroDiv, OverF, UnderF,Prec, StackF
-- FAILEDArithmeticsFADD,FDIV,FIADD,FIDIV,FIMUL,FISUB,FMUL,FSU
B -- FAILED
FABS,FCHS,FPREM,FRNDINT,FSCALE,FSQRT,FXT
RACT -- FAILED
FPREM1 -- FAILED 
						

							91ComparisonFBLD/FBSTP, FILD/FIST,FLD/FST,FXCH -- FAILED
FCOM,FICOM,FTST,FXAM -- FAILED
FUCOM -- FAILEDTrigonometryF2XM1,FPATAN,FPTAN,FYL2X,FYL2XP1 -- FAILED
FCOS,FSIN,FSINCOS -- FAILEDMemory test responses
Suspend RAM testFailed: memory manager loadedExtended Pattern And
Address TestCould not allocate buffer
BIOS reports no extended memory available
Error at address XXXXXXXXH
Parity Error at blocks XXXXXXXH-YYYYYYYYH
Parity Error at blocks XXXXXXXH-YYYYYYYYH
Test aborted at block XXXXXXXHBase/UMB Pattern And
Address TestError at memory paragraph XXXXH
Parity Error at paragraphs XXXXH-YYYYH
Test aborted at paragraph XXXXHBase/UMB Bus Throughput
TestError at segment XXXXH
Bus Throughput Test aborted at segment XXXXHEMS Bus Throughput TestNot Enough EMS Memory Available!
Could Not Allocate EMS Memory!
Error at segment XXXXH
Could Not Establish EMS Page Frame Location!EMS Pattern And Address
TestError on page XXXXX
Parity Error on page XXXXX
Test aborted at EMS page XXXXXCode TestBIOS reports no extended memory available
“PC-DOCTOR encountered an unexpected exception while code-
testing memory in protected mode. System halted (this error is
unrecoverable).”Cache test responses
Cache Test“Error at memory block XXXXXXXH”
“Parity Error at blocks XXXXXXH-YYYYYYYH”
“Test aborted at block XXXXXXXXH”VGA test responses
Video PagesAborted at mode XXXH (III)
Mode XXXH (III) page Y failedVideo MemoryPattern Error in mode XXXH (III) plane Y, bits XXXXH Failed
Pattern Error in mode XXXH (III) bits XXXXH FailedColor RegistersCould not initialize mode 13H
DAC-register N  -- Red  , Green  , Blue   -- FAILEDVGA Controller RegistersVideo RAM Enable -- FAILED
Video IRQ -- FAILED
Map Mask Register -- FAILED
Set/Reset Register -- FAILED
Enable Set/Reset Register -- FAILED
Color Compare Register -- FAILED
Data Rotate Register -- FAILED
Read Map Select Register -- FAILED 
						

							92Mode Register -- FAILED
Color Dont Care Register -- FAILED
Bit Mask RegisterTimer chip test responses
Timer chip testClock 0 Not Counting, Clock 1 Not Counting -- FAILED
Clock 2 Not Counting
Could Not Control Clock 2CMOS RAM test responses
CMOS RAM TestAddr XXH Failed, In YYH, Out ZZH
CMOS Checksum Failed, ChkSum is XXH, not YYH,
CMOS Pattern Test -- FAILEDSound test responses
DSPNo sound card detected
DSP Chip Data Path FailedDMANo sound card detected
No DMA Request GeneratedInterruptNo sound card detected
No interrupt generatedSound outputNo sound card detectedKeyboard test responses
Keyboard TestFailed: Fn key
Failed: Contrast Up button
Failed: Contrast Down buttonWindows prevents keyboard testing
OS/2 prevents keyboard testing
Could not test keyboard because of stuck key(s)
Keyboard Power-On Selftest Failed
Keyboard IRQ Failed
Keyboard clock line stuck low
Keyboard clock line stuck high
Keyboard data line stuck low
Keyboard data line stuck high
Interface chip internal diagnostics errorManual keyboard test
Manual Keyboard TestError reading KBD file.
Test aborted before all keys were pressed.LPT test responses
Registers TestWrote XXH, Read YYHExternal LoopbackInterrupt Failed
DATA0-->ERROR
STROBE-->SLCT