I'll update the links in post #1 to refer to those links - thanks for finding them. The 64-bit version of 5.16.3 you reference at CNet is identical to the one I have, which came from ActiveState's site. I'm not going to post the binaries as this might violate some ActiveState terms. Reinstalling 5.16 works fine, so I'd say the only option currently is that version. Version 5.18 does not have certain required modules available, so that's a no-go. Given the unfriendliness here towards anything not JScript or VBScript, I'm not hopeful this will get investigated or resolved. The 32-bit version of ActivePerl 5.20 causes DirectoryOpus to emit to the log the diagnostic "Script Engine 'perlscript' could not be opened". The 64-bit version of ActivePerl 5.20 causes DirectoryOpus 11.12.04 to crash upon selecting a perlscript rename script. there is a download-location on the forum somewhere where you can store 'your'ĪctivePerl? But likely that requires okay from the administrator. Maybe you can verify the checksums? Alternatively, maybe. Now, I don't know which versions you have available at yours. for 圆4 one might try it from CNet - ActiveState ActivePerl Windows (64-bit)ĭ/ActiveState-Ac. I am not sure whether the below files are 'reworked' (meaning: added trojans, malware, pups whatever)īut. If that is the case, then the below can be ignored. Doesn't offer many advanced features for CGI scripting.So, the latest version of Dynamic Renamer is indeed compatible with v5. ![]() Allows you to perform advanced bug testing.In the newly-created directory, in a DOS or Powershell window, type: perl Makefile.PL dmake dmake install. Run the following command to display the Perl version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |