barrytraver
Programmer
Help!
I used the Package & Deployment Wizard to set up an installation package (for a VB program created with VB 6, professional edition, on a computer running Windows ME), but when I tried to use it to install my VB program on another computer (a prograrm running Windows 95), I got the following error message:
"C:\WINDOWS\SYSTEM\RICHED32.DLL
An access violation occurred while copying this file."
Since there were only two programs in memory (Explorer and Systray) when I started the install program, I can't see why there would be any reason for an "access violation" to occur "while copying this file."
To the warning message, I responded with an "Ignore" rather than "Retry" or "Abort," and the installation seemd to be successful, i.e., the program seems to work fine, but why the error message? (If I give my program to others, I certainly don't want such an error message showing up when they install the program!)
The following additional information may or may not be relevant. When I ran the installation package also on the computer on which I created the program, there too I got a warning about RICHED32.DLL, but this one claimed that there was already a newer version of the file installed on the computer! How can that be, since that was the very computer on which I ran the Package & Deployment Wizard to create the installation package?
Any advice on this situation would be greatly appreciated.
Warm regards,
Barry Traver
I used the Package & Deployment Wizard to set up an installation package (for a VB program created with VB 6, professional edition, on a computer running Windows ME), but when I tried to use it to install my VB program on another computer (a prograrm running Windows 95), I got the following error message:
"C:\WINDOWS\SYSTEM\RICHED32.DLL
An access violation occurred while copying this file."
Since there were only two programs in memory (Explorer and Systray) when I started the install program, I can't see why there would be any reason for an "access violation" to occur "while copying this file."
To the warning message, I responded with an "Ignore" rather than "Retry" or "Abort," and the installation seemd to be successful, i.e., the program seems to work fine, but why the error message? (If I give my program to others, I certainly don't want such an error message showing up when they install the program!)
The following additional information may or may not be relevant. When I ran the installation package also on the computer on which I created the program, there too I got a warning about RICHED32.DLL, but this one claimed that there was already a newer version of the file installed on the computer! How can that be, since that was the very computer on which I ran the Package & Deployment Wizard to create the installation package?
Any advice on this situation would be greatly appreciated.
Warm regards,
Barry Traver