We have a legacy Net Express 3.1 application that just got moved to a new Windows machine along with the runtime files and when invoked we see the EXE running but the screenset is never displayed. We have tried using compatibility mode and a variety of other things but cannot narrow down why it works on one machine and not on another. We do notice on the machines where the screenset is not displayed that the EXE it taking 5-10 percent CPU which it normally does not on a machine that displays it correctly so I am assuming it's cascading an error but we cannot see it. The OS versions involved in the test are Windows 7, server 2008 and 2012. Is there any way to debug the program or screenset on the offending machine without recompiling? Thanks for any information.
↧