PC Win WRmt: Upgrading Windows for Workgroups MailLast reviewed: December 28, 1996Article ID: Q124100 |
The information in this article applies to:
SUMMARYIn order to successfully install version 3.2x of Microsoft Mail for Windows or version 3.2x of Microsoft Mail Remote for Windows over Microsoft Windows for Workgroups version 3.11, certain Windows for Workgroups Mail files must be deleted prior to running 3.2x of Mail for Windows or Mail Remote for Windows SETUP.EXE.
MORE INFORMATIONWindows for Workgroups Mail components have a more recent internal version stamp than version 3.2x of Mail for Windows or Mail Remote for Windows files. The setup process is designed to check this version stamp during installation and ensure that the most recent version of the file is installed or remains on the disk. Since many Workgroup component files share the same file names as Mail for Windows and Mail Remote for Windows files, the Workgroup files remain on the disk. In the case of upgrading a Workgroups client to the Mail for Windows, the Workgroups Mail client components will remain and will continue to operate when running against version 3.2 of Microsoft Mail for PC Networks postoffice. Additionally, Mail for Windows setup will update the Windows for Workgroups MSMAIL.INI and enable spell checking, demonstrations, and Apple Macintosh (MAC) file type translation tables. The Windows for Workgroups Mail files are designed to integrate with and support:
NOTE: This will result in the loss of At Work Fax and unified logins. Special considerations will need to be addressed if the Workgroups user has selected the Doublespace option. In summary, either the Windows for Workgroups machine must maintain the full set of Windows for Workgroups Mail specific files (listed below), or the files should be deleted prior to running 3.2x of Mail for Windows setup. This will update the required files for Mail for Windows. To update the Windows for Workgroups Mail client to version 3.2x of Mail for Windows: NOTE: If Windows for Workgroups files must be replaced with Mail for Windows files, the following procedure should be performed for all Windows for Workgroups client machines prior to deleting the Windows for Workgroups Mail files.
NOTE: The files prefaced with * are Mail specific files that load when MSMAIL.EXE is launched. Files prefaced with # are files that are Mail specific, but are called when some menu item within mail is selected. Both the \WINDOWS and the \WINDOWS\SYSTEM subdirectories should be checked for copies of these files. MSMAIL.EXE and MSMAIL.HLP may reside elsewhere on the disk as well.
*AB DLL 97,600 11-01-93 4:11a #IMPEXP DLL 66,560 11-01-93 4:11a *MAILMGR DLL 51,632 11-01-93 4:11a *MAILSPL EXE 51,792 11-01-93 4:11a *MSMAIL EXE 302,528 11-01-93 4:11a #MSMAIL HLP 76,521 11-01-93 4:11a *MSSFS DLL 266,464 11-01-93 4:11a *PABNSP DLL 44,672 11-01-93 4:11a *STORE DLL 235,072 11-01-93 4:11a #WGPOMGR DLL 80,224 11-01-93 4:11a Microsoft Mail Remote for WindowsMail Remote for Windows will not function properly when installed into a standard Windows for Workgroups version 3.11 installation (due to file version stamps). If only Remote Mail functionality is desired, then the above procedure should be performed prior to running Remote Mail's SETUP.EXE. If both LAN-based Mail (full 3.2x Mail for Windows) and Mail Remote for Windows functionality is desired (switched through the Mail Selector Icon), then:
|
Additional reference words: 3.20 Setup WFW update
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |