Article ID: 318945 - View products that this article applies to.
This article was previously published under Q318945
When you install Visual Studio .NET (VS .NET) or its components, including the Microsoft Developer Network (MSDN) Library, problems may occur during installation or when you use VS .NET or the MSDN Library.
This problem can also occur if third-party software is not turned off by using Msconfig.exe during the installation, or if other applications are running during the installation.
Some of the common errors are the following:
This behavior occurs because one or more files are not read properly from the DVD-ROM during the file copy phase of the setup process; some files may become corrupted.
During some occurrences, you may receive an error message. During other occurences, you do not receive an error message and the file is copied without errors; however, a piece of the file is corrupted after the file is copied to your computer.
The following are several methods to work around this problem.
Update the driverContact the DVD-ROM manufacturer to verify whether an updated device driver is available. Contact the hardware manufacturer before you apply any updates because an incorrect driver update could damage the hardware. For more information about installing device drivers, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/275499/ )Troubleshooting device driver issues by using the Driver Information Database
Disable DMA accessIn some cases, you can resolve the problem by disabling direct memory access (DMA) for both the DVD-ROM drive and the local hard disk. For more information about how to turn off and turn on DMA, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/258757/ )How to enable Direct Memory Access (DMA)
Install from a CD-ROMInstall the programs from a CD-ROM instead of from a DVD-ROM. For more information about how to receive a CD-ROM to replace your DVD-ROM, click the following article number to view the article in the Microsoft Knowledge Base:
284230However, occasionally CD-ROMs also fail because of issues with the physical hardware and drivers.
(http://support.microsoft.com/kb/284230/ )INFO: Replacing damaged or defective Visual Studio product disks
Install from a network shareTo install from a network share, create a local folder share, and then use the xcopy command to install the programs without the interaction of the CD-ROM or DVD-ROM drivers. To do this, type the following at a command prompt:
/V = verify
xcopy <source> <destination> /V /H /Y /E
/H = hidden files
/E = sub folder including empty folders
/Y = suppresses prompting to confirm that you want to overwrite an existing destination file
To create the local installation points, follow the steps provided in the following Microsoft Knowledge Base articles:
Copy help files to your hard disk to replace corrupted FilesCopy from the DVD-ROM to your hard disk only the help files that were corrupted when you installed the program.
Note This method will fix the immediate problem; however, it is possible that other files were corrupted at the same time as the help files. You may not know that other files were corrupted until unpredictable problems occur later.
When your receive the following dialog box message, Microsoft Help 2.0 is merging the indexes that exist in .HxI files:
If these .HxI files are corrupted, then the merge cannot occur. The merge must occur for your computer to display the index for VS .NET online help or the MSDN Library.
"Help Update in Progress"
To determine which files are damaged, compare the files on your computer with the files on the DVD-ROM. To do this, follow these steps:
Copy the DVD-ROM to your hard diskCopy all of the files on the DVD-ROM to your hard disk, verify that the files were copied correctly, and then re-install from the hard disk copy.
This problem has been identified as typically a problem in the driver software or firmware for some DVD-ROMs. This bug was corrected in Visual Studio .NET (2003) and the .NET Framework 1.1.
For additional information about the following topics, click the article number to view the article in the Microsoft Knowledge Base:
Article ID: 318945 - Last Review: March 16, 2007 - Revision: 4.9
Contact us for more help