Dell PowerEdge 4350 Dell PowerEdge 4350 Systems Installation and Troubleshooti - Page 57

Pause for User Response, Pause for User, Response, Output Device for, Status Messages, result,

  • 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
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208

Running the Dell Diagnostics
5-9
If the
Pause for User Response
parameter is set to
No
, the diagnostics ignores
some subtests that require your interaction; certain subtests can run only if this
option is set to
Yes
because they require user interaction. Use the
Pause for User
Response
parameter in situations where you may want to prevent subtests that
require user interaction from running´such as when you run the diagnostics
overnight.
2XWSXW±’HYLFH±IRU±6WDWXV±0HVVDJHV
Ordinarily, all status messages appear only on the screen. The
Output Device for
Status Messages
parameter allows you to direct status messages to either a printer
or a file, in addition to the screen. If you choose the
File
option, status messages are
written to a file named
result
. This file is automatically created on a diskette in drive A
when you run the diagnostics. If the
result
file already exists on the diskette, then
new status messages are added to it.
The
result
file is an ordinary American Standard Code for Information Interchange
(ASCII) text file. You can access the
result
file with the MS-DOS
type
command as
follows:
1.
Select
Quit
to exit the diagnostics and return to the operating system prompt.
2.
At the operating system prompt, type the following command and press
<Enter>:
W\SH±UHVXOW
The contents of the file appear on the screen.
After running particular diagnostic tests and viewing the status messages generated
by the tests in the
result
file, you can erase the contents of the file so that it is clear
for the next set of messages generated. Otherwise, the next messages are added at
the end of the previous ones in the file.
2XWSXW±’HYLFH±IRU±(UURU±0HVVDJHV
Ordinarily, all error messages appear only on the screen. The
Output Device for Error
Messages
parameter allows you to direct error messages to either a printer or a file,
in addition to the screen. If you choose the
File
option, error messages are written to
the
result
file used for status messages. This file is automatically created on a diskette
in drive A when you run the diagnostics. If the
result
file already exists on the diskette,
then new error messages are added to it.
The
result
file is an ordinary ASCII text file. You can access and review the
result
file
with the MS-DOS
type
command as described in the previous subsection, ²Output
Device for Status Messages.³
After running particular diagnostic tests and viewing the error messages generated by
the tests in the
result
file, you can erase the contents of the file so that it is clear for
the next set of messages generated. Otherwise, the next messages are added at the
end of the previous ones in the file.