_ FCO MS630-F001, Excessive parity errors w/16 meg memory +-----------------------------------------------------------------------------+ | | | _ _ _ _ _ _ _ Level of Urgency Page_1_ | || | | | | | | | MS630-CA +--+ Of_3_ | ||d|i|g|i|t|a|l| FCO |F | | ||_|_|_|_|_|_|_| +--+ | |_____________________________________________________________________________| | | | FIELD CHANGE ORDER Number: FCO MS630-F001 | |_____________________________________________________________________________| | Applicability: This FCO is only applicable to those contract and warranty | | customer systems that exhibit the following PROBLEM SYMPTOM, or to contract | | and warranty customers during the add-on installation of a second MS630-CA | | where the existing system MS630-CA is out of rev i.e. A1 or B1. | | [This Revision supersedes the previous release of 7-Aug-1989] | |_____________________________________________________________________________| | Problem/Symptom: | | Excessive system parity errors logged in some MicroVAX II configurations | | with 16 megabytes (2 MS630-CA) of memory, while running certain | | applications that intensively exercise memory. | | | |_____________________________________________________________________________| | Compatibility/Prerequisite FCO: | Est. Time to Install: | | N/A | | | | 1 hr. | |_____________________________________________________________________________| | Special Tools or Test Equipment: | | NONE | |_____________________________________________________________________________| | FCO Parts Information | |_____________________________________________________________________________| | Order by Quantity: Part Number: Description: | | FCO Kit#: | | EQ-01549-01 1 M7609 MS630-CA 8MB memory module | | Rev. A2 or C1* | | *Rev A2 and C1 are functionally and physically | | equivalent and have the ECO installed. | | FA-04854-02 FCO Document | |_____________________________________________________________________________| |EQ Kit Variation System/Option Applic: N/A | |_____________________________________________________________________________| | Approvals | |_____________________________________________________________________________| | CSSE Engineer | F.S. Product Safety | F.S. Logistics | | R.Grogan | N/A | Barry Weinstein | |____________________|__________________________|_____________________________| | CSSE Manager | F.S. Microfiche Libraries| Affected Population: | | Curtis Smith | | 6086 | |____________________| |____________________________ | | MicroMedia Pub | | Initial Kitting: | | Diane MacDonald | | 300 | |____________________| |____________________________ | | Revision: | | Hardcopy Publication: | | B | | 7000 | |____________________| |_____________________________| | FCO Release Date | | Parts Availability: | | 30 Oct 1989 | | NOW | +-----------------------------------------------------------------------------+ _ _ _ _ _ _ _ | FCO MS630-F001 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 2 OF 3 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ FIELD INSTALLATION AND TEST PROCEDURE FOR FCO MS630-F001 -------------------------------------------------------- ** NOTE ** ************************************************************** * When handling any system components/options, be sure to * * follow proper ESD precautionary procedures. This includes * * the use of the Velostat Kit (PN 29-11762). * ************************************************************** 1. Shut down the system by executing the appropriate shutdown command procedure and/or site specific procedures. For example, under VMS use the following DCL command from a priveledged account: $@sys$system:shutdown 2. Power down the system. 3. Connect yourself to the system enclosure via the anti-static wriststrap. 4. Remove the new MS630-C module from its anti-static bag. 5. Remove the old MS630-C module from the system and in its place install the new MS630-C module. 6. Place the old MS630-C module in the anti-static bag and packing box which was used for the new module. 7. Reinstall all enclosure covers and power-on the system. 8. Verify correct functional operation of the new memory module by performing the following: (a) Self Test 6 and 7 (b) MDM Memory Exercisor and Utility (c) Boot Operating System Each of the above should be run/performed without errors. 9. Update the Site Management Guide to reflect this FCO. 10. For additional information refer to the MS630-CA Maintenance Advisory EK-MS6CA-MA. 11. Report this FCO activity on the LARS for in the "Fail Area/Module/FCO/Comments" column. (See example on Page 3.) _ _ _ _ _ _ _ | FCO MS630-F001 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 3 OF 3 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ LARS USA GIA EUROPE Activity - (a)Contract and Warranty W U Y Hardware Segment Code 111 Non Contract/Non Warranty F F F (b)RTD/Off-Site Agreement F Product Line 01 DEC Option MS630-CA MS630-CA MS630-CA Type of Call M M M Action Taken D D I Fail Area-Module-FCO-Comments MS630-F001 MS630-F001 MS630-F001 Material Used EQ-01459-01 EQ-01459-01 EQ-01459-01 (a) Warranty Optimum, Warranty Standard and Warranty Basic (on-site) Agreements. (b) RTD+Return to Digital or Off-Site Agreements; if Field Engineer On-Site, Use Activity Code "F". \^ MS630 \\MS630 \\MS630-F001 \\GROGAN \\1989 \\OCT \\FCO_DOCS