Prentice, check your AUTOEXEC.NT and CONFIG.NT files, which are in your System32 folder usually. These are called instead of the DOS AUTOEXEC.BAT and CONFIG.SYS files. You can see exactly what files are called by pulling up properties for the program and on the PROGRAM tab click on the Windows NT button.

HTH
Barbara

>All,
>
>In foxpro for windows under NT workstation 4.0 what is the dos environment when:
>1) running a dos program
>2) running command
>
>It seems to me that running command will be what ever is set up in the foxrun.pif; I would also think that running a dos program would do the same. I am wondering if there is a comspec specified some where.
>
>The problem I have run into is I have a foxpro for windows app that calls a dos program to read orders from a scanner. It was working just fine. I don't know what has happened, but now I get errors saying that the program is unable to communicate with the scanner. If I shell out to dos from the command box and execute the program that talks to the scanner it works just fine (on the 2nd and subsequent tries). I have tried setting my foxrun.pif to call command.com which was the original and setting to call cmd.exe. I get the same result.
>
>Any help will be appreciated.
>
>Prentiss Berry