The one other thing that PPM does besides copy the files is to note the changes in an XML file so that it "knows" which modules have been installed. For this reason PPM will not be aware of any modules that you have installed manually, adn it will not be aware of any changes that you make, such as substituting .dll files. In this case it shouldn't make a difference, but in certain cases that could cause it to overwrite the .dll file if you did a verify --upgrade.
As for the perl56.dll, what version and build of Perl did you have installed would be the first thing to check with this kind of an error. -----Original Message----- From: chris To: [EMAIL PROTECTED] Sent: 7/27/02 5:54 PM Subject: Re: What does PPM do to install a package? I did some more experimenting and discovered that the culprit was perl56.dll. For some reason, the perl56.dll is not compatible with TaskScheduler.dll in this distribution. If I simply replace this one file from ActiveState, it works but I cannot live with this fix. Anyways, PPM seems to have just copied the files to the target directories. My manual install was OK except for the perl56.dll incompatibility issue. Sorry for any confusion I may have caused. On Sat, 27 Jul 2002 20:07:16 -0400, [EMAIL PROTECTED] (Chris) wrote: >I have two perl distribution on the same computer. > >The ActiveState distribution has PPM. I used this to install >Win32::TaskScheduler package and all is well. > >For my other perl distribution, I thought I would just copy the files >in the two packing lists to the appropriate directories but perl is >unable to find the entry point in the dll. How do I install >Win32::TaskScheduler manually? -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
