Dynamic Renamer

I was trying to use the -+1 transformation on file of the form filename_001.ext but it removes the leading zeros so ends up changing it to filename_2.ext instead of filename_002.ext. Would be great if it kept leading zeros.

To workaround the issue, I tried to chain the -### transformation but couldn't get the required result.

Also, the script doesn't remove any leading spaces from the New name field, so it doesn't recognise " -+1".

Ah, good ones. Thanks.

Here's another pre-release which fixes the two problems mentioned.
_Dynamic Renamer 1.12pre2.zip (6.31 KB)

Confirmed 1.12pre2 solves both issues.

Thanks for the quick fixes MrC.

@MrC

tip..

"... The script requires ActivePerl 5.16 (not 5.18)"

The link in your post gets you to the download site showing 5.18 and 5.20 only.
v5.16 is available in Business Edition and Enterprise Edition but I am not sure they are for free.

=

@opw62,

I've known about this for a while, and was awaiting for someone to mention it, or be affected by it. Unfortunately, ActivePerl pulled the old release, and has bumped their versions. They do charge for the archived versions (a pure money grab), so I'll have to check that the required modules are built for the newer versions of Perl (when I wrote Dynamic Renamer, they were not yet ready). I'll take a look this weekend.

Edit: The modules are available. I just have to verify the code is 5.18 or 5.20 compatible.

@MrC


I have a couple of older versions. Let me know if you need.

Regards, AB

@MrC -

So, the latest version of Dynamic Renamer is indeed compatible with v5.18.4.1803 / v5.20.1.2000 ?

If that is the case, then the below can be ignored...

==
As for v5.16.xxx

I am not sure whether the below files are 'reworked' (meaning: added trojans, malware, pups whatever)
but.. for x64 one might try it from CNet - ActiveState ActivePerl Windows (64-bit)
download.cnet.com/ActiveState-Ac ... =pdl-redir
File: ActivePerl-5.16.3.1603-MSWin32-x64-296746.msi - size: 27,6 MB (28.955.364 bytes)
Checksums:
CRC32: 2CE6DDE3
MD5 : 23103D237A9EE0E1836AF266603B9D01
SHA-1: 7A2BFE37BF17B227FDDEBB0A1D070A020C6E6704
SHA-256 : 9D8AE2B5FCE8B2D750B37CD238D5E6AF9DCE2C69E8571952A4ACB2D857B824BF

(cnet does not have the 32b version)

or
github.com/EQEmu/eqemu.github.c ... /downloads
ActivePerl-5.16.3.1604-MSWin32-x64-298023.msi - size: 27,6 MB (29.025.564 bytes)
CRC32 : 99ADAC59
MD5 : 376928383125FCA012FC359C38317028
SHA-1 : D3E16317B9DE6F18017C3BF79284E84A0F280EE0
SHA-256 : DD592518BC0A435E239CA447FB0B53061E32F1CAEB3602610ECC6449151DD1EA

ActivePerl-5.16.3.1604-MSWin32-x86-298023.msi - size: 25,7 MB (27.028.100 bytes)
CRC32 : 58D45C00
MD5 : 287C784C1791637EAE254E46EFBA6BB1
SHA-1: A8DCB719B0CF7CF08B0A3562BD0E81D05AB24F03
SHA-256: 3768D99A130FBF0070C70F0D31AD50AEFFD64AD9ED00C247FC9FFC2C0A6A9706

Now, I don't know which versions you have available at yours. Maybe you can verify the checksums?

Alternatively, maybe.. there is a download-location on the forum somewhere where you can store 'your'
ActivePerl? But likely that requires okay from the administrator. Just a suggestion.

[quote="opw62"]@MrC -

So, the latest version of Dynamic Renamer is indeed compatible with v5.18.4.1803 / v5.20.1.2000 ?

[/quote]

Well, so far, it isn't looking too good.

The 64-bit version of ActivePerl 5.20 causes DirectoryOpus 11.12.04 to crash upon selecting a perlscript rename script.

The 32-bit version of ActivePerl 5.20 causes DirectoryOpus to emit to the log the diagnostic "Script Engine 'perlscript' could not be opened".

Given the unfriendliness here towards anything not JScript or VBScript, I'm not hopeful this will get investigated or resolved.

Version 5.18 does not have certain required modules available, so that's a no-go.

Reinstalling 5.16 works fine, so I'd say the only option currently is that version.

I'm not going to post the binaries as this might violate some ActiveState terms. 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'll update the links in post #1 to refer to those links - thanks for finding them.

It's crashing in PerlSE.dll in the call to IActiveScriptParse::InitNew. You'll have to report this to ActiveState if you want it "investigated or resolved" :slight_smile:

@Jon - Thanks, I'll report the issue.

@opw62 - I've updated the links in post #1.

From the ActivePerl developers:

... it looks like we already have a fix. It will be in the next release (5.20.2.2001), which seems likely to be released before the end of the month.

Note: ActiveState has updated ActivePerl 5.20 to version 5.20.2.2001. This restores the ability for ActivePerl to work with Windows Scripting hosts. I've updated post #1 to reflect this version as the new recommend version.

I'll be updating Dynamic Renamer shortly with a few bug fixes and features.

I am unable to install date-manip. It is not found by PPM or PPM GUI.
Going to ActivePerl web site - indicates that date-manip 'fails build' on both Win32 and Win64 for Perl 5.22. Using the url ActivePerl Downloads - Perl Binaries for Windows, Linux and Mac defaults to the 5.22 build.
I plan to uninstall all of 5.22 - download 5.20 and then see if this solves the date-manip issue. As it stands now - Rename Import fails without date-manip on 5.22

Use 5.20 for now. The Date::Manip package is used for the various date guessing transformations. Those options aren't essential if you don't want them. I could make the package optional, and make those date guessing transformations available if the Date::Manip module is installed.

There's no benefit to using 5.22 over 5.20.

I can't get this too work. I have ActivePerl 5.22 loaded. In addition, I completed the ActivePerl module update. I have Dynamic Renamer 1.12 loaded in the Renamer Dialog:



However, nothing works. I do not get any scripting errors.

Please advise.

Hi Chuck,

I haven't tested (nor own) DO 12. I see that you have your question answered in another thread. If you are still interested in using Dynamic Renamer, I'll go ahead to do the work to see that it works with DO 12. The folks here are a little hostile towards the Perl requirement, so I haven't spent any time working on it in ages.

MrC, I'm still interested!

Chuck,

The problem seems to be with more recent ActivePerl versions, namely 5.22 and 5.24. This isn't the first time ActiveState has botched Windows Scripting hosts integration. A few threads above I posted about this for a previous breakage. Sigh.

Use the 5.20 version. Remove your newer version(s) of ActivePerl first.


So far, so good. Thanks!

Any plans to migrate to javascript (comes default with OS) or another language?