As an alternative, I'd recommend checking out Win32::LongPath. It won't be a drop in replacement (i.e. existing code that uses Win32::Unicode will need more modifications than just changing use Win32::Unicode; to use Win32::LongPath;), but it should be able to provide similar functionality. Also, the author does give credit to Win32::Unicode's author.