Could you verify that Win32::GUI is causing this by testing
without GUI code running. Create an application that uses threads and
Win32::FileOp without Win32::GUI loaded and see if the problem still occurs. If
so, it's out of our hands and is a fault in Win32::FileOp. A lot of modules are
not threads-compatible, and it's probable that Win32::FileOp is one of
If it only happens with Win32::GUI loaded, please let us know
and we'll undoubtable jump at the chance to look into it, such a powerhouse
of activity that we are.
----- Original Message -----
Sent: Saturday, January 24, 2004 10:24
Win32::FileOp Erro with Win32::GUI
I noticed that when I use the
in a GUI application (may be also
not gui) in a Threads,
When the threads starts, the
script shows error
that says :
The instruction at "0x28053f9a"
referenced memory at "0x000010c0". The memory ould not be
Click on OK to terminate the
Click on CANCEL to debug the
and sometimes it is The memory
ould not be "Written" instead of "read".
I actually found that if I use the
module "Win32::API" it will generate
this error and of course
Win32::FileOp use internally this module.
The threads works fine if I remove
the "use Win32::FileOp;" line but
I need to use it for the File Open
and Save Dialogs.
Any solutions or
Thank you in advance for