Thank you for the reply. I think everything is 64 bit. I changed the system32 path to Sysnative and the results remained the same.

A security issue seems likely to me. There's all sorts of security and tracking software installed, but the IT guy says that's not the issue. I looked at the event log and AppLocker doesn't have any events associated with it. He said that the tracking software is all shut off on a clean boot. He also removed it from the workgroup to check the group policy. Here's a list of configurations he tried:

Both 32-bit and 64-bit versions
Both patches from the Demeter website
Normal mode
Last known good configuration
Selective startup
Disabled all non-critical local services
Terminated all non-critical system and user processes
Uninstalled Java
Uninstalled .NET framework
Reinstalled Java
Reinstalled .NET framework
Adjusted memory settings for best performance
Verified use has full control of all of their profile data (including 
+appdata) and installation directory
Attempted as a normal user and administrative user
Windows 95 compatibility mode
Windows 98 compatibility mode
Windows NT 4.0 compatibility mode
Windows 2000 compatibility mode
Windows XP (SP2) compatibility mode
Windows XP (SP3) compatibility mode
Windows Server 2003 (SP1) compatibility mode
Windows Server 2008 (SP1) compatibility mode
Windows Vista compatibility mode
Windows Vista (SP1) compatibility mode
Windows Vista (SP2) compatibility mode
Windows 7
Disabled visual themes
Disabled desktop composition
Disable display scaling on high DPI settings
Install to default location
Install to a specific location C:\demeter (not default)
Workstation was removed from domain and joined to workgroup
Various reboots throughout

[download]

It only runs is safe mode and safe mode with networking. He also tried disabling the antivirus, but that didn't help either. I don't know what the difference is between the safemode and clean boot. that is causing the problem.

As I understand it, the MinGW issue was resolved a while ago with the release of version 9.14 or so.

Does any of this set off any new alarms? Unfortunately, I don't have much control of the computer, so I can't view the security settings or any of that.

Thanks

In reply to Re^2: Invalid Access to Memory location using DynaLoader - path? by MattN
in thread Invalid Access to Memory location using DynaLoader by MattN

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.