Here's my problem:
I've got a production application written in what I believe is version 4.5 or 5.0 of VAST.
It is run by the users off of a corporate network drive that is read only, and the application is started using a windows command file that changes directory to the network location, and invokes nodialog.exe with the -i parameter.
Now under Windows 7, we are seeing that the app terminates unexpectedly on rare occasions.
The first thing that I would look for is the VMTRAP.LOG file to see what was going on, but since that directory is read only, it would not be generated there.
Does anyone know where the VMTRAP.LOG file would be created in this instance (if at all)?
And for the followup, is there a way to set where the VMTRAP.LOG file would be created via a command line switch? Does it work off of the -l switch?