Peter Ekberg lysator.liu.se> writes:
>
> On Sun, May 28, 2006 at 10:40:34PM +, Torfinn Ottesen wrote:
> >
>
>
> > I did this for three programs, prog1 (commercial, external),
> > prog2 (inhouse, compiled on Cygwin) and native cygwin pr
Larry Hall (Cygwin cygwin.com> writes:
> The key words here are "If you use Registry Editor incorrectly". In other
> words, if you modify something other than what's recommended, you might
> cause yourself other problems. This is standard boiler-plate legalese that's
> spewed whenever mention o
pasting). I would like to help,
> but all information I have at this point is rather negative... One
> definite data point is that unloading and reloading just Cygwin1.dll (by
> exiting all Cygwin processes) fixes the problem for me (until the next
> time I run that resource-intensive sc
OS : Windows XP Pro SP1
cygwin: fresh as of february 2006
I am trying to run a lot of numerical analysis in loop using "bash",
principally as follows:
for case in 1 2 3 ... 132
do
prepare input-$case
analyse input-$case
save results-$case
done
I find that my loops are O
at.exe and id.exe) everything appears to be fine.
Info:
We compared the WinXPs for the machines, it appears that the newest machine
is using
WinXP Service Pack 2 as opposed to SP1 for the others where we got no
failure messages.
Does anyone know why this is happening
Regards Torfi
5 matches
Mail list logo
