servers, see the “Special Features” section.

restart it using a locked startup floppy. For more details on scanning

errors, we recommend that you remove the server from production and

which you do not have the necessary access privileges. To avoid these

These error messages are issued if a server folder is encountered for



### cannot be checked.

### privileges to this folder. This folder

### You have neither See Files nor See Folders



### cannot be checked.

### to this folder. Folders within this folder

### You do not have See Folders privilege





### cannot be checked.

### to this folder. Files within this folder

### You do not have See Files privilege



### WARNING: This file is still infected!

### It cannot be repaired.

### to the folder containing this file.

### You do not have Make Changes privilege



### files in those folders may be infected!

### to access files in some of the folders. Some

### WARNING: You do not have the proper privileges







(“File” and “Res” privileges for “Other,” “System” and “Self”).

Disinfectant privileges. You should grant Disinfectant all privileges

files on a Gatekeeper-protected system when you have forgotten to grant

One possible cause of unexpected errors is attempting to repair infected



### WARNING: This file is probably still infected!

### granted privileges to Disinfectant.

### Gatekeeper, check to make certain you have

### Unexpected error (nnn). If you are using







us a copy of the file that was being scanned when the error occurred.

specify the error number reported in the message. If possible, also send

author describing what you were doing when the error occurred. Please

in Disinfectant. We would appreciate it if you would send a note to the

Unexpected errors should not occur. It means that there may be an error



### WARNING: This file is still infected!

### to open this file for repair.

### Unexpected error (nnn) occurred while trying



### Unexpected error (nnn).





on MDEF for details.

The MDEF D virus can also sometimes damage applications. See the section



the section on Scores for details.

System file from Apple’s System Software release 6.0.4 or later. See

This error message is also issued when the Scores virus has infected a



by T4, you will get this error message. See the section on T4 for details.

infected by T4 cannot be repaired. If you attempt to repair a file infected

In particular, the T4 virus damages files when it infects them. Files





You should delete it and replace it with a known good copy of the file.

file, but leaves the file damaged. You should not attempt to use such a file.

repaired properly. In this case, Disinfectant removes the virus from the

Viruses sometimes damage files in such a way that they cannot be



### and replace it with a known good copy.

### be repaired properly. You should delete the file

### This file was damaged by the virus, and it cannot







rebuild the desktop. See the “Problem Clinic” section for details.

and busy. In this case, the easiest way to remove the infection is to

The third message above is issued when a Finder desktop file is infected



message above is only issued under System 6.

The first message above is only issued under System 7. The second



section.

errors. For more details on scanning servers, see the “Special Features”

restart it using a locked startup floppy. This should avoid file busy

disks, we recommend that you remove the server from production and

System 6 with MultiFinder, or when scanning server disks. For server

by some other application. This error is common when using System 7,

Your file could not be opened for writing because the file was already open



### WARNING: This file is still infected!

### To repair this file, rebuild the desktop.

### This file is busy and cannot be repaired.



### WARNING: This file is still infected!

### disk and try running Disinfectant again.

### Restart using your locked “Virus Tools”

### This file is busy and cannot be repaired.



### WARNING: This file is still infected!

### disk and try running Disinfectant again.

### Restart using a locked Apple “Disk Tools”

### This file is busy and cannot be repaired.







servers, see the “Special Features” section.

disk. This should avoid file busy errors. For more details on scanning

remove the server from production and restart using a startup floppy

only occur on server disks. For server disks, we recommend that you

with exclusive access by some other application. This message should

Your file could not be opened for reading because the file was already open



### This file is busy and cannot be checked.







Info window. Run Disinfectant again.

memory allocated to Disinfectant in the Get Info window. Close the Get

Finder’s “Get Info” command in the “File” menu. Increase the amount of

Disinfectant. Select the Disinfectant program icon in the Finder. Select the

If you get this error, you should give Disinfectant more memory. Quit



Another possible cause of this error is that the file is damaged.



get this error message.

check them for viruses and, if there is not enough memory available, you

CODE resources. Disinfectant must load these resources into memory to

This error is usually caused by applications which contain very large



Disinfectant was unable to get enough memory to check or repair the file.



### WARNING: This file is probably still infected!

### There is not enough memory to repair this file.



### There is not enough memory to check this file.





created by Studio Session and Super Studio Session.

The same problem has also been reported with the “phrase library” files



which also makes non-standard use of the resource fork.

The same problem has been reported with some files created by MacTran,



Reflex.

These files are not really damaged. They are still usable, but only by

Reflex makes non-standard use of the resource fork in its database files.

Disinfectant also reports that all Reflex database files are “damaged.”



fork.

since StuffIt stores the archived files in the data fork, not the resource

of StuffIt archive files. These “damaged” files are usually still usable

For some reason, we have seen invalid resource information in a number



applications which have damaged resource forks.

infected and contagious. For this reason, you should not attempt to use

WARNING: It is possible for an application to be damaged and yet still be





with the file and you should replace it with a known good copy of the file.

and system files, this usually indicates that something is seriously wrong

usable. For document files, this is usually not a problem. For applications

is not valid resource information. The data fork may still be intact and

fork. This message means that the information stored in the resource fork

data fork. When Disinfectant checks a file, it tries to open the resource

Macintosh files have two parts or “forks:” the resource fork and the



### in an unknown format. It cannot be checked.

### The resource fork of this file is damaged or







disk is ejected and not scanned.

non-Macintosh disk on a scanning station with no mouse or keyboard. The

This error occurs if you insert an uninitialized, damaged, or



### or not a Mac disk. It cannot be scanned.

### The inserted disk is uninitialized, damaged,







Disinfectant again.

the files on the disk to some other disk to make more room and run

free space on the disk before it can repair the file. Try moving some of

infected file on the disk. Disinfectant requires at least a small amount of

This error may occur if a disk is very full and you attempt to repair an



### WARNING: This file may still be infected!

### The disk is too full to repair this file.







send a report to the author.

probably an error in Disinfectant. We would appreciate it if you would

If this error occurs in some other situation, it means that there is



which the disk is directly connected.

over the network. We recommend that you scan the disk using the Mac to

network. TOPS does not permit access to currently active System files

This error should only occur if you try to scan a disk over a TOPS



### System files cannot be scanned over TOPS.







You canceled a scan or disinfection run.



### Scan canceled.







error messages occurred during a scan.

This message appears in the summary section of the report if any other



### and click the error message text.

### explanation of an error message, press Command-?

### NOTE: Some errors were reported. For a detailed







originally attacked the file, so it issues this special message.

infected file. In this case, Disinfectant has no way of knowing which virus

identical. It is possible for only these common parts to be present in an

nVIR A and nVIR B are different viruses, but some of their parts are



### but not contagious.

### File partially infected by nVIR A or nVIR B,







protection mechanisms.

harmless part of the Scores infection will manage to evade Gatekeeper’s

particular, if the Scores virus attacks a Gatekeeper-protected system, a

Partial infections can also arise on Gatekeeper-protected systems. In



but not all of the infection.

which have errors. The other virus tool may remove part of an infection,

Partially infected files sometimes are the result of other virus tools



the file or you may use Disinfectant to remove the infection.

they cannot spread to other files. You may choose to leave the infection in

infection is not contagious. These kinds of infections are not dangerous and

Your file is partially infected by the virus named “xxxxx,” but the



### but not contagious.

### File partially infected by xxxxx,







sections on the WDEF and CDEF viruses for more information.

appreciate it if you would send us a copy of the infected file. See the

yet been reported. If you have not already repaired the file, we would

Your file is infected by a strain of the WDEF or CDEF virus which has not



### File infected by an unknown strain of xxxx







(Scores, nVIR A, etc.).

Your file is infected by a virus. “xxxxx” is the name of the virus



### File infected by xxxxx.







intermittent, it might work the second time.

Disinfectant again on the same file. If the hardware problem is

or the disk drive is not operating properly. You can try running

while trying to read or write a file. They usually mean that the disk itself

These error messages are listed in the report if a hardware error occurs



### WARNING: This file may still be infected!

### this file.

### An I/O error occurred while trying to repair



### this file.

### An I/O error occurred while trying to check





properly.

application damaged in such a way that Disinfectant cannot repair it

handle multiple infections properly and they sometimes leave the

repair the file before running Disinfectant. Some other virus tools cannot

by more than one virus and you attempt to use some other virus tool to

One situation in which this error can occur is if an application is infected





not common, but it can occur in unusual situations.

or it may be damaged in such a way that it cannot be used. This error is

longer infected, you can try running it to see if it works. It may be usable

is still infected, you should delete it. If Disinfectant reports that it is no

Scan the file again with Disinfectant to find out if it is still infected. If it

discovered something wrong with the file. The file may still be infected.

Your file was infected, but while attempting to repair it, Disinfectant



### WARNING: This file may still be infected!

### trying to repair this file.

### An error or inconsistency was detected while





order, with a brief explanation of each one.

This section presents all of Disinfectant’s error messages, in alphabetical








åError Messages



3




3