If you didn't post as an anonymous monk, I would hav /msg'ed this to you rather than posting a reply: your node is hardly readable at all. Put code tags arounf your code, at least.

Did you notice that after pressing the preview button you were told " If something looked unlike you expected it to you might need to check out Writeup Formatting Tips". So I must suppose it did look like you expected, shouldn't I?

Update: now that your post has been fixed, I can answer to you...

i.e only test1.dll files are extracting other names with .dll are not coming..
if i use $name = "/*.dll|*.exe/" to extract my required .exes and .dlls.. the module

You're confusing shell patterns with regexen. Check perldoc perlre. Or else, you may try the find2perl command for a starter.

#!/usr/bin/perl

use File::Find;
[download]

As a general rule, you're missing the two most important lines in your program: maybe it won't seem so at first, but make your life easier and help people (not to say perl!) to help you by writing

use strict;
use warnings;
[download]

as well.

 sub filefind
 {
 # my $aName = @_;
 # my $file = $File::Find::aName;
  my @dirs = ($dir);
  find(\&mysub, @dirs);
  return @files;
 }
[download]

really, I don't see the need for this wrapper sub. As I don't see the need for many intermediate variables you're putting in many places - since they do not contribute to readability and are at most confusing.

   if ($_ =~ $name)
   {
   
    push @files, $_;
 
   }
[download]

Two things:

1. the topicalizer is just there to be the implicit topic: use it as such or else use explicit variable names,
2. here you have $_ =~ $name, but $name is a string: what is happening is that perl converts it to a regex. This is not generally what you want and may have an unexpected outcome for you if $name contains charachters that have a regex special meaning (which it does happen to have here, but for a "fortunate" coincidence it doesn't happen to have any "surprising" effect in this case).