I did some research regarding NTVDM.EXE and found out the following from the Microsoft support web site :
When a 16-bit application passes command-line parameters to another application on a Windows Vista-based computer, the second application does not receive the command-line parameters
SYMPTOMS
loadTOCNode(1, 'symptoms');
Consider the following scenario. A 16-bit application is running on a Windows Vista-based computer. This 16-bit application passes command-line parameters to another application. For example, the 16-bit application calls the ShellExecute function to start another application. Meanwhile, the 16-bit application passes command-line parameters to the newly started application.
In this scenario, the second application starts. However, the second application does not receive the command-line parameters. Therefore, the second application may not work as expected.
I do not understand why NTVDM.EXE is summoned when I decide to make my application file, even though I began designing the program on the Clarion 4 platform, as far as I know all applications generated with Clarion 6 are 32 bit applications.
According to Microsoft the hot fix for this problem is included with Service Pack I, which as you can see from my computer description above came with my operating system installation disk and is properly installed on my computer.
As you can see, I am experiencing some fairly frustrating issues between Clarion 6.3 and Windows Vista Ultimate Edition. I would very much appreciate any help or advice you can provide regarding this problem.