Word 95: Word 6 Startup Directory Contents Not Copied to Word
Article ID: 134113
Article Last Modified on 8/16/2005
APPLIES TO
- Microsoft Word 95 Standard Edition
This article was previously published under Q134113
SYMPTOMS
When you install Word 7.0 on a computer where Word 6.0 is already
installed, the contents of the Word 6.0 Startup folder is not copied to the
new Word 7.0 Startup folder.
CAUSE
This is by design. The Startup folder typically contains Word add-ins and
templates that contain macros that make 16-bit API calls. These 16-bit API
calls or 16-bit Word add-ins will generate error messages if you run them
in Windows 95. By not copying the contents of the Startup folder to the
Word 7.0 Startup folder, you are less likely to encounter error messages
when you start Word.
WORKAROUND
If you have templates in the Word 6.0 Startup folder that do not contain
macros that make 16-bit API calls, you can copy or move these templates to
the Word 7.0 Startup folder. Under no circumstances should a Word 6.0 add-
in (a 16-bit WLL) be copied to the Word 7.0 Startup folder: it will not
work with Word 7.0. Rather than use a 16-bit WLLs or add-in, you must
obtain a 32-bit update from the add-in author.
Additional query words: word95 7.0 582 library unable load specified word7 winword
Keywords: KB134113