Contents of MSWORKS3.TXT for Works 3.0a and 3.0b (Part 3 of 4)
  
PSS ID Number: Q125207
Article last modified on 03-10-1999
 

 
WINDOWS
 

======================================================================
-------------------------------------------------------------------------
The information in this article applies to:
 
 - Microsoft Works versions 3.0a, 3.0b for Windows
-------------------------------------------------------------------------
 
SUMMARY
=======
 
This article contains Part 3 of the text from the MSWORKS3.TXT file for
Works for Windows, versions 3.0a and 3.0b.
 
For the contents of Parts 1,2, and 4, please query in the Microsoft Knowledge Base for the following articles:
 
   ARTICLE-ID: Q125206
   TITLE: Contents of MSWORKS3.TXT for Works 3.0a and 3.0b (Part 1 of 4)
 
   ARTICLE-ID: Q125208
   TITLE: Contents of MSWORKS3.TXT for Works 3.0a and 3.0b (Part 2 of 4)
 
   ARTICLE-ID: Q125209
   TITLE: Contents of MSWORKS3.TXT for Works 3.0a and 3.0b (Part 4 of 4)
 
 ============================================================
 B.  Common Error Messages
 ============================================================
 
 B1.  Setup Error: While registering OLE servers, Setup had
      a Problem with REG.DAT, SHELL.DLL, or disk space.
 ------------------------------------------------------------
   The following conditions can cause this error:
   * An invalid Path parameter in the AUTOEXEC.BAT.
   Entries in the Path that do not contain a drive
   letter will cause this problem. A path statement
   like PATH=C:\;\DOS will cause this problem but
   PATH=C:\;C:\DOS will not. Notice the second example
   includes the drive letter on both Path parameters.
 
   -or-
 
   * A corrupt REG.DAT file
 
   To change your Path in the AUTOEXEC.BAT file
   --------------------------------------------
   1. From the File menu in Windows Program Manager, choose Run.
   2. In the Command Line box, type "sysedit" (without the quotation
      marks) and choose OK.
   3. In the AUTOEXEC.BAT window, locate the Path command.
   4. Change the Path so each entry contains both a drive and directory.
      For example, if Windows is installed in the default directory of
      C:\WINDOWS, the line should read C:\WINDOWS. For example, the
      following is a sample Path statement in AUTOEXEC.BAT:
 
         PATH C:\;C:\DOS;C:\WINDOWS
 
      NOTE: You may want to double-check the entire Path command. Make
      sure that every directory specified has the appropriate syntax. For
      more information about your Path command, see your MS-DOS user's
      guide.
 
   5. From the File menu, choose Exit. Choose Yes to save changes.
   6. Exit Windows and restart your computer.
   7. Reinstall Works for Windows, version 3.0. Because Setup was not
      complete the first time, you do not need to uninstall Works 3.0
      before you reinstall.
 
   To correct a corrupt REG.DAT file
   ---------------------------------
   1. Check to see if there are two REG.DAT files on your hard drive.
      Your REG.DAT file should only be in the Windows directory.
   2. If there is only one copy of the REG.DAT on your hard drive, change
      the filename to REG.OLD to create a backup.
   3. Restart Windows. When Windows restarts, it will not find a REG.DAT
      file so it will re-create one with default settings.
   4. In Program Manager, choose Run from the File menu, and type
      "regedit" (without the quotation marks) then press ENTER.
   5. From the File menu of the Registration Editor, choose Merge
      Registration File.
   6. Switch to the SYSTEM subdirectory of Windows and double-click the
      SETUP.REG file.
   7. The Registration Editor will inform you if the data is registered
      properly. If it was, choose OK to return to the editor.
   8. Close the Registration Information Editor program and save the
      changes.
   9. Now you will need to reinstall Works 3.0 for Windows since the
      installation process did not complete successfully.
 
 B2.  Works requires SHARE.EXE in order to run
 ------------------------------------------------------------
   This problem can occur if you are loading SHARE.EXE
   without the proper parameters and you are running
   Windows in Standard Mode or if you are running Windows
   in 386 Enhanced mode and do not have DEVICE=VSHARE.386
   in the [386Enh] section of your SYSTEM.INI.
 
   If you are running Windows in 386 Enhanced mode make
   sure that you have DEVICE=VSHARE.386 in the [386Enh]
   section of your SYSTEM.INI.
 
   To verify this entry in your SYSTEM.INI follow the steps
   below:
 
   1. Switch to the Windows Program Manager if you are not already there.
   2. Select Run from the File menu.
   3. Type NOTEPAD SYSTEM.INI into the command field and press OK.
   4. Once the SYSTEM.INI file appears in Notepad, choose Find from the
      Search menu.
   5. Type [386Enh] into the Find What field and choose OK
   6. Manually scan through this section of the file for the line
      DEVICE=VSHARE.386, if it does not exist enter it on the line below
      [386Enh].
 
      IMPORTANT NOTE: Be careful what you change in this file, making the
      wrong change may cause Windows to fail the next time you try to
      start.
 
   7. If you added the command DEVICE=VSHARE.386, then pull down the File
      menu and choose Save.
   8. You will need to Close Notepad and restart Windows for the change
      to take place.
 
   If you are running Windows in Standard Mode, then you
   need to start SHARE.EXE from MS-DOS before running Windows.
   If you are using MS-DOS 4.0, SHARE.EXE must be loaded by
   your CONFIG.SYS file, but if you are using MS-DOS 5.0 or
   later SHARE.EXE can be loaded in your AUTOEXEC.BAT.
 
   CONFIG.SYS command for loading SHARE.EXE
   ----------------------------------------
   INSTALL=C:\DOS\SHARE.EXE /L:500 /F:5100
 
   AUTOEXEC.BAT command for loading SHARE.EXE
   ------------------------------------------
   C:\DOS\SHARE.EXE /L:500 /F:5100
 
   This must be loaded after SMARTDRV.EXE if it is present
   in your AUTOEXEC.BAT, otherwise add this line to the top
   of your AUTOEXEC.BAT.
 
   After making these changes, you will need to exit Windows
   and restart your computer, you should now be able to run
   Works for Windows without receiving the above error
   message.
 
 B3.  Too many files open, or invalid Share parameters
 ------------------------------------------------------------
   Refer to the instructions above in section B1 for the
   error message "Works Requires SHARE.EXE in order to run"
   to resolve this problem. You are loading SHARE.EXE from
   either the AUTOEXEC.BAT or CONFIG.SYS without the proper
   parameters.
 
 B4.  Cannot find file or file already open...
 ------------------------------------------------------------
   If the error message "Cannot find file or file already
   open..." is followed by the error message "Not all
   files were loaded in the workspace" then you have saved
   a Workspace that contains files that you have since
   deleted. You can easily disable the Workspace by
   selecting Options from the Tools menu and deactivating
   the Use Saved Workspace option.
 
 B5.  Header too tall
 ------------------------------------------------------------
   Whenever you receive this error message you need to
   increase your top margin in order for your header to
   fit between the header margin and the top margin. The
   top margin should always be larger than the header margin.
   You can change the margin settings under the Page Setup
   option on the File menu.
 
 B6.  Footer too tall
 ------------------------------------------------------------
   Whenever you receive this error message you need to
   increase both your bottom margin and footer margin.
   The bottom margin should always be larger than the footer
   margin. You can change the margin settings under the
   Page Setup option on the File menu.
 
 B7.  No PC Card installed on COM 3
 ------------------------------------------------------------
   This problem may be caused by a 3rd party communications
   driver installed into the SYSTEM.INI. To check your
   communications driver in the SYSTEM.INI, carefully
   follow the steps listed below:
 
   1. Switch to Windows Program Manager if you aren't already there.
   2. Select Run from the File menu of Program Manager.
   3. Type NOTEPAD SYSTEM.INI into the command field and press ENTER.
   4. Scan the [Boot] section, which is normally at the top of the
      SYSTEM.INI, for the line containing COMM.DRV=.
   5. If this line contains COMM.DRV=COMM.DRV then you will need to
      contact Microsoft Product Support for help determining the cause of
      the problem. If this line does not contain COMM.DRV=COMM.DRV then
      continue with the steps below.
   6. Place a semi-colon (;) in front of the line COMM.DRV=, then add a
      new line above it containing COMM.DRV=COMM.DRV.
   7. Once you have made this modification, pull down the File menu and
      choose Save, then pull down the File menu again and choose Exit.
   8. You will need to restart Windows for this change to make a
      difference.
 
Text Continued in Part 4 of 4...
 
Additional query words: kbhowto 3.00a 3.00b w_works readme.txt
======================================================================
Platform          : WINDOWS
=============================================================================
Copyright Microsoft Corporation 1999.