PRB: Visual Basic Setup Fails on Disk 2

ID: Q136268

The information in this article applies to:

Microsoft Visual Basic Standard, Professional, and Enterprise Editions, 16-bit and 32-bit, for Windows, version 4.0
Microsoft Visual Basic Standard and Professional Editions for Windows, version 3.0

SYMPTOMS

In Visual Basic, the Setup program fails after you insert Disk 2.

CAUSE

This does not necessarily mean that the disk is defective. It could be that the physical drive is not reading the disk properly.

RESOLUTION

You may need to use the MS-DOS DRIVPARM command to correct the problem. If a physical drive is not reading a disk properly and the disk is not defective, the MS-DOS DRIVPARM command in the CONFIG.SYS file can often correct the problem. The DRIVPARM command modifies the parameters of an existing physical drive. It does not create a new logical drive. The settings specified in the DRIVPARM command over-ride the driver definitions for any previous block device.

MORE INFORMATION

The DRIVPARM command does not correct any problems reading floppy disks if the disks are defective. In the case of defective disks, it is necessary to obtain replacement disks from Microsoft Technical Support.

Symptoms of Disk Drive Not Reading Properly

Place a Setup disk (Disk 1) in drive A or drive B, and use the MS-DOS DIR command to display a directory list of that disk. Switch to Disk 2, and use the MS-DOS DIR command to display a directory of Disk 2. If you receive another directory list for Disk 1, your logical drive is reading incorrectly.

DRIVPARM Command and Its Parameters

If your logical drive is reading incorrectly, add the following statement to your system's CONFIG.SYS file:

drivparm=/d:number /f:factor

The /d:number item specifies the physical drive number. Values for the number must be in the range from 0 through 255 (/d:0 = drive A, /d:1 = drive B, /d:2 = drive C, and so on).

The /f:factor item specifies the drive type. The factor numbers for drive types are:

0 = 160K/180K or 320K/360K
1 = 1.2 megabyte (MB)
2 = 720K (3.5-inch disk)
5 = Hard disk
6 = Tape
7 = 1.44 MB (3.5-inch disk)
8 = Read/write optical disk
9 = 2.88 MB (3.5-inch disk)

For more information on the DRIVPARM command, please see pages 455-457 of the "Microsoft MS-DOS Operating System version 5.0 User's Guide and Reference."

For more information on the MS-DOS DRIVPARM command, query on the following words in the Microsoft Knowledge Base:

drivparm and MS-DOS

Additional Workarounds

Method One:

Eject Disk 2 and press ENTER. Then reinsert the disk and press ENTER again.

Method Two:

When you are prompted to change disks, insert disk 2. Then press ALT+TAB to change the focus to File Manager (or to Program Manager and start File Manager). Select drive A and press F5 to force a refresh. Press ALT+TAB to return the focus to Setup and continue.

Additional query words: 4.00 3.00 bad fail vbwin corrupt vb4win vb4all

Keywords : kbsetup
Version : 3.00 4.00
Platform : WINDOWS
Issue type :