Home > Archive > Clipper > September 2005 > Re: swpruncmd() - limit of calls
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: swpruncmd() - limit of calls
|
|
| frank van nuffel 2005-09-15, 7:55 am |
| > clipper 5.2e
> blinker - any
> OS - any
>
> for i:=1 to 200
> swpruncmd("dir *.txt")
> next
>
> result - gpf after appr. 100 calls.
>
> Yours suggestion?
cmd := getenv( "COMSPEC" )
if( "CMD" $ cmd ) // assuming this is XP
swpruncmd( "start /wait c:\windows\system32\command.com /c dir *.txt")
else
swpruncmd("dir *.txt")
end
| |
| frank van nuffel 2005-09-15, 7:55 am |
|
> frank van nuffel wrote:
>
> Note: ^^^^^^^^^^^^^^^^^^ OS - any
therefore, if else end
>
> XP: result - GPF after appr. 100 calls
>
>
> Win9x: result - GPF after appr. 100 calls
>
>
> Any suggestions?
what location does your environment's temp variable point to?
same q for your executable's swap file; see docs
/SD<path> Directory for SWPRUNCMD() swap file
any chance there's not enough free space?
f
ps:
Blinker supports version 5.01a, 5.2e and 5.3b of CA-Clipper to create DOS
and DOS extended programs. No other versions are supported, so please
obtain the appropriate upgrade from Computer Associates before attempting
to use Blinker with CA-Clipper 5.x.
| |
| frank van nuffel 2005-09-15, 7:55 am |
| >> what location does your environment's temp variable point to?
>
> 1. TEMP variable proint to different location in different OS
> 2. TEMP variable is CORRECT, there is full access rights to this
> location
> 3. Free disk space is enought
> 4. First 100(apprx) swpruncmd() calls - without errors
> 5. There is GPF in ANY environment (os, hardware... etc)
sorry, ran out of clues, but a fellow comp.lang.clipper reader
recently mentioned CauseWay, if anything else works out for
your issue, why not give it a try.
http://www.devoresoftware.com/freesource/cwsrc.htm
f
post from around July, 25th subject: Blinker 7
|
|
|
|
|