SCP-65  (140-1206)          Care and Maintenance       Faxback Doc. # 9855

CARING FOR THE CASSETTE PLAYER

The Radio Shack SCP-65 Stereo-Mate AM/FM Stereo Cassette Player with
Digital Tuning is an example of superior design and craftsmanship.  The
following suggestions will help you care for the SCP-65 so you can enjoy
it for years.

    Keep the SCP-65 dry.  If it gets wet, wipe it dry immediately.
    Liquids can contain minerals that corrode electronic circuits.

    Use and store the SCP-65 only in normal temperature environments.
    Temperature extremes can shorten the life of electronic devices,
    damage batteries, and distort or melt plastic parts.

    Handle the SCP-65 gently and carefully.  Dropping it can damage
    circuit boards and cases, and can cause it to work improperly.

    Keep the SCP-65 away from dust and dirt, which can cause premature
    wear of parts.

    Wipe the SCP-65 with a damp cloth occasionally to keep it looking new.
    Do not use harsh chemicals, cleaning solvents, or strong detergents
    to clean it.

Modifying or tampering with the SCP-65's internal components can
cause a malfunction and might invalidate its warranty and void your
FCC authorization to operate it.  If your SCP-65 is not performing as it
should, take it to your local Radio Shack store for assistance.

THE FCC WANTS YOU TO KNOW

This equipment complies with the limits for a Class B digital device
as specified in Part 15 of FCC Rules.  These limits provide reasonable
protection against radio and TV interference in a residential area.
However, your equipment might cause TV or radio interference even when it
is operating properly.  To eliminate interference, you can try one or more
of the following corrective measures:

    Reorient or relocate the receiving antenna.

    Increase the distance between the equipment and the radio or TV.

    Use outlets on different electrical circuits for the equipment and
    the radio or TV.

Consult your local Radio Shack store or an experienced radio/TV technician
if the problem still exists.

(br/all-02/28/95)