One alternative to useing a VM is use the Microsoft Application Compatibility Toolkit and create a shim to intercept the invalid calls and redirect them to the correct places (for example your hard coded C:\documents and settings\username can be redirected to %UserProfile%. The program is very large and can even help you scan and figure out what API calls are not working correctly, connect to a database of known problems, and give automatic recommendations on what fixes need to be applied.

One alternative to using a VM is use the Microsoft Application Compatibility Toolkit and create a shim to intercept the invalid calls and redirect them to the correct places (for example your hard coded C:\documents and settings\username can be redirected to %UserProfile%. The program is very large and can even help you scan and figure out what API calls are not working correctly, connect to a database of known problems, and give automatic recommendations on what fixes need to be applied.

One alternative to useing a VM is use the Microsoft Application Compatibility Toolkit and create a shim to intercept the invalid calls and redirect them to the correct places (for example your hard coded C:\documents and settings\username can be redirected to %UserProfile%. The program is very large and can even help you scan and figure out what API calls are not working correctly, connect to a database of known problems, and give automatic recommendations on what fixes need to be applied.

One alternative to useing a VM is use the Microsoft Application Compatibility Toolkit and create a shim to intercept the invalid calls and redirect them to the correct places (for example your hard coded C:\documents and settings\username can be redirected to %UserProfile%. The program is very large and can even help you scan and figure out what API calls are not working correctly, connect to a database of known problems, and give automatic recommendations on what fixes need to be applied.