Am 05.05.2010 12:54, schrieb Rene Schickbauer: > Just install ActivePerl and all the development tools. Then, just > replace C:\Perl with your backed-up copy. > > I do this all the time on some of my production servers, works like a > charm for me.
Am 05.05.2010 13:37, schrieb Lyle: > The modules must be there if you've copied them over, so PPM isn't > showing them... I'd suspect that PPM keeps a local record somewhere of > the modules it's installed. Maybe in "Documents & > Settings\AppData\ActivPerl"?? Or something like that. Both are right. I previously had a WinXP System and now have Win7. The described issues has to been seen in the context of UAC. Perl is installed as administrator - the previous perl installation was copied in this installation as administrator. Running perl scripts/ppm as administrator everything is OK - running as normal user the described behaviour occurs .... Since I'm pretty new to Win7, I've to search further on for an solution ... http://aspn.activestate.com/ASPN/Mail/Message/activeperl/3815369 seems to address a similar problem: * perl.exe and wperl.exe now contain an application manifest that tells Windows Vista, Windows 2008 and Windows 7 to run the executable with the same privileges as the invoker. This avoids getting redirected to the "Virtual Store" sandbox while trying to access certain parts of the filesystem. Does anybody know, whether it is possible to run AvtiveState Perl 5.8.8 817 under Win7 reasonably at all? Thanks Johannes _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
