Microsoft KB Archive/125206

Contents of MSWORKS3.TXT for Works 3.0a and 3.0b (Part 1 of 4)

PSS ID Number: Q125206 Article last modified on 03-10-1999

WINDOWS:3.0a,3.0b

WINDOWS

=
========================================================= 3.00a 3.00b WINDOWS kbreadme

= SUMMARY =

This article contains Part 1 of the text from the MSWORKS3.TXT file for Works for Windows, versions 3.0a and 3.0b.

For the contents of Parts 2-4, please query in the Microsoft Knowledge Base for the following articles:

ARTICLE-ID: Q125208 TITLE: Contents of MSWORKS3.TXT for Works 3.0a and 3.0b (Part 2 of 4)

ARTICLE-ID: Q125207 TITLE: Contents of MSWORKS3.TXT for Works 3.0a and 3.0b (Part 3 of 4)

ARTICLE-ID: Q125209 TITLE: Contents of MSWORKS3.TXT for Works 3.0a and 3.0b (Part 4 of 4)

=
======================================================== MSWORKS3.TXT =====================================================================

Works 3.0a for Windows Troubleshooting/Readme File

This file contains late-breaking information about Microsoft Works 3.0 for Windows. This consists mainly of troubleshooting information that you might find useful, plus documentation of some common error messages that you may encounter.

You can read this file on screen or print it by choosing Print from the File menu.

= TABLE of CONTENTS =

A. Common Questions and Answers A1. System Hangs Entering Works Communications A2. Printing Envelopes with an Envelope Feeder A3. Changing the Default Font A4. Opening Works 3.0 for Windows files in Word 6.0 for Windows A5. Removing Bullets from Word Processor Document A6. How to Delete, Move, or Copy a File A7. Menu Commands not Accessible A8. Printing Multiple Copies of a Label A9. Using Templates from a Previous version of Works A10. Text Columns do not Align A11. Deleted File appears in Recently Used File list or under File menu A12. Call Waiting Causes Problems with Works Communications A13. Spreadsheet Prints Blank Pages A14. Exchanging Files with Works for the Macintosh using Macintosh PC Exchange A15 Exchanging Files with Works for the Macintosh using Networks, Apple File Exchange, or another 3rd party utility

B. Common Error Messages B1. Setup Error: While registering OLE servers… B2. Invalid SHARE parameters B3. Works requires SHARE.EXE in order to run B4. Cannot find file or file already open B5. Header too tall B6. Footer too tall B7. No PC Card installed on COM 3 B8. Device Conflict on COM 3 B9. Waited too Long for Response B10. Not Enough Memory to Undo B11. Operator Missing or Not Valid B12. OLE Registration Database incorrect. Run Setup. Continue anyway?

C. Hewlett-Packard DeskJet Printers C1. Printing Envelopes C2. Printing Color Charts

D. Canon BJ-200, BJ-300, BJC-600 D1. Printing Envelopes

=
=============================================== A. Common Questions and Answers ============================================================

A1. System Hangs Entering Works Communications
* If you have a Pentium Processor and you are running Windows for Workgroups 3.11 you must obtain an updated SERIAL.386 driver for Windows for Workgroups 3.11. You can obtain this driver from Microsoft Product Support Services, Microsoft Download Service, or the CompuServe Software Library.

* If you are encountering this problem and you are not using a computer that has a Pentium processor then the updated SERIAL.386 will not solve your problem. In  this case you are experiencing a hardware interrupt conflict where you have more than one device in your computer configured for the same interrupt request. This can occur if you have an internal modem configured for COM 1 and a physical COM 1 port on your system. You must disable the physical COM 1 port in order for the modem to work correctly. Refer to your hardware documentation for instructions for disabling serial ports. This can occur with other devices as well, such as a sound card, network card, or other add-in peripheral. Please contact your hardware vendor for help resolving hardware interrupt conflicts.

There is a workaround if the port involved in the interrupt conflict is not the port that your modem is connected to. You can add the following lines to  the MSWORKS3.INI file that is in your Windows directory to disable auto port detection.

[Communications] DisablePortChecking=1

After adding these lines to your MSWORKS3.INI file you will need to restart Works 3.0 for Windows. Now when you start the communications module your system should not hang. You will need to manually select the port that your modem is on and choose Test. If your system hangs at this point then we know that the interrupt conflict involves the port that you selected. You will need to resolve the hardware interrupt conflict before you will be able to use the Works communication module.

A2. Printing Envelopes with an Envelope Feeder
To print envelopes from the envelope feeder on your printer, you must tell Works that you have an envelope feeder installed. First, select Options from the Tools menu. Select &quot;Printer's envelope feeder is installed&quot; then choose OK. If the &quot;Printer's envelope feeder is installed&quot; option is not enabled the printer will try to print the envelope(s) from the manual feed tray.

A3. Changing the Default Font
Works 3.0 for Windows allows you to choose whatever font you want as your default font. To set your default font for the Word Processor for example, while you are in a Word Processor document you would choose Font and Style... from the Format menu. While you are in the Font and Style dialog you would select the Font name, size, color, etc. then choose the Set Default button. This will take effect with the next Word Processor document that you create. The Word Processor and Database form view will use the same default font, while the Spreadsheet and Database list use the same default font.

A4. Opening Works 3.0 for Windows files in Word 6.0 for Windows
If you receive the error message &quot;This is not a Works for Windows file&quot; when you are attempting to open a Works 3.0 for Windows file into Word 6.0 for Windows, you need to turn on the Confirm Conversions option in the File Open dialog of Word 6.0 for Windows. Once you have enabled Confirm Conversions then you can select the Works 3.0 for Windows converter from the list of available converters in Word 6.0 for Windows. If this option is not available you will need to obtain the Word 6.0 for Windows supplemental conversion kit. The supplemental conversion kit is available on the Microsoft Download Service, on CompuServe in the Software Library, and from Microsoft Word Support.

A5. Removing Bullets from Word Processor Document
When you add Bullets to a Word Processor document in Works for Windows, the only way to remove the bullets is through the Paragraph... command under the Format menu. In the Paragraph dialog box, you need to select the Indents and Alignment tab then uncheck the Bulleted option.

A6. How to Delete, Move, or Copy a File
If you want to move, delete, copy, or rename a file that you created in Works for Windows you can do this in the File Organizer Wizard or through the Windows File Manager. The File Organizer Wizard can be accessed through the Create New File option under the File menu. Selecting the Create New File option will bring up the Startup dialog. In the Startup dialog, first choose Use a WorksWizard then you can select the File Organizer option from the list of available Wizards.

A7. Menu Commands not Accessible
After you open or save a document for the first time, you may find that most menu commands are unavailable. For example, choosing Font & Style from the Format menu may result in no action, while Save and Print in the File menu may work correctly. This may indicate that you have an incorrect version of the file COMMDLG.DLL on your computer. This file should be located in your WINDOWS\SYSTEM subdirectory, but we have found it in various locations.

Carefully follow the steps below to resolve this problem. 1. Start File Manager (usually located in the Main group of Windows   Program Manager). 2. From the View menu, choose All File Details. 3. From the File menu, choose Search. 4. In the Search For box, type &quot;commdlg.dll&quot; (without the quotation   marks) and enter the C:\ to search your C drive. Repeat this process for each hard drive you have on your computer. 5. If commdlg.dll is found in any directory other than the WINDOWS\SYSTEM directory, rename each of the files in   directories other than WINDOWS\SYSTEM to COMMDLG.OLD. 6. Next we need to verify the version of the file left in the WINDOWS\SYSTEM directory. If it is not present, or the size is   different than those listed in the table below continue on to    step 7, otherwise just restart Windows since step 5 should have resolved the problem.

Windows Version     File Date     File Size      Disk --     3.1             3/10/92       89248 bytes      4 3.11           11/1/93       97936 bytes      1

7. Exit Windows to MS-DOS and use the following command to expand the file from the original Windows disk (shown above):

expand a:commdlg.dl_ c:\windows\system\commdlg.dll

Note: You will need to substitute the path to your WINDOWS\SYSTEM directory if it is different than the one shown above. 8. Restart Windows and test Works. It should operate correctly now. Text Continued in Part 2 of 4…

KBCategory: kbreadme KBSubcategory: wworkskb mwksole

Additional reference words: kbhowto 3.00a 3.00b w_works readme.txt Tools Options Hang ====================================================================== Version : WINDOWS:3.0a,3.0b Platform : WINDOWS ============================================================================= Copyright Microsoft Corporation 1999.