Stacey
Thanks for that suggestion but it doesn't fix the problem.
The interesting thing is that the batch file that I have
written works perfectly on Win2K but not on Win95.
It's very frustrating to try to track down, because the client
site only run's it once a day so I can only try a new fix
Further to this:
For what it's worth, I have been able to simulate the Win95 behaviour
by replacing
Call NewPatch.exe with
Start NewPatch.exe
Not sure if that gives any clues??
Mark
On 30 May 2003 at 10:59, Mark Howard wrote:
Stacey
Thanks for that suggestion but it doesn't
Mark,
Why not have the patch program execute the following commands as it exits? It
could be parameterised, so an ini file tells the patch program what (if any)
batch file to execute on exit, and the attribute and backup commends are in the
batch file.
In fact you could go further and allow for
this may be of help...
START ["title"] [/Dpath] [/I] [/MIN] [/MAX]
[/SEPARATE | /SHARED] [/LOW | /NORMAL | /HIGH
| /REALTIME | /ABOVENORMAL | /BELOWNORMAL]
[/WAIT] [/B] [command/program]
[parameters]
"title"
Title to display in window title bar.
path Starting
directory
B Start
You don't have a test machine setup with one of the operating systems you
deploy to?
JED
[EMAIL PROTECTED] wrote on 30/05/2003 08:59:03 AM:
It's very frustrating to try to track down, because the client
site only run's it once a day so I can only try a new fix once
a day. (Can't fix
Instead of running a batch file, write a simple executable to do what you
want.
Even if it just calls the batch commands.
JED
[EMAIL PROTECTED] wrote on 30/05/2003 10:11:40 AM:
Further to this:
For what it's worth, I have been able to simulate the Win95 behaviour
by replacing
Call
Mark
I believe the START command also is supported in W95
so if in your batch file you have
START /w foo1.exe
START /w foo2.exe
foo2 will wait for foo1 to complete before starting
i'm not 100% sure about this - but i think it's correct
-ns
http://www.roserox.co.th
- Original Message
Hello John,
Not something to do with Outlook/Express wanting to dial up on start? If so,
just uncheck that option within the program (it can change by itself I believe).
Otherwise you might need to check what is actually running, and asking for DUN
then run that - might be spyware or similar.
Al+
Well! Thanks for all the replies:
Paul - 1. re use of Pause. Yep, that would have been a last
resort!
Pedrocelli - the Patch builder is 3rd party with no source.
Jeremy - 1 No. 2 I was sort of coming to the conclusion that I
might have to do this.
Paul and Nello (again!)
This is
Use Start not Call. Start.exe has a Wait parameter which should do what you
need and works on all Win O/S's.
Ross.
---
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website:
Mark,
in addition to the 'start wait' option others have mentioned, I have had on
occasion to add a delay in a batch file while waiting for a file to be fully
written/closed etc.
I have a small wait.exe which takes a parameter of no. of seconds to wait -
I can send it if you want.
regards,
Steve
actually i have a program like this too and was
going to suggest it - but then i wondered ...
how to get W95 to wait for the wait program?
won't W95 just start the wait program and then
immediately execute the next batch command
(before the wait expires)?
-ns
http://www.roserox.co.th
This being Friday, here's an answer to my own question ...
if the exe being run by the .BAT file is a 16bit DOS
exe then W95 will wait for it to finish before
executing the next command in the .BAT file.
if the exe being run is a 32 bit Win32 exe then w95
can (and does) start it and then
Maybe...
I don't have a Win95 pc to check - although it is a Dos (Clipper) app not a
win32 app if that makes a difference.
Steve
-Original Message-
From: Nello Sestini [mailto:[EMAIL PROTECTED]
Sent: Friday, 30 May 2003 1:46 p.m.
To: Multiple recipients of list delphi
Subject: Re:
14 matches
Mail list logo
