Filter
Top Products
Chapter 4: Maintaining the PowerStation Resolving Problems
PA PowerStation User Guide 4-11
Resolving Problems when Starting Up
Some of the most common problems that users encounter with PCs occur
when they start up their systems. This section describes some problems
that may occur in the PA PowerStation during startup and solutions for
these problems.
The LED Power indicator on the back of the unit does not light
1 Check to see whether the power switch is in the On position, and the
PA PowerStation is operating correctly.
a. If the PA PowerStation appears to be operating properly, the LED
indicator may be defective. Contact your Parker equipment
supplier or Parker Product Technical Support department for
assistance.
b. If the PA PowerStation does not appear to be operating properly,
restart the PowerStation.
2 Check the DC power line to determine whether the DC voltage is
either 12VDC or 24VDC.
3 Check the power connector to determine whether the leads are
properly connected and not reversed. The positive line should
connect to the positive terminal, the negative lead should connect to
the negative terminal, and the ground lead should connect to the
ground terminal.
4 Check to see if you have a blown fuse. To replace the fuse, see
Replacing the Fuse on page 4-8.
The startup halts with the Award (System Info) screen displayed
1 Check for a loose CF card.
Restart the PA PowerStation.
The AUTOEXEC.BAT file and/or CONFIG.SYS file does not execute properly
Some startup problems are caused by a corrupted or modified
AUTOEXEC.BAT or CONFIG.SYS file. Parker includes backup copies of these
files in the \CTC directory on your PowerStation’s CompactFlash Disk and
on the PowerStation Start Disk. These files are called AUTOEXEC.CTC and
CONFIG.CTC.
For a complete listing of the AUTOEXEC.BAT and the CONFIG.SYS files, see
Appendix B.
If you suspect a problem with either the PA PowerStation’s AUTOEXEC.BAT
or CONFIG.SYS files, use the ROM-DOS Copy command to create a backup
copy of your current file and overwrite the suspect file with the appropriate
backup file. For example, if the AUTOEXEC.BAT file becomes suspect, type
the following commands at the ROM-DOS prompt:
copy autoexec.bat autoexec.old
copy \ctc\autoexec.ctc autoexec.bat