TIP: Click on subject to list as thread! ANSI
echo: delphi
to: TOMMY USHER
from: BRYAN SMITH
date: 1996-07-08 21:14:00
subject: RUN A DOS BAT FILE.

On 07 Jul 96 Tommy Usher said to Bryan Smith...
 TU> Okay, the question is, does this (WinExecAndWait) work for WIN32?
 TU> I have used a similar routine under C/C++ for Window 3.1, but was
 TU> under the impression that Windows 95 had eliminated some of the
 TU> necessary elements of this routine.
Can't say - I'm keeping Win95 off my own PC for as long as I can .
However, I may have a possibility to test WinExecAndWait on a Windows NT
network server (i.e. running right on the server PC itself).  Would that
answer the question ?
W32 may be changed, but I would have thought they would provide SOME way in
the Win32-API to determine if a particular task was still active.  Or does
multi-threading (or whatever the concept is called) make that impossible ?
An alternative might be to run the batch file in a non-maximized window,
using WinExec, and to have the main task post a MessageDlg asking the user
to press OK when the batch file completes (or when the MS-DOS icon vanishes,
if we run minimized).  Yuck.
All of which raises an interesting question.  Is there any way that a Delphi
1.0 program can determine whether it is running under Win 3.1 or Win95 ?  In
other words, does WinAPI's GetVersion still work in Win32, and if so, what
version number does it return for Win95 ?
--- PPoint 2.00
---------------
* Origin: Kingston, Canada (1:249/109.11)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.