I have one nal application that simply executes a 32bit program and passes
various parameters on the command line. When launched, it will give you
the typical "xxx.exe has generated errors and will closed by Windows"
message. If I create a regular windows shortcut with the same parameters
or run it right from the cmd prompt it works fine. NAL is doing something
to change it's behavior. This happens with either nal explorer or the
window. This does NOT happen on our windows 2003 server and works fine,
but failes on all of our win2k pro workstations. Any ideas???