On 5/3/07, Dave Korn wrote:
On 02 May 2007 22:37, Michael D. Adams wrote:
> This is a bit of a bummer. I can't reproduce the error anymore. I
> have absolutely no idea what changed. I moved the old version out of
> the way and cleaned the registry, but the bug still won't appear. I
> guess j
On 02 May 2007 14:13, Aaron Gray wrote:
>> Just on the offchance, do you have any of these installed?
>>
>> Windows Defender
>
> AFAIK Windows Defender is built in to Vista.
>
> Aaron
Been known to cause problems before:
http://cygwin.com/ml/cygwin/2007-01/msg00742.html
although it's not
Just on the offchance, do you have any of these installed?
Windows Defender
AFAIK Windows Defender is built in to Vista.
Aaron
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/
On 02 May 2007 22:37, Michael D. Adams wrote:
> This is a bit of a bummer. I can't reproduce the error anymore. I
> have absolutely no idea what changed. I moved the old version out of
> the way and cleaned the registry, but the bug still won't appear. I
> guess just hope the next person to ru
On 4/30/07, Igor Peshansky wrote:
On Sun, 29 Apr 2007, Michael D. Adams wrote:
> On 4/24/07, Larry Hall (Cygwin) wrote:
> > Michael D. Adams wrote:
> > > On 4/23/07, Dave Korn wrote:
> > >> On 24 April 2007 00:19, Michael D. Adams wrote:
>
> > >> What's going on here could be related to secu
On Sun, 29 Apr 2007, Michael D. Adams wrote:
On 4/24/07, Larry Hall (Cygwin) wrote:
> Michael D. Adams wrote:
> > On 4/23/07, Dave Korn wrote:
> >> On 24 April 2007 00:19, Michael D. Adams wrote:
> >> What's going on here could be related to security changes in the
> >> way Vista handles dll
On 4/24/07, Larry Hall (Cygwin) wrote:
Michael D. Adams wrote:
> On 4/23/07, Dave Korn wrote:
>> On 24 April 2007 00:19, Michael D. Adams wrote:
>> What's going on here could be related to security changes in the way
>> Vista
>> handles dll and executable search paths, perhaps, but that's f
Michael D. Adams wrote:
> On 4/23/07, Dave Korn wrote:
>> On 24 April 2007 00:19, Michael D. Adams wrote:
>> > On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
>> The workaround for this problem that I have found is to set the
>> *Windows* path to include C:\cygwin\bin before running
On 4/23/07, Dave Korn wrote:
On 24 April 2007 00:19, Michael D. Adams wrote:
> On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
The workaround for this problem that I have found is to set the
*Windows* path to include C:\cygwin\bin before running setup.exe. So
for example thi
On 4/23/07, Dave Korn wrote:
On 24 April 2007 00:19, Michael D. Adams wrote:
> On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
Please, Michael, try and http://cygwin.com/acronyms#PCYMTNQREAIYR avoid
quoting people's email addresses. Thanks.
Thank you for pointing that out. I had nev
On 24 April 2007 00:19, Michael D. Adams wrote:
> On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
Please, Michael, try and http://cygwin.com/acronyms#PCYMTNQREAIYR avoid
quoting people's email addresses. Thanks.
The workaround for this problem that I have found is to set the
*W
On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
Brian Dessent wrote:
> > The workaround for this problem that I have found is to set the
> > *Windows* path to include C:\cygwin\bin before running setup.exe. So
> > for example this sequence works:
> >
> > set PATH=C:\cygwin\bin;%PATH%
> > s
Brian Dessent wrote:
> > The workaround for this problem that I have found is to set the
> > *Windows* path to include C:\cygwin\bin before running setup.exe. So
> > for example this sequence works:
> >
> > set PATH=C:\cygwin\bin;%PATH%
> > setup.exe
> >
> > Then /bin/sh is actually created, the
"Michael D. Adams" wrote:
> > Please try the latest setup.exe snapshot, if you can. And even better
> > would be to debug the problem. I don't have access to a Vista system
> > but if I did I think I would start by running it under gdb/insight and
> > putting a breakpoint at script.cc:run() righ
On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
"Michael D. Adams" wrote:
> The workaround for this problem that I have found is to set the
> *Windows* path to include C:\cygwin\bin before running setup.exe. So
> for example this sequence works:
>
> set PATH=C:\cygwin\bin;%PATH%
> setup.ex
Brian Dessent wrote:
"Michael D. Adams" wrote:
he workaround for this problem that I have found is to set the
*Windows* path to include C:\cygwin\bin before running setup.exe. So
for example this sequence works:
set PATH=C:\cygwin\bin;%PATH%
setup.exe
Then /bin/sh is actually created, the pro
On 4/22/07, Michael D. Adams <[EMAIL PROTECTED]> wrote:
On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
> "Michael D. Adams" wrote:
>
> > The workaround for this problem that I have found is to set the
> > *Windows* path to include C:\cygwin\bin before running setup.exe. So
> > for example
On 4/22/07, Brian Dessent wrote:
"Michael D. Adams" wrote:
> The workaround for this problem that I have found is to set the
> *Windows* path to include C:\cygwin\bin before running setup.exe. So
> for example this sequence works:
>
> set PATH=C:\cygwin\bin;%PATH%
> setup.exe
[Snip]
That wou
On 2007-04-22 14:38Z, Michael D. Adams wrote:
> On 4/22/07, Brian Dessent
[raw email address removed]
> wrote:
>>
>> Please try the latest setup.exe snapshot, if you can. And even better
>> would be to debug the problem.
[...]
> Where are those snapshots located? A quick google didn't turn them
"Michael D. Adams" wrote:
> The workaround for this problem that I have found is to set the
> *Windows* path to include C:\cygwin\bin before running setup.exe. So
> for example this sequence works:
>
> set PATH=C:\cygwin\bin;%PATH%
> setup.exe
>
> Then /bin/sh is actually created, the prompt is
20 matches
Mail list logo
