Lenovo NetVista Hardware Maintenance Manual (HMM) for NetVista 2251, 6830, and - Page 142

Hardware considerations, Applications to operating system to BIOS to hardware

Get Lenovo NetVista PDF manuals and user guides View all Lenovo NetVista manuals
Add to My Manuals
Save this manual to your list of manuals

Page 142 highlights

Not all device drivers are found in the CONFIG.SYS file. Advanced operating systems use .INI files to set up and start devices. Device drivers can access the hardware in five ways. v Operating system direct to hardware using a direct driver Direct drivers, which bypass BIOS, have the advantage of faster throughput, but the disadvantage of limited error-handling capability and reduced software and hardware compatibility and flexibility. This method is not used in the IBM PC Series systems. v Operating system to BIOS to hardware This is the recommended way. It's the most flexible because it is independent of the hardware. v Applications to operating system to BIOS to hardware This method is inflexible and is dependent on the operating system. v Applications to BIOS to hardware This method has some flexibility but it is dependent on the BIOS. v Applications to hardware This method is dependent on the hardware and is very inflexible. However, it is very fast, very efficient, and it has no overhead. Hardware considerations Use the following tools to help identify and resolve hardware-related problems. v Power-on self-test (POST) v POST Beep codes v Test programs v Error messages POST does the following operations. v Checks some basic system board operations v Checks the memory operation v Starts the video operation v Verifies that the diskette drive is working v Verifies that the hard disk drive is working Use the test programs that come with this HMM or with the system you are servicing to test the IBM components of the system and some external devices. Also, from the DOS prompt or from OS/2 Utilities, use the CHKDSK command to check and repair hard disk data allocation errors. Error messages generated by the software (the operating system or application programs), generally are text messages. However, error messages can be text, numeric, or both text and numeric. Any time there is an error message indicating a problem with the system, follow the General Checkout procedures in this HMM to resolve the problem. Basically, there are five types of error messages. v POST error messages are displayed when the POST finds problems with the hardware or detects a change in the hardware configuration. 134 Hardware Maintenance Manual

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
Not all device drivers are found in the CONFIG.SYS file. Advanced operating
systems use .INI files to set up and start devices.
Device drivers can access the hardware in five ways.
v
Operating system direct to hardware using a direct driver
Direct drivers, which bypass BIOS, have the advantage of faster throughput, but
the disadvantage of limited error-handling capability and reduced software and
hardware compatibility and flexibility. This method is not used in the IBM PC
Series systems.
v
Operating system to BIOS to hardware
This is the recommended way. It
’
s the most flexible because it is independent of
the hardware.
v
Applications to operating system to BIOS to hardware
This method is inflexible and is dependent on the operating system.
v
Applications to BIOS to hardware
This method has some flexibility but it is dependent on the BIOS.
v
Applications to hardware
This method is dependent on the hardware and is very inflexible. However, it is
very fast, very efficient, and it has no overhead.
Hardware considerations
Use the following tools to help identify and resolve hardware-related problems.
v
Power-on self-test (POST)
v
POST Beep codes
v
Test programs
v
Error messages
POST does the following operations.
v
Checks some basic system board operations
v
Checks the memory operation
v
Starts the video operation
v
Verifies that the diskette drive is working
v
Verifies that the hard disk drive is working
Use the test programs that come with this HMM or with the system you are
servicing to test the IBM components of the system and some external devices.
Also, from the DOS prompt or from OS/2 Utilities, use the
CHKDSK
command to
check and repair hard disk data allocation errors.
Error messages generated by the software (the operating system or application
programs), generally are text messages. However, error messages can be text,
numeric, or both text and numeric.
Any time there is an error message indicating a problem with the system, follow
the General Checkout procedures in this HMM to resolve the problem.
Basically, there are five types of error messages.
v
POST error messages
are displayed when the POST finds problems with the
hardware or detects a change in the hardware configuration.
134
Hardware Maintenance Manual