Threat Descriptions

Richard Keil

Classification

Category :

Malware

Type :

-

Platform :

-

Aliases :

Richard Keil, Memorial Abend

Summary

This is not a virus, but we sometimes get queries about "Richard Keil Memorial Abend #27" on Novell Netware servers.

Removal

Based on the settings of your F-Secure security product, it will either move the file to the quarantine where it cannot spread or cause harm, or remove it.

A False Positive is when a file is incorrectly detected as harmful, usually because its code or behavior resembles known harmful programs. A False Positive will usually be fixed in a subsequent database update without any action needed on your part. If you wish, you may also:

  • Check for the latest database updates

    First check if your F-Secure security program is using the latest updates, then try scanning the file again.

  • Submit a sample

    After checking, if you still believe the file is incorrectly detected, you can submit a sample of it for re-analysis.

    Note: If the file was moved to quarantine, you need to collect the file from quarantine before you can submit it.

  • Exclude a file from further scanning

    If you are certain that the file is safe and want to continue using it, you can exclude it from further scanning by the F-Secure security product.

    Note: You need administrative rights to change the settings.

Technical Details

Here is more information from Novell:


MEMORIAL ABENDS DURING NETWARE 3.12 INSTALL
 NOVELL TECHNICAL INFORMATION DOCUMENT
DOCUMENT ID:TID013640 DOCUMENT REVISION:A DATE: 07OCT93 ALERT STATUS:

 Yellow INFORMATION
 Symptom Solution NOVELL PRODUCT CLASS
NetWare OSNOVELL PRODUCT and VERSION:
NetWare 3.12CATEGORY:
InstallationABSTRACT:
Memorial Abends During NetWare 3.12 Install SYMPTOM

"Richard Keil Memorial Abend #27"
TROUBLESHOOTING

The user was trying to install v3.12.
While in INSTALL he
 received the above message. CAUSE

This message was intended to be remarked out before the code
 being frozen.
Many other "memorial abends" were remarked out.
 This error is usually triggered by disk hardware failures. SOLUTION

The user was trying to install v3.12 on a clone machine. When
 they installed v3.12 on a certified machine the problem went
 away.

From what Novell has seen the error is manifest when there is a
 drive deactivation due to hardware failure, bad cabling, and so
 forth.