====================================================================== Microsoft(R) Product Support Services Application Note (Text File) BV0698: SETUP AND INSTALLATION QUESTIONS & ANSWERS ====================================================================== Revision Date: 11/92 No Disk Included The following information applies to Microsoft Visual Basic(TM) for Windows(TM) versions 1.0 and 2.0. -------------------------------------------------------------------- | 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(R) | | 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 1992 Microsoft Corporation. All Rights Reserved. | | Microsoft and MS-DOS are registered trademarks and Visual Basic | | and Windows are trademarks of Microsoft Corporation. | -------------------------------------------------------------------- 1. Q. What should I do if I receive the "Path file access" error message when I am running Microsoft Visual Basic for Windows Setup? A. After you enter your name or company name, Setup attempts to write this information back to the Setup disk for identification purposes. If your Setup disk is write protected, the "Path file access" error message is displayed when Setup attempts to write to the disk. Back up all write-protected disks to non-write- protected disks, then run Setup again using the non-write- protected disks. 2. Q. When I run Setup, I receive the "Insufficient disk space" error message even though I have verified that I have enough hard disk space. What should I do? A. It is possible to receive the "Insufficient disk space" error message during Setup when sufficient disk space exists to allow installation. This problem occurs most frequently when you are installing version 2.0 of Microsoft Visual Basic for Windows over an existing installation of Visual Basic version 1.0 or 2.0. When you receive the "Insufficient disk space" error message, you can choose to stop the installation process, delete the existing copy of Visual Basic, and then attempt to run Setup again. If you are certain the computer has enough hard disk space, you can choose the Install Anyway button to continue the installation process. If you continue the installation and there is not enough hard disk space, the installation fails and presents a dialog box with Abort, Retry, and Ignore buttons. The "Insufficient disk space" error message may also be displayed if the drive name of your WINDOWS directory is missing from the PATH environment variable or if the size of your temporary Windows swap file increases during Setup. Check the format of the PATH environment variable. Make sure that the drive name for your WINDOWS directory is included in the path to the WINDOWS directory. If you are using Microsoft Windows without a permanent swap file, the temporary swap file may be increasing in size and using up your available hard disk space during Visual Basic Setup. To correct this problem, you can either make additional disk space available or create a permanent Windows swap file. (The size of permanent swap files does not change.) For more information about swap files, please refer to the chapter titled "Optimizing Windows" in the Microsoft Windows "User's Guide." 3. Q. When I run Setup, I receive the error message "Setup was unable to create a program item for VB.EXE." How can I correct this problem? A. This error occurs when Setup performs dynamic data exchange (DDE) with Windows Program Manager if a shell program other than PROGMAN.EXE is specified in your SYSTEM.INI file. You do not need to change your shell program to run Setup. To avoid this error, start PROGMAN.EXE from your custom shell before you run the Visual Basic Setup program. 4. Q. The Setup program was interrupted by the error message "Disk not ready." What should I do? A. The disks must remain in the floppy disk drive until the Setup program has completely installed Microsoft Visual Basic for Windows. If an interruption occurs, delete from your hard disk any files that were installed up to the point of the interruption, then run Setup again.