×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I notice that I can open Word with 'Start Winword.exe' but the command
doesn't wait for Word to be ended. I put the >command in a .bat and that
way the i5 waits for Word to end. What's happening here exactly?
'start' by default does not block (i.e. wait for the process to finish),
but it can be made to do so with: 'start /wait winword.exe'.
When you stick it in a .bat file, you are invoking cmd.exe directly, and
it does block by default. Note that you can also over-ride this
behaviour with a comand line switch as well: 'cmd /c something.bat'.
Although it will only exit if the started processes were native windows
apps, it will still wait for DOS apps to finish.
Typically, 'start' is intended to start native windows programs, while
'cmd' is still the default command shell.
Here's a more in depth description of the two commands:
http://www.ss64.com/nt/cmd.html
http://www.ss64.com/nt/start.html
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
