[Thursday, February 17, 2005 12:58 AM]

Friedrich:

The msjava.dll dependency wasn't important. I managed to reinstall MS
Virtual machine to test, and it didn't fix it. Later I saw Dependency Walker
was labelling msjava.dll as a "delay-load module".

I found sbuilder.exe executed fine in my notebook, which has exactly the
same windows version of my desktop PC. I compared one by one all the dlls
used by sbuilder between notebook and desktop and all them matched. To
confuss things further, if I booted the desktop PC in safe mode, sbuilder
loaded fine.

After a few hours of uninstalling and reinstalling software, I finally found
the problem: the desktop PC has an AMD64 cpu. Windows XP SP2 has a new
feature called "Data Execution Prevention". If I add SBUILDER.EXE to the
list of exceptions, it loads fine. This feature is hidden in "My PC"
properties - "Advanced features" - first "Configuration" button - last Tab

I think somewhere in your code or in one of the libraries you are using
there is "unsafe" code. Maybe you should test this.

Regards,

--
Carlos Gutiérrez