Installing program error #76 Path not found

[4iamernie]

I wrote a program using vb6 and using the package and deployment wizard I wound up with two floppies of cab files. I used the two floppies to install the program I wrote to the computer I wrote the program on. While installing the program I get
"ERROR: C:\WINDOWS\SYSTEM\MSVCRT.DLL
ERROR: An access violation occured while copying the file.
ERROR: If you ignore a copy error, the file will not be copied. The application may not function properly as a result."
I was forced to use the "IGNORE" choise offered to continue with the installation.
The installation finished and reported that the program installed successfully.
The program ran ok on this computer but as a check I attempted to install it on a second computer that doesn't have vb6 installed.
The same ERROR event occurred and the installation also reported a successfull installation.
However, when I attempted to run the program on the second computer, a msgbox popped up stating ERROR #76, Path not found.
Looking in program explorer of the second computor the program and the same MSVCRT.DLL version are installed. An attempt to run the program's EXE brought up the same ERROR #76, Path not found.
Allthough I may be wrong, I feel that the problem is caused by my inability to access the MSVCRT.Dll file while installing the program.
I have tried to overcome this by various methods, all of which have failed.
The methods are:
Using the Ctrl,Alt, & Delete keys I shut down everything but explorer and then installing, no go.
Removed all the start-up program in the registry one by one and then installing, no go.
Tried the various pathes allowed in the set-up program while installing, no go.
Tried to rename the MSVCRT.Dll to see what program would crash but I wasn't allowed access, no go.
Copied MSVCRT.DLL to a floppy and tried to delete it from the hard disk but was denied access again, no go.
Cleaned up both computers hard drives, no go.
I'm at my wits end! Help!
Any help would be appreciated.
Thanks!
4iamernie
aka ErnstKnud@aol.com

 

[edderic]

The version of files MSVCRT40.DLL and OLEPRO32.DLL in Windows 2000, Windows NT 4.0, and Visual C++ 4.2 are wrapper DLLs that call functions in a new file, MSVCRT.DLL. The file MSVCRT.DLL is included in Windows 2000, Windows 98, and Windows Me, but not in Windows 95 or Visual Basic 4.0.



RESOLUTION
Create the \VB\SETUPKIT\KITFIL32\SYS32 directory and copy the following files from the \VB\SYSTEM directory of the Visual Basic distribution disks:


FILE VERSION NUMBER
--------------------------------------------
MSVCRT40.DLL 4.00.5209 or 4.00.5270
OLEPRO32.DLL 4.00.5208 or 4.00.5277



The versions of these files in Visual C++ 4.2, Windows 2000, and Windows NT 4.0 are forwarder DLL files that call functions in MSVCRT.DLL. If you include the versions of MSVCRT40.DLL and OLEPRO32.DLL from Visual C++ 4.2, Windows 2000, or Windows NT 4.0, then this error will occur because these files are looking for MSVCRT.DLL.

The versions of MSVCRT40.DLL and OLEPRO32.DLL included with Visual Basic 4.00 do not require MSVCRT.DLL. Your setup program should install these versions to prevent this error.

NOTE: If your setup program still fails on a target system, delete or rename the files, MSVCRT40.DLL and OLEPRO32.DLL on the target system. The target system has the newer versions of these files. The setup program created using the Setup kit is designed so that older files do not overwrite existing newer files on the target system.

After deleting or renaming these files, your setup program should function properly Eric De Decker
vbg.be@vbgroup.nl

License And Copy Protection AxtiveX.

Download Demo version on my Site:

http://www.createsoftware2000.com

 

[edderic]

When running a setup that was created by the Visual Basic Setup Wizard or Package and Deployment Wizard (PDW), the following error message is generated:

<file path and name>

An access violation occurred while copying the file.
where <file path and name> is the name of the file, including the complete path, that Setup is attempting to copy.



CAUSE
Another open program is using the specified file. In some cases, the file may be in use by the operating system.



RESOLUTION
Follow these steps to resolve the problem:

Verify that the file specified in the error message is redistributable. If the file is not listed as being redistributable, rebuild the distribution removing that file from the setup files.

In Visual Basic 5.0, check the files License.txt and Redist.txt, both of which are located in the &quot;Program files\DevStudio\VB&quot; folder.

In Visual Basic 6.0, check the files Eula.txt in the &quot;Program Files\Microsoft Visual Studio\Common\Setup\1033&quot; folder and Redist.txt in the &quot;Program Files\Microsoft Visual Studio&quot; folder.


If the file is redistributable, make certain that the user closes all open programs before installing the application. Booting Win9x in Safe Mode prevents most applications from loading automatically at startup, as does holding down the SHIFT key for the duration of the boot. Neither method disables anti-virus software, screen savers, and so forth, so they must be shut down manually if they load the problem DLL.

To determine which program is using the file, use a utility such as DLLView for Windows 9x or HandleEx for Windows NT/Windows 2000. Both utilities are available as free downloads from a third-party Web site at the following address:

http://www.sysinternals.com

If all open programs are closed, and the user still receives the error message, the file may be in use by the operating system. In this case, the following alternatives are available to work around the error message:


Users can click Ignore in response to the error message. When they click Ignore, they will receive the same message again with the following additional information:
If you ignore a copy error, the file will not be copied. The application may not function properly as a result. Do you want to ignore the error?
If they click Yes, Setup continues installing the remaining files, and the application will often run properly without replacing the file.


If a version of the file that is compatible with the application is already on the user's target system, you can remove the file from the file you distribute to avoid the message altogether. See the MORE INFORMATION section later in this article for details concerning the files that most commonly cause this error message.


You can customize the Setup Toolkit project (Setup1.vbp). Microsoft Technical Support does not provide support for modifying the Setup Toolkit project, but the source code is available for customization. For more information, search on the phrase &quot;setup toolkit project&quot; in &quot;Books Online&quot; for Visual Basic 5.0 or the &quot;MSDN Library Visual Studio 6.0.&quot;
For additional information about programmatically replacing files that are in use, please refer to the following article in the Microsoft Knowledge Base:
Q140570 HOWTO: Moving Files That Are Currently in Use



You may want to consider using a third-party Setup program.





MORE INFORMATION
This error occurs most frequently when developers distribute the following files:


Comctl32.dll (Not redistributable)
Comdlg32.dll (Not redistributable)
Mfc42.dll
Msvcrt.dll
Msvcrt20.dll
Msvcrt40.dll

This error has also been reported less frequently with the following files:

Mfc40.dll
Msvcirt.dll

NOTE: Do not redistribute Comctl32.dll or Comdlg32.dll. If you must update Comctl32.dll, download 401comupd.exe from the following Microsoft Web site:

http://www.microsoft.com/msdownload/ieplatform/ie/comctrl.asp

The following tables contain information about the files listed above, including which operating systems install them and which operating systems require them.


File Operating File File File
Name System Installed? In Use? Version
--------------------------------------------------------------

Mfc40.dll Windows 95 No No
Windows 95b Yes No 4.1.6139
Windows 98 Yes No 4.1.6139
NT 4.0 Yes No 4.1.6139

Mfc42.dll Windows 95 No No
Windows 95b No No
Windows 98 Yes No 4.21.7325
NT 4.0 Yes No 4.2.6068

Msvcirt.dll Windows 95 No No
Windows 95b No No
Windows 98 Yes No 4.20.6164
NT 4.0 Yes No 4.20.6201

Msvcrt.dll Windows 95 No No
Windows 95b No No
Windows 98 Yes Yes 5.00.7128
NT 4.0 Yes Yes 4.20.6201

Msvcrt20.dll Windows 95 Yes No 2.11.000
Windows 95b Yes No 2.11.000
Windows 98 Yes No 2.11.000
NT 4.0 Yes No 2.11.000

Msvcrt40.dll Windows 95 No No
Windows 95b Yes No 4.10.6038
Windows 98 Yes No 4.10.6038
NT 4.0 Yes No 4.20

Eric De Decker
vbg.be@vbgroup.nl

License And Copy Protection AxtiveX.

Download Demo version on my Site:

http://www.createsoftware2000.com

 

[Craftor]

I had the exact same problem with my program and one of the guys on this site suggested copying the mscvrt.dll file to the directory my program was running from. This seems to have resolved my problem - don't know if it will help you??

Just a suggestion...