Microsoft KB Archive/138868

WD: Known Issues with the Scanprot Macro Virus Protection Tool

Q138868

The information in this article applies to:

Microsoft Word for the Macintosh, versions 6.0, 6.0.1, 6.0.1a
Microsoft Word for Windows, versions 6.0, 6.0a, 6.0c
Microsoft Word for Windows 95, versions 7.0, 7.0a

SUMMARY

This article describes issues known to occur with the Scanprot.dot template which is supplied with the Application Note titled "Macro Virus Protection Tool" (WD1215 for Windows; MW1222 for the Macintosh). If you are using Word for Windows 95 version 7.0, upgrade to version 7.0a. This latest version of Word is designed to alert you whenever you open a document that contains macros. Because of the way version 7.0a is designed, it does not have some of the problems described below, such as document protection and multiple files issues.

Please note that the Macro Virus Protection Tool and Word version 7.0a are intended as interim tools only. For a permanent solution to macro virus problems, install anti-virus software that is specifically designed to detect Word macro viruses. Such software is available from several third- party companies. For information on anti-virus software vendors, please see the following article in the Microsoft Knowledge Base:

Q49500 List of Antivirus Software Vendors

MORE INFORMATION

Symptom: Documents and Templates protected for forms are unprotected when Scanprot has been used to clean the files of macro viruses.

Cause: This is caused by code in the macro protection tool.

Platform: Macintosh and Windows.

Symptom: When you try to open a password-protected forms document, you are prompted for the protection password. If you click Cancel instead of entering the password, the error message "WordBasic Err=102 - Command failed" appears, and the file opens and is not scanned. Note that if you open the file by choosing it from the File Most Recently Used list, you are not prompted for a password, and the document is scanned.

Cause: Unknown.

Resolution: None.

Platform: Macintosh and Windows.

Symptom: If you have an autoopen macro that protects a document for forms and you choose not to disable the auto macros, the template opens unprotected.

Cause: Unknown.

Platform: Macintosh and Windows.

Symptom: When you try to run Scanprot, you receive the following error message:

WordBasic Err=1177 - Document name or path invalid

Cause: The hard drive name starts with a space. Although the hard drive name can start with any number of spaces, some WordBasic operations will fail if a path name starts with a space.

Resolution: Remove the spaces in the drive name. This will affect other parts of Word and other programs; you may also need to retype the File Locations setting in Tools Options, and you may need to reregister some applications.

Platform: Macintosh

Symptom: On a Macintosh, when you run Scanprot from a Windows 95- formatted floppy disk, you may receive the following error message:

WordBasic Err=154 - Document not found

The macro then halts.

Disks formatted by a computer running Windows NT do not exhibit this problem when used on the Macintosh.

Cause: The error occurs because of the way the Macintosh computer reads the disk label which has been automatically named by Windows 95. The default name given by Windows 95 is "Axxxx".

Resolution: Do either of the following:

Copy Scanprot.dot to the Macintosh hard drive, and open it from within Word
Rename the the floppy disk, using the Macintosh Finder, then open Scanprot from within Word

Platform: Macintosh

Symptom: Cannot install Scanprot with WordMail running.

Cause: If WordMail is started before Word is, it has ownership of the Normal template. Scanprot is unable to save its changes to the Normal template because WordMail has control of Normal.dot.

Resolution: Exit WordMail and then install Scanprot.

Platform: Windows only.

Symptom: "WordBasic Err=1078 - This file could not be found (Global)."

Cause: There is no Normal template, or the Tools/Options/File Locations/User Templates setting points to the wrong folder.

This can happen on the Macintosh platform if the Word Settings File has been removed, and the Normal template is not on Word's search path.

Resolution:

Click OK.
Quit Word (this creates a Normal template).
Restart Word.
In the Tools/Options/File Locations tab, correct the setting for User Templates.
Reopen Scanprot.dot.

Platform: Macintosh and Windows.

Symptom: "WordBasic Err=1078 - This file could not be found (<file name>)." Where <file name> is the name of your document.

Cause: This can happen on the Macintosh platform if there is a space at the end of the file name.

Resolution: Rename the file to remove the space after the file name.

Platform: Macintosh

Symptom: "WordBasic Err=1025 - Word cannot open the document <file name>."

Cause: The scanning portion of the Protection Tool opened a main document, and it can't find the attached data document (the data document was renamed, moved, or deleted).

Resolution: When asked if you want to locate the data document, answer "Yes." Locate the data document and click OK.

If you answer "No," the main document will not be scanned.

Platform: Windows and Macintosh.

Symptom: The message "This file should be converted into a Master Document" appears.

Cause: The scanning tool encountered a Word 4.x or Word 5.x File Series.

Resolution: Answer "No." If you answer "Yes," the scanning continues, but an untitled master document is created, and a Word 6.0 document is created for each document in the file series. In addition, the same question will appear for each subsequent file in the File Series that has a Next File. The remainder of the documents will also produce an untitled document (a master document with the remainder of the files), but it does not create any Word 6.0 copies of the files.

Platform: Macintosh only.

Symptom: Mouse pointer is corrupted; it displays as an arrow, an italic I-bar, or some other unexpected shape.

Cause: Unknown; happens during File Find portion of scan tool.

Resolution: Wait for the usual pointer shape to return.

Platform: Macintosh only.

Symptom: There is no "wait" mouse pointer while the scanning portion of the tool works. The user receives no indication that the macro is still running.

Cause: Unknown; this happens during the File Find portion of scan.

Resolution: Wait.

Platform: Macintosh only.

Symptom: File names on NT server are truncated from long file names to 8.3 nomenclature.

Cause: Unknown.

Resolution: Unknown.

Platform: Macintosh only.

Symptom: Scanning tool ignores Windows files when run on Macintosh.

Cause: When a file is copied from a PC disk to a Macintosh, the file type is incorrectly registered as "text." The scanning tool looks only for Word documents and templates.

Resolution: Open the Word for Windows files in Word for the Macintosh, and save the documents. Run the scan tool again.

Platform: Macintosh only.

Symptom: "Bad file name error" when you open files from a PC floppy disk while using a Macintosh.

Cause: Anomaly in the WordBasic FileOpen Dialog call.

Resolution: Change the name of the floppy disk after inserting it into the Macintosh drive.

Platform: Macintosh only.

Symptom: When the scan tool examines documents with passwords, you are prompted to enter the password twice.

Cause: Unknown.

Resolution: Enter the password each time you are prompted for it.

Platform: Windows and Macintosh.

Symptom: When you open a file known to be infected, the scan tool doesn't run.

Cause: The Winword7.reg file has been double-clicked. This removes the registry information that Scanprot created.

Resolution: Delete the Scanprot macros from the Normal.dot file and reinstall Scanprot.

Platform: Windows only.

Symptom: "WordBasic Err=1078 - This file could not be found (<aliasname>)."

Cause: The scanning tool searched alias names that were on the Recent Documents list on the Apple menu.

Resolution: None.

Platform: Macintosh only.

Symptom: The scanning tool shows the message "The file <aliasname> has been cleaned and is a template file, convert to document?"

Cause: Unable to differentiate between aliases and documents in WordBasic.

Resolution: None.

Platform: Macintosh only.

Symptom: Right-click a template with macros, and click Print on the File menu. When Word starts and displays the macro alert, choose "Yes" to disable the macros.

Result: The new file is created based on the template but does not print.

Resolution: None.

Platform: Windows only.

Symptom: Using the Open command from the File menu produces the error "WordBasic Err=1078 - This file could not be found <file name>." (where <file name> is the name of your file) when choosing to open a file.

Cause: This can happen on the Macintosh platform if the file name has a space at the end of the file name.

Resolution: Rename the file to remove the space after the file name.

Platform: Macintosh

Symptom: When you open a Word attachment from electronic mail and Word is not currently running, Word becomes infected with the virus

Cause: Unknown.

Resolution: Start Word first prior or opening mail. Open the electronic mail and then open the Word attachment.

Platform: Windows.

Symptom: When running Scanprot in Word 7 under Windows 95, you may receive page fault errors or illegal command errors when trying to create a new file from the Start button, from a New document, from the New document button on the Office Shortcut Bar, or within Word from the File New command.

Cause: Scanprot changes some Registry items.

Solution: Close Word, double-click on the winword7.reg file, then start Word and quit from Word. This will register Word.

-or-

Run Word or Office Setup using the "/Y" switch to re register all items.

This problem was corrected in Word version 7.0a. For additional information, please see the following article in the Microsoft Knowledge Base:

Q146059 Page Fault in KERNEL32.DLL When You Open or Create a Document

Symptom: When you run Scanprot, you receive the following error message:

WordBasic Err=102 - Command Failed

followed by

Not enough memory to complete the operation

Cause: The FindFile WordBasic command is not functioning.

Resolution: Delete the Microsoft Find File folder, located in the System:Preferences folder.

-or-

Reinstall the Shared Code dll files (the OLE Client DLL, the OLE Reg DLL, and the OLE Server DLL). To do this, delete or rename the Shared Code folder, located in the System:Extensions folder, and then reinstall Word or Office.

Symptoms: Scanprot gives the following error message:

WordBasic Err=513

Cause: Scanprot is trying to scan a file whose name is complex.

Resolution: Simplify or shorten the file name by removing multiple spaces and punctuation. After the file has been scanned and found clear of viruses, you can rename the file back to its original file name.

Platform: Macintosh

Symptom: When Word is not running and you right-click a document from Windows 95 and choose Print, a WordBasic error 100 (Syntax Error) appears and the document is not printed.

Cause: This problem occurs when the Scanprot.dot macros have been manually removed from your Normal template (for example if Normal.dot is renamed or deleted). Scanprot.dot changes entries in the registry that instruct Word how to handle printing and opening documents from Windows. These DDE commands are not syntactically correct and will generate the error when a document is launched.

Resolution: Reopen Scanprot.dot and let it install its macros in the Normal template. The commands that have syntax problems in the registry are not used when the Scanprot macros are installed.

Platform: Windows 95

Symptoms: Nothing happens when you try to merge the Word Settings (5) file with Word 6.0.1.

Cause: Unknown.

Resolution: None.

Platform: Macintosh.

Symptoms: AutoOpen macros execute only when the document is opened from the MRU list. They do not execute when the document is opened by pressing CTRL+O or by clicking Open on the File menu.

Cause: Unknown.

Resolution: Open the document by clicking Open on the File menu, or by pressing CTRL+O.

Additional query words: beam scan831 scan831.doc Scanprot.dot scan prot prank concept

Keywords : kberrmsg kbtool winword macword word6 word7 word95
Issue type : kbbug
Technology :