This works fine for me:

use strict;
use warnings 'all';

my $found = 0;

for my $in_path (@INC){
    next if ! -e $in_path."\\Win32API\\File.pm";
    print "found module in $in_path ...\n";
    $found = 1; 
    last;
}

if ($found == 1){
    use Win32API::File;
    my @drv = map{s/\\$//;lc}  
               Win32API::File::getLogicalDrives();
    print @drv;
}

[download]

Giving these results:
found module in C:/Perl/site/lib ...
a:c:d:e:p:u:

[download]

SMiTZ

Update: All though this works OK, its pointless putting use into a conditional block as it gets loaded at compile time. Testing for its existance after perl has attempted to load it seems a bit superfluous. Ooops, thanks jmcnamara.

In reply to Re: strange things happen by smitz
in thread problem with @INC when using activestate perl by NaSe77

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.