Last revision January 5, 1999 TJD 11171-11175 = December 24-28, 1998 The MQT for LA detector 4 turned off again (second time). It was discovered several days later when it was noticed that the SPHIST-FIT program had been failing. The holiday period plus icy roads led to the delay in discovering the problem. The time that the MQT for LA detector 4 went off was after TJD/SoD = 11171/8613.6014 (time of last apparently good packet based on CONT data but which may already have had lower rates; therefore, possibly after the preceding packet at TJD/SoD = 11171/8611.5534 The problem was fixed by turning off detector module 4 by command BAUB4OFF after TJD/SoD = 11175/52924.1294 (time of last good packet based on DISCLA data) and turning it on by command BAUB4ON (with voltages and LLDs adjusted) before TJD/SoD = 11175/53018.3374 (time of first good packet based on DISCLA data). Therefore, the MQT for LA detector 4 (affects CONT and HER data) was out between 11171/8612 and 11175/53016 and the entire module 4 (also affects DISCLA, DISCSP, and SHER data) was out between 11175/52925 and 11175/53016. Flags 74 and 56 (also temporarily flag 50 for CDFITS) were set. The gain for LA detector 4 was out of balance (no flag 64 was set) between 11171/8612 and 11175/52925. The affected triggers were numbers 7278-7285 which were Burst: 7281, 7283, 7285 Flare: 7279 SAA entry: 7278, 7280, 7282, 7284