BUG: Multiple "Please Insert Disk" Messages When Installing VB6 Application

ID: Q216158

The information in this article applies to:

Microsoft Visual Basic Learning, Professional, and Enterprise Editions for Windows, version 6.0

SYMPTOMS

When trying to install a distribution set built by the Package and Deployment Wizard (PDW), you receive one of the following messages:

Please insert disk <number>

-or-

Cannot find file '<file or folder name>'. Please insert disk '<number>'

NOTE: <file or folder name> is the name of a setup file or the folder that contains the setup files and <number> is either the number of a diskette or blank.

If you click OK, you are prompted to insert a disk again.

CAUSE

There are two known causes of this problem:

Files from a previous failed installation attempt are still on the system.

-or-
The application's long file name was not converted to a valid short file name when creating the .cab files for a floppy-based distribution set. (There is a space within the first six characters of the application's .exe file name, and the resulting .cab file names contain a space.)

RESOLUTION

Testing for Left-Over Setup Files

In the Windows folder (or Winnt folder on Windows NT) on the target computer, look for a copy of each .cab file from your Setup. If found, delete the .cab file(s).

In the Windows\Temp folder (or the folder specified by the TEMP environment variable in Windows NT), look for a subfolder named Msftqws.pdw. If found, delete the subfolder.

Run Setup again.

Removing Space from CAB File Names

NOTE: The following steps remove the space from the names of your existing .cab files. If you create .cab files using the PDW again later, the problem reoccurs. Instead, you may want to remove any spaces from the first six characters of your project (.vbp) and executable (.exe) file names to avoid this problem in future PDW sessions for this application.

On the development computer, open the Package\Support\<project name>.ddf file in a text editor, such as Notepad. Change the following line:
```
   .Set CabinetNameTemplate="<name with space>*.CAB" 
```
to:
```
   .Set CabinetNameTemplate="<new name without space>*.CAB" 
```
NOTE: <name with space> is the current name that contains a space and <new name without space> is a new name that is six characters long without a space. For example, if the existing CabinetNameTemplate is set to "Test A*.CAB", you should change it to something like "TestAp*.CAB".

Save the changes to the .ddf file and close it.

Double-click <application name>.bat in the Package\Support folder (where <application name> is the name of your application's .exe file) to create new .cab files in the Package folder.

Delete the old .cab files from the Package folder.

Open Setup.lst in a text editor, such as Notepad, and change the following line:
```
   CabFile=<old name of first CAB>.CAB 
```
to:
```
   CabFile=<new name of first CAB>.CAB 
```
NOTE: <old name of first CAB> is the name of your old first .cab file that contained a space and <new name of first CAB> is the new name of your first .cab file.

Run Setup again.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

Additional query words:

Keywords : kbwizard kbAppSetup kbCAB kbVBp kbVBp600bug kbGrpVB
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbbug