Greetings fellow monks!

Today was a most joyous occasion for me, I was actually asked to implement some sort of digital logging mechanism to track instrument usage! (That may not sound like much, but technology is terribly underutilized at this company.) I'm just a scientist with a programming hobby so this means that all the time I've spent meditating here at the monastery has helped me get to a place where I'm actually asked to tackle these sorts of problems so I humbly thank all of you for your guidance over these years. It also means that the seed of change has been planted and they are starting to realize that a computer can be more than just a giant typewriter!

Unfortunately, this wont be easy. I've tried to automate other parts of the software in question before with little success (Collecting data from a program that doesn't make it easy). What would be ideal would be to record the start time and end time of the instrument's operation and maybe a few other details (who's running it, what study, etc.). My initial thought was to write a little bat script to call a little perl program to log the time, user, study etc. then call the instrument's software. (Maybe even bracket that with another script to record the time the software is closed, assuming it's closed when it's done being used.)

The downside of that is I'd have to install and maintain perl on quite a few machines (not terrible, I agree, but laziness is a virtue). I do, however, have access to all the data directories over the network. So, what I'm wondering is if there is another, less obtrusive way to log usage, say perhaps by monitoring the data directory for new files and logging the creation and last modification time? Has anyone run into similar problems on Win32? Any thoughts on alternate ways to tackle this problem?

Thanks in advance!

In reply to Automating program use logging on Win32 by c4onastick

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.