On Tue, 13 Nov 2007, Thomas Baker wrote:
The /bin/pdksh script sequence that is causing problems is:
[snip]
The obvious question is: do you still get the error if you replace pdksh
with bash, or is the problem pdksh-specific?
When you reduce this to a minimal testcase, are there bits of that
On Thu, Nov 22, 2007 at 12:56:33PM -0500, Igor Peshansky wrote:
The /bin/pdksh script sequence that is causing problems is:
[snip]
The obvious question is: do you still get the error if you replace pdksh
with bash, or is the problem pdksh-specific?
When you reduce this to a minimal
On Wed, Nov 14, 2007 at 06:03:42PM -0500, Larry Hall (Cygwin) wrote:
Lewis Hyatt wrote:
These machines have an anti-virus program, but the same one I have
been using for the past two or three years. The filenames either have
no extension, or .txt.
That's most likely the problem anyway,
On Wed, Nov 14, 2007 at 10:07:09AM +0100, Corinna Vinschen wrote:
I would be grateful if someone could suggest a way to test
this. Would it make sense (and is it possible) to replace
the Cygwin kernel or the coreutils package (because of
mv) with earlier versions and see if the script
On Nov 14 08:22, Thomas Baker wrote:
I would be grateful if someone could suggest a way to test
this. Would it make sense (and is it possible) to replace
the Cygwin kernel or the coreutils package (because of
mv) with earlier versions and see if the script works then?
You should first create
These machines have an anti-virus program, but the same one I have
been using for the past two or three years. The filenames either have no
extension, or .txt.
That's most likely the problem anyway, what happens if you turn it off?
-Lewis
--
Unsubscribe info:
Lewis Hyatt wrote:
These machines have an anti-virus program, but the same one I have
been using for the past two or three years. The filenames either have
no extension, or .txt.
That's most likely the problem anyway, what happens if you turn it off?
This is possible, particularly if the
Morgan Gangwere wrote:
/!\ WOOGA WOOGA /!\
Possible Stupid human Error!
/!\ OOOPS OOOPS /!\
if the copy of xp is new enough, its got a funky little tool called
the Windows Malware Detection And removal Tool (a freind of mine who
is an MS MVP has had the same problem as you just under a
On Mon, Nov 12, 2007 at 04:03:14AM -0600, René Berber wrote:
[snip]
However, the other problem (see below) has occurred --
sporadically -- on three different machines, all running
German or English-language versions of XP, two with SATA
disks and one with an ATA disk, all with freshly
On Mon, Nov 12, 2007 at 09:38:03PM -0500, Morgan Gangwere wrote:
if the copy of xp is new enough, its got a funky little tool called
the Windows Malware Detection And removal Tool (a freind of mine who
is an MS MVP has had the same problem as you just under a different
circumstance.)
I'll
On Tue, Nov 13, 2007 at 09:58:31AM -0500, Robert Pendell wrote:
One other thing I wanted to add to this was make sure the drives are not
overheating. Some drives will actually shut down or begin to act
erratically if they get too hot. I discovered this when doing work with
my external
On Tue, Nov 13, 2007 at 06:06:21PM +0100, Thomas Baker wrote:
if the copy of xp is new enough, its got a funky little tool called
the Windows Malware Detection And removal Tool (a freind of mine who
is an MS MVP has had the same problem as you just under a different
circumstance.)
I
On Tue, Nov 13, 2007 at 05:59:01PM +0100, Thomas Baker wrote:
The speed is not the problem, it could be the usual suspect: an
anti-virus, unlikely because the data written is not executable but it
could be adding an extraneous delay between data written and data read.
I'll ask the guy who
René Berber wrote:
[snip]
I have searched FAQs and mailing lists for problems with
timeout and the like but find nothing obviously relevant.
[snip]
I have seen that problem and it has nothing to do with Cygwin. The
problem is with SATA drives and Window's asynchronous unbuffered disk
Thomas Baker wrote:
[snip]
However, the other problem (see below) has occurred --
sporadically -- on three different machines, all running
German or English-language versions of XP, two with SATA
disks and one with an ATA disk, all with freshly downloaded
installations of cygwin.[snip]
OK,
/!\ WOOGA WOOGA /!\
Possible Stupid human Error!
/!\ OOOPS OOOPS /!\
if the copy of xp is new enough, its got a funky little tool called
the Windows Malware Detection And removal Tool (a freind of mine who
is an MS MVP has had the same problem as you just under a different
circumstance.)
I took
Thomas Baker wrote:
[snip]
I have searched FAQs and mailing lists for problems with
timeout and the like but find nothing obviously relevant.
[snip]
I have seen that problem and it has nothing to do with Cygwin. The
problem is with SATA drives and Window's asynchronous unbuffered disk
I/O,
17 matches
Mail list logo
