Are you sure you've given us all relevant code and messages?

When I execute what you gave us, under 32 bit Win7, AS 5.16.3, with the original install (v = .11) of Win32::NetAdmin, I see:

Reference found where even-sized list expected at D:\_wo_sch\1080998.pl line 4.

That's as expected; if you delete the " = {}" so line 4 becomes "my %UserList;", you may have better success (emphasis on the "may", as I'm not playing with 64 bit 'doze.


Questions containing the words "doesn't work" (or their moral equivalent) will usually get a downvote from me unless accompanied by:
  1. code
  2. verbatim error and/or warning messages
  3. a coherent explanation of what "doesn't work actually means.

In reply to Re: SEGV signal termination in Win32::NetAdmin ver 0.12 on Win64 w ActiveStatePerl5.16.3 X64 by ww
in thread SEGV signal termination in Win32::NetAdmin ver 0.12 on Win64 w ActiveStatePerl5.16.3 X64 by suzun30

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.