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

BS>On 08 Jul 96 Tommy Usher said to Bryan Smith ...
BS> TU> Okay, the question is, does this (WinExecAndWait) work for WIN32?
BS> TU> I have used a similar routine under C/C++ for Window 3.1, but was
BS> TU> under the impression that Windows 95 had eliminated some of the
BS> TU> necessary elements of this routine.
BS>Re WinExecAndWait under Win32.  I don't have Win95, but I'm happy to 
eport
BS>that WinExecAndWait seems to run OK on the console of a Win NT 3.51 
etwork
BS>Server.  I set the test code up as follows, so that if the MessageDlg had
BS>appeared prematurely (and been hidden behind the spawned task) one would
BS>still know something was wrong from the timing ...
Lovely....  I spent $15 for a component I really didn't need. :-(  Oh
well, it works.
BS>  Const s : string = '' ;
BS>  .......
BS>  s := TimeToStr(Time) ;
BS>  WinExecAndWait(.......... ;
BS>  MessageDlg('Spawned task was started at ' + s
BS>             +'.  This dialog appeared at ' + TimeToStr(Time),
BS>             mtInformation,[mbOK],0) ;
BS>Can someone please confirm or deny Tommy's suspicion that WinExecAndWait
BS>will not work correctly under Win95 ?
I am probably wrong.  It was based on a statement in a book, which was
trying to push the WIN32 method of launching other programs, which I
really wasn't interested in trying to figure out at the time.  That's
what I get for being lazy.   Right now, I't trying to figure out the
ListView control.  I've has some extremely bizarre behavior from it...
---
 * QMPro 1.52 * "Like torment Cardassians?" - O'Brien to Q
--- WILDMAIL!/WC v4.12 
---------------
* Origin: GC-BBS! (1:226/810.0)

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™.