>>Hi Ed,
>> So I guess it's back to my initial question: "How do I get the Win2000 VDM to close when a simple DOS command (like ! /n pkzip25) has completed" from fpw26. Thanks.
>>
>
>Several ways - the easiest is to go into Windows Explorer, right-click on the executable program, select Properties, the Program Tab, and either on the Program Tab, or on the Dialog shown from the Advanced button, check 'Close on Exit'.


Therein lies my quandry. There is no 'Program Tab', no Advanced button, and no 'Close on Exit', anywhere.


Clearly the batch file will work, by simply including exit at the end.


However, I've think I found a way around it. This behavior (not closing when it's done) only seems to occur when running from inside FPW26. It behaves correctly (so far) when I run the .exe from outside of FoxPro. There was an issue that was forcing me to run from foxpro, but has since been resolved (opaque fonts).


If anyone can figure this thing out, I would be interested in the outcome, but it is no longer a critical problem for my client.

Thanks for all your help.

Daniel



>
>Alternatively, you could build a batch file and use the START verb in the batch file, have it wait, and then EXIT.
>
>>>>> The foxrun.pif is located in the directory (on the server) where the application is. The config.fpw on the server however, points all the work files to the users machine. I think that's the problem. I also noticed that when I run the compiled app outside of foxpro, I don't have the problem. It's only when I run it from inside that it doesn't close down correctly.
>>>>>
>>>
>>>This is a =very= bad idea. PIF file formats vary between different operating systems, and feature support even for DOS applications via a PIF file is not uniform. If you're launching a DOS-based app, especially a .BAT file, this is almost certain to cause problems in mixed OS environments; the console's CLI (Command Line Interpreter) isn't even named the same between different OS versions - Win9x uses COMMAND.COM, while WinNT/2K use CMD.EXE - and the memory management settings and VDM options are not identical between the two environments.
>>>
>>>PIF files should be a purely local item; it's proper technique to store all PIF files in a Windows SpecialFolder, which has different security and even physical existance in different environments.
>>>
>>>>> So why would I want the app to run from inside foxpro? I was having a problem with the fonts on the reports. They are just big black marks. No fonts, and I can't remember what causes that. I will post a message.
>>>>>
>>>>> Thanks again.
>>>>>
>>>>>Daniel
>>>>>
>>>>>
>>>>
>>>>As far as the location of the .PIF file, I think it needs to be wherever your run-time files are located for FoxPro.
>>>>
>>>>The black marks may be caused by the transparent setting of the label. This was a problem with the run-time of FPW under W95. Are you running FPW or VFP? I don't think this is a problem with VFP.
>>>>
>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>Check your FOXRUN.PIF properties and on the Program tab, there is a Close on Exit checkbox.
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>Daniel,
>>>>>>>>>>
>>>>>>>>>>Can't answer your question directly, but you could solve your problem use Ed Rauh's API_APPRUN utility in the files section... its far superior to the run command.
>>>>>>>>>>
>>>>>>>>>>Mace
>>>>>>>>>>
>>>>>>>>>>>Hi Everyone,
>>>>>>>>>>> Normaly when I execute a command useing run or ! I can select the 'close on exit' checkbox so that the window automatically closes after execution.
>>>>>>>>>>>
>>>>>>>>>>> I can't find this checkbox in Windows 2000. How do I mimic the behavior, ie. shut down the window after the command executes?
>>>>>>>>>>>
>>>>>>>>>>>Thanks.
>>>>>>>>>>>
>>>>>>>>>>>Daniel