Hugh McMaster wrote:
Hi Larry, and everyone,
I would just like to add that this issue has been resolved by Agnitum,
the developers of Outpost Firewall.
Terrific! This list thanks you and them. :-)
--
Larry Hall http://www.rfk.com
RFK Partners, Inc.
Hi Larry, and everyone,
I would just like to add that this issue has been resolved by Agnitum,
the developers of Outpost Firewall.
Hugh
On 29/11/06, Larry Hall (Cygwin) wrote:
It messes with the network stack. This happens at install time, not
run-time. That means that you have to un-install
Mikkel Erup wrote:
--- Hugh McMaster <[EMAIL PROTECTED]> wrote:
Hi everyone,
After doing some analysis of this issue, I have determined the
problem
to most likely be Agnitum Outpost Firewall. I am not disputing
your
findings (Mikkel, anyone else), but all of the evidence that I
have
learned p
--- Hugh McMaster <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> After doing some analysis of this issue, I have determined the
> problem
> to most likely be Agnitum Outpost Firewall. I am not disputing
> your
> findings (Mikkel, anyone else), but all of the evidence that I
> have
> learned poin
Hi everyone,
After doing some analysis of this issue, I have determined the problem
to most likely be Agnitum Outpost Firewall. I am not disputing your
findings (Mikkel, anyone else), but all of the evidence that I have
learned point to this. In fact, I installed the trial version 4.0 of
Outpos
--- Mikkel Erup <[EMAIL PROTECTED]> wrote:
> >DaveK wrote:
> >You wouldn't by any chance be using any kind of firewall or
> >internet
> >security packages, would you? Something by Norton/McAffee,
> >perhaps?
>
> I am using outpost pro but that is not started in safe mode
> with
> network where
>DaveK wrote:
>You wouldn't by any chance be using any kind of firewall or
>internet
>security packages, would you? Something by Norton/McAffee,
>perhaps?
I am using outpost pro but that is not started in safe mode with
network where Cygwin produces the errors described.
Cygwin only works for me
Christopher Faylor wrote:
> The address in question is in cygwin's cygthread handling code.
> Historically, this has been affected by things like scanners/firewalls
> and special drivers, so this is a good thought.
The clincher for me is when he said it works in safe mode without
networking, but
On Mon, Nov 27, 2006 at 11:52:55AM -0500, Larry Hall (Cygwin) wrote:
>Christopher Faylor wrote:
>>On Mon, Nov 27, 2006 at 02:36:45PM -, Dave Korn wrote:
>>>On 27 November 2006 14:06, Mikkel Erup wrote:
>>>
>>>
Making sh.exe a copy of bash.exe and running the installer to
reinstall produ
On 27 November 2006 16:53, Larry Hall (Cygwin) wrote:
>
> I'm with Dave and Mikkel in believing that the difference between safe mode
> and not is significant. I'm betting on virus scanners/firewalls or some
> network driver.
Or Logitech. Never let us forget Logitech. Never let us forget
Christopher Faylor wrote:
On Mon, Nov 27, 2006 at 02:36:45PM -, Dave Korn wrote:
On 27 November 2006 14:06, Mikkel Erup wrote:
Making sh.exe a copy of bash.exe and running the installer to
reinstall produces the same error for bash.exe, ash.exe, sed.exe,
sh.exe, rm.exe, cmp.exe and a some
On Mon, Nov 27, 2006 at 02:36:45PM -, Dave Korn wrote:
>On 27 November 2006 14:06, Mikkel Erup wrote:
>
>
>> Making sh.exe a copy of bash.exe and running the installer to
>> reinstall produces the same error for bash.exe, ash.exe, sed.exe,
>> sh.exe, rm.exe, cmp.exe and a some others (The instr
On 27 November 2006 14:06, Mikkel Erup wrote:
> Making sh.exe a copy of bash.exe and running the installer to
> reinstall produces the same error for bash.exe, ash.exe, sed.exe,
> sh.exe, rm.exe, cmp.exe and a some others (The instruction at
> "0x6100365f" referenced memory at "0x006ada90". The m
--- Mikkel Erup <[EMAIL PROTECTED]> wrote:
>
> --- "Larry Hall (Cygwin)" <[EMAIL PROTECTED]>
> wrote:
>
> > Mikkel Erup wrote:
> > > I get a message box with the following error trying to run
> > > any cygwin program:
> > >
> > > The instruction at "0x6100365f" referenced memory at
> > > "0x0
--- "Larry Hall (Cygwin)" <[EMAIL PROTECTED]>
wrote:
> Mikkel Erup wrote:
> > I get a message box with the following error trying to run
> > any cygwin program:
> >
> > The instruction at "0x6100365f" referenced memory at
> > "0x006ada90".
> > The memory could not be "written".
> >
> > id.exe,
Hugh McMaster wrote:
Hi Mikkel,
I have tried to install Cygwin, with no luck. The installation did
not even finish the final configuration before resulting in errors.
By this, I mean 'bash.exe' and 'id.exe' were terminated, resulting in
a Microsoft Error Reporting service window appearing.
It
Mikkel Erup wrote:
I get a message box with the following error trying to run
any cygwin program:
The instruction at "0x6100365f" referenced memory at
"0x006ada90".
The memory could not be "written".
id.exe, bash.exe etc. All of them produce the error.
Somtimes, like 1 out of 50 or less a prog
Hi Mikkel,
I have tried to install Cygwin, with no luck. The installation did
not even finish the final configuration before resulting in errors.
By this, I mean 'bash.exe' and 'id.exe' were terminated, resulting in
a Microsoft Error Reporting service window appearing.
It would appear that ther
Hi Mikkel,
I too have had this problem, as has another Cygwin user on this
mailing list. I am now attempting to install Cygwin once more to
check whether this problem still exists. If it does, it could be the
result of a recent change to a package.
I will let you know how things go.
Hugh
On
19 matches
Mail list logo
