INF: Setup Questions & Answers
  
PSS ID Number: Q104391
Article last modified on 02-07-1995
 
1.00 1.10
 
WINDOWS
 

---------------------------------------------------------------------
The information in this article applies to:
 
 - Microsoft Access versions 1.0 and 1.1
---------------------------------------------------------------------
 
======================================================================
  Microsoft® Product Support Services Application Note (Text File)
                   WX0812: SETUP QUESTIONS & ANSWERS
======================================================================
                                                   Revision Date: 9/93
                                                      No Disk Included
 
The following information applies to Microsoft Access®, versions
1.0 and 1.1.
 
----------------------------------------------------------------------
| INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY     |
| ACCOMPANY THIS DOCUMENT (collectively referred to as an Application |
| Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER      |
| EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED      |
| WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR       |
| PURPOSE. The user assumes the entire risk as to the accuracy and    |
| the use of this Application Note. This Application Note may be      |
| copied and distributed subject to the following conditions:  1) All |
| text must be copied without modification and all pages must be      |
| included;  2) If software is included, all files on the disk(s)     |
| must be copied without modification (the MS-DOS®  utility         |
| diskcopy is appropriate for this purpose);  3) All components of    |
| this Application Note must be distributed together;  and  4) This   |
| Application Note may not be distributed for profit.                 |
|                                                                     |
| Copyright (C) 1993 Microsoft Corporation.  All Rights Reserved.     |
| Microsoft, Microsoft Access, and MS-DOS are registered trademarks   |
| and Windows is a trademark of Microsoft Corporation.                |
| Quicken is a registered trademark of Intuit.                        |
|---------------------------------------------------------------------|
 
1.  Q. Why does Microsoft recommend that I remove SHARE.EXE from my
       AUTOEXEC.BAT file if I run Microsoft Windows for Workgroups?
 
    A. We recommend that you remove SHARE.EXE from your AUTOEXEC.BAT
       file only if you run Microsoft Windows for Workgroups in 386
       enhanced mode. When Windows for Workgroups is run in 386
       enhanced mode loads and uses a file-sharing program called
       VSHARE.386, which replaces SHARE.EXE. There is an entry for
       VSHARE.386 in the SYSTEM.INI file.
 
       If you plan to run Windows for Workgroups exclusively in 386
       enhanced mode and not run other applications that require
       SHARE.EXE, you can save approximately 5 kilobytes (K) of
       conventional memory by not loading VSHARE.386 at all. If you
       have already loaded SHARE.EXE, delete it from your AUTOEXEC.BAT
       file and restart your computer.
 
       You are likely to find SHARE.EXE in your AUTOEXEC.BAT file
       because SETUP.EXE automatically inserts the following MS-DOS
       command in your AUTOEXEC.BAT file when you install Microsoft
       Access
 
          <directory>\share.exe /l:500
 
       where <directory> is the name of your MS-DOS directory.
 
       If you load VSHARE.386 and SHARE.EXE is already present,
       VSHARE.386 temporarily disables it. VSHARE.386 takes over file-
       sharing tasks until you exit Windows for Workgroups. VSHARE.386
       then transfers the tasks back to SHARE.EXE, so file sharing is
       available to your MS-DOS-based applications.
 
       Microsoft Access runs correctly with either SHARE.EXE or
       VSHARE.386, but SHARE.EXE limits the number of available locks
       to the number you specified when you loaded the file
       originally. The /L parameter specifies the number of locks; the
       default is 20. VSHARE.386, on the other hand, dynamically
       allocates the number of locks available, based on demand. The
       number of locks available is especially important if you are
       running Windows for Workgroups in a client-server environment.
 
       For additional information on the SHARE.EXE file, please obtain
       Technical Note #95047. You can order this technical note by
       selecting the FastTips Technical Library option from the
       FastTips Main Menu.
 
 2. Q. Why do I get the error message "Outdated 'COMMDLG.DLL' found.
       Please reinstall Microsoft Access" when I install Microsoft
       Access?
 
    A. This error can occur for a number of reasons. To isolate the
       cause, check the following:
 
        NOTE: This example uses the COMMDLG.DLL file. The same problem
        can occur with other .DLL files. These steps can be used to
        resolve any problems with outdated .DLL files.
 
        - Make sure that you have no more than one COMMDLG.DLL file on your
          hard disk. If you have several earlier versions of this file,
          either delete or rename the earlier COMMDLG.DLL files and keep
          only the latest one.
 
          If you are running MS-DOS version 5.0 or later, use the
          following two steps to search for all occurrences of the
          COMMDLG.DLL file:
 
          1. Quit Windows.
 
          2. At the MS-DOS prompt, type the following command for all
             logical drives
 
                dir <drive>:\commdlg.dll /s
 
             where <drive> is the drive on which your Windows
             directory is located, the drive on which you installed
             Microsoft Access, and each drive located in the PATH
             statement in your AUTOEXEC.BAT file.
 
          For versions of MS-DOS earlier than 5.0, you must either go
          into each directory and execute the above DIR command
          without the /S parameter, or use a utility to search for all
          occurrences of the COMMDLG.DLL file.
 
        - Make sure that the COMMDLG.DLL file is located in your Windows
          SYSTEM subdirectory only.
 
        - Make sure that the COMMDLG.DLL file is up to date. The file
          should have one of the three dates below, or later:
 
             03/10/92    (for Microsoft Windows 3.1)
             10/01/92    (for Microsoft Windows for Workgroups)
             10/25/92    (for Microsoft Access)
 
        - Make sure that you are not using a third-party, incompatible
          COMMDLG.DLL file.
 
        - Make sure that no other applications are running with Windows
          before you run Microsoft Access Setup.
 
          You cannot update the COMMDLG.DLL file during installation
          if another application is currently using the file. To
          ensure that all other Windows-based applications are closed,
          use the following five steps:
 
          1. Create a temporary Program Manager group.
 
          2. Move all the icons from the Startup group into the
             temporary group.
 
          3. Back up your WIN.INI file. In the original copy, delete
             all the items from both the run= and the load= lines to
             read:
 
                [windows]
                run=
                load=
 
          4. Restart Windows.
 
          5. After installing Microsoft Access, move the icons from
             the temporary group back into the Startup group and
             restore the WIN.INI file from your backup. Quit and
             restart Windows.
 
       If you follow all the previous instructions and you still get
       an "Outdated DLL" error message, your copy of the COMMDLG.DLL
       file may be corrupt or damaged. To solve this problem,
       reinstall a new copy of this file from your Microsoft Access
       package using the following three steps:
 
       1. Copy the COMMDLG.DL_ file from Disk 1 of your Microsoft
          Access package to a directory on your hard disk.
 
           NOTE: Be sure to copy the COMMDLG.DL_ file, not the
           COMMDLG.DL$ file.
 
       2. Copy the EXPAND.EXE file from the appropriate Windows setup
          disk to the same directory you used in step 1.
 
       3. Use EXPAND.EXE to unpack the COMMDLG.DL_ file and place it
          in your Windows SYSTEM subdirectory. The syntax to complete
          this action is as follows
 
             <drive>:\<directory>\expand commdlg.dl_
             <destination>\commdlg.dll
 
          where <drive> and <directory> correspond to the location of
          EXPAND.EXE and <destination> is the drive and location of
          your Windows SYSTEM subdirectory.
 
       For additional information about outdated DLLs, please obtain
       Technical Notes #93694 and #90863. You can order these
       technical notes by selecting the FastTips Technical Library
       option from the Fast Tips Main Menu.
 
3.  Q. When I try to install Microsoft Access, Setup fails. What
       should I do?
 
    A. Setup problems are often caused by terminate-and-stay-resident
       (TSR) programs that are loaded at the
       MS-DOS level and/or at the Microsoft Windows level.
 
       To determine if TSRs are causing Setup to fail, remove all
       unnecessary TSRs and device drivers from the CONFIG.SYS and the
       AUTOEXEC.BAT files, remove all icons from the Startup group in
       Program Manager, and delete all entries under the load= and
       run= lines in your WIN.INI file.
 
        NOTE: Be sure to back up your CONFIG.SYS, AUTOEXEC.BAT, and
        WIN.INI files before modifying them.
 
       The table below describes some TSRs that are known to cause
       problems with the Microsoft Access Setup program:
 
          Filename       Description
       -----------------------------------------------------------------
          APPEND.EXE     An MS-DOS TSR loaded in the AUTOEXEC.BAT file
 
          SUBST.EXE      An MS-DOS TSR loaded in the AUTOEXEC.BAT file
 
          BILLMNDR.EXE   An automated bill reminder loaded with Quicken®
                         that can reside on the load= line of the
                         WIN.INI file
 
       For additional troubleshooting steps to resolve Setup problems,
       please obtain Technical Note #96109. You can order this
       technical note by selecting the FastTips Technical Library
       option from the FastTips Main Menu.
 
 4. Q. A directory called MS-SETUP.T is left on my hard disk after I
       install Microsoft Access. Can I safely delete this directory?
 
    A. Yes. After Microsoft Access installation is complete, it is
       okay to delete the MS-SETUP.T directory and all the files in
       it.
 
       This directory is not deleted automatically because of a known
       problem that occurs in Microsoft Access Setup when you choose
       the Reboot Your System After Completing Setup option. If you
       choose the Return To Windows After Setup option instead,
       Microsoft Access automatically deletes the
       MS-SETUP.T directory and its contents.
 
5.  Q. Why do I get a general protection (GP) fault when I run Setup?
 
    A. Running the Microsoft Access version 1.1 Setup program in
       Windows standard mode results in a GP fault. To run Setup
       correctly, run it in Windows 386 enhanced mode instead. To
       start Windows in 386 enhanced mode, type the following at the
       MS-DOS prompt:
 
          win /3
 
6.  Q. The AccessWizards are unavailable after I upgrade to Microsoft
       Access version 1.1. How do I get the AccessWizards to work?
 
    A. If the AccessWizards button is unavailable when you create a
       new form or report, it is likely that the MSACCESS.INI file was
       not properly updated. To solve this problem, use the following
       three steps:
 
       1. Rename your current MSACCESS.INI file to a different name,
          such as MSACCESS.BAK. The MSACCESS.INI file is located in
          your Windows program directory.
 
       2. Back up any database (.MDB) files that you have created.
 
       3. Run the Microsoft Access Setup program again.
 
       The MSACCESS.INI file should now be correctly updated.
 
Additional reference words: 1.00 1.10
KBCategory: kbusage kbfasttip kbappnote
KBSubcategory: FstQa
=============================================================================
Copyright Microsoft Corporation 1995.
