Frank Foss wrote:
> What I would like to do, is to write a quick Perl script that will traverse
> a directory, look "inside" each .DLL or what ever type of file, read the metadata
> attributes, and write to a file.
You will do better, as a software writer, to learn about
writing software. It is clear you do not hold enough
knowledge to tackle this task.
Windows dll files appear as three basic types, with a number
of variations on each. Should you elect to research and read,
elect to learn, you will discover windows dll files can be
sixteen bit, thirty-two bit Win9.x and thirty-two bit NT types.
Sixteen bit dll files can be used with FAT32 Win systems.
NT types, depending on which NT version, can run under
FAT32 or NTFS file systems, but usually not both.
There are thousands of gray market (third party) dll files
which may or may not comply with expected standards, and often
run under both sixteen bit and thirty-two bit Win systems.
Many gray market dll files are installed with default Win
installations. Some gray market dll files are written for
sixteen bit and thirty-two bit, both Win9x and Win NT.
Differences here are in how these various dll files are accessed.
Older sixteen bit, Win9.x 32 bit and gray market sixteen/thirty-two
bit dll files, usually require a compiled C language executable
to access information. NT NTFS dll files can be accessed, to a degree,
with WIN32 API perl modules designed solely for NT.
Other choices are compiled binaries and Visual Basic scripts, both
dependent upon Windows version. There are many commercial compiled
binaries written specifically for working with Win dll files. For
a low level beginner, such as yourself, your money will be wisely
invested in the skills of a professional.
Your Win2k system will include all dll types being NT 5 enhanced
for limited compatibility with older 16/32 bit DOS software. You
may or may not be able to access those dll files depending on how
your Win2k system is installed.
My suggestion is you hit those "reference books" and learn about
what you clearly don't know. You will not do well writing software
based upon this lack of knowledge you display. Personally, I don't
think you can write any Windows software with your not knowing even
the simple basics of Win dll files.
Research, read and learn, or pay a professional to do your work.
I am curious why you want to pull information for _all_ dll files
when only a limited number are needed for any given software. You
are aware of this, yes? I tend to believe you are unaware many
dll files depend on other dll files which depend on....