> Next step is to blow away my entire cygwin installation and install each
> package anew. Not sure what else I can do. This will be the 2nd time in
> 6 months I've had to do this.
As long as you're doing that, be sure to delete and redownload all of the
package files.
--
Unsubscribe info:
Larry Hall (Cygwin) wrote:
> Chuck wrote:
>> Larry Hall (Cygwin) wrote:
>>> Chuck wrote:
Larry Hall (Cygwin) wrote:
> Chuck wrote:
>> Larry Hall (Cygwin) wrote:
>>> Chuck wrote:
>
>
>> HD scan shows no errors.
>
>
>> I'm beginning to think I need to remove
Chuck wrote:
Larry Hall (Cygwin) wrote:
Chuck wrote:
Larry Hall (Cygwin) wrote:
Chuck wrote:
Larry Hall (Cygwin) wrote:
Chuck wrote:
HD scan shows no errors.
I'm beginning to think I need to remove and reinstall every cygwin
package, but I'm not certain that will fix it either. I've
Andrew DeFaria wrote:
> Chuck wrote:
>> I'd buy into the HD-getting-ready-to-fail argument more if I saw
>> weirdness on Windows too, but I don't. At least not yet. Plus scans of
>> the HD with both Tuneup Utilities and Windows itself are not turning
>> anything up.
> WAG but have you looked at the
Larry Hall (Cygwin) wrote:
> Chuck wrote:
>> Larry Hall (Cygwin) wrote:
>>> Chuck wrote:
Larry Hall (Cygwin) wrote:
> Chuck wrote:
>>>
>>>
HD scan shows no errors.
>>>
>>>
I'm beginning to think I need to remove and reinstall every cygwin
package, but I'm not certain that
Chuck wrote:
I'd buy into the HD-getting-ready-to-fail argument more if I saw
weirdness on Windows too, but I don't. At least not yet. Plus scans of
the HD with both Tuneup Utilities and Windows itself are not turning
anything up.
WAG but have you looked at the event log?
--
Andrew DeFaria
Chuck wrote:
Larry Hall (Cygwin) wrote:
Chuck wrote:
Larry Hall (Cygwin) wrote:
Chuck wrote:
HD scan shows no errors.
I'm beginning to think I need to remove and reinstall every cygwin
package, but I'm not certain that will fix it either. I've already
reinstalled both coreutils and cyg
DePriest, Jason R. wrote:
> I am not used the latest / greatest DaemonTools however since I am
> under the impression that it has become adware if you don't buy it.
>
> -Jason
>
It includes adware. You can unselect it in the installer.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscri
Matthew Woehlke wrote:
> Andrew DeFaria wrote:
>> I have no idea what this Daemon tools thing is. Hooks into the file
>> system. Gee that's beginning to sound like a root-kit!
>
> Last I checked, it is a program to allow you to mount CD images as "real
> drives". Since it is supposed to make them
Larry Hall (Cygwin) wrote:
> Chuck wrote:
>> Larry Hall (Cygwin) wrote:
>>> Have you checked if you can do similar operations with DOS commands? I
>>> believe what you're seeing here is a hardware (probably disk) problem.
>>> Years ago I had a failing disk pick off files randomly for a while until
On 2/12/07, Matthew Woehlke wrote:
Andrew DeFaria wrote:
> I have no idea what this Daemon tools thing is. Hooks into the file
> system. Gee that's beginning to sound like a root-kit!
Last I checked, it is a program to allow you to mount CD images as "real
drives". Since it is supposed to make
Andrew DeFaria wrote:
I have no idea what this Daemon tools thing is. Hooks into the file
system. Gee that's beginning to sound like a root-kit!
Last I checked, it is a program to allow you to mount CD images as "real
drives". Since it is supposed to make them look "real" enough to even
fool
Chuck wrote:
Andrew DeFaria wrote:
which makes me think that maybe its the writing to stdout that's
failing.
At this point I'd suggest SpinRite: http://www.grc.com/sr/spinrite.htm
Haven't tried spinrite yet but I did do a "thorough" check of the
drive using Tuneup Utilities. That's the one t
Chuck wrote:
Larry Hall (Cygwin) wrote:
Have you checked if you can do similar operations with DOS commands? I
believe what you're seeing here is a hardware (probably disk) problem.
Years ago I had a failing disk pick off files randomly for a while until
the whole thing finally went.
Is the
Larry Hall (Cygwin) wrote:
>
> Have you checked if you can do similar operations with DOS commands? I
> believe what you're seeing here is a hardware (probably disk) problem.
> Years ago I had a failing disk pick off files randomly for a while until
> the whole thing finally went.
>
>
Is there
Andrew DeFaria wrote:
>> which makes me think that maybe its the writing to stdout that's failing.
>>
>>
> At this point I'd suggest SpinRite: http://www.grc.com/sr/spinrite.htm
Haven't tried spinrite yet but I did do a "thorough" check of the drive
using Tuneup Utilities. That's the one that req
Chuck wrote:
Andrew DeFaria wrote:
Chuck wrote:
At first I thought my recent problems with cygwin were limited to the
occasional "ls" command listing nothing. Run it again an it works
(usually). Now the problems are getting worse. I tried to "rm" a file
that I own and it didn't fully delete it.
Larry Hall (Cygwin) wrote:
> Chuck wrote:
>> Larry Hall (Cygwin) wrote:
>>> Chuck wrote:
>
>
>
>>
>> HD scan shows no errors.
>
>
>
>> I'm beginning to think I need to remove and reinstall every cygwin
>> package, but I'm not certain that will fix it either. I've already
>> reinstalled both c
Andrew DeFaria wrote:
> Chuck wrote:
>> At first I thought my recent problems with cygwin were limited to the
>> occasional "ls" command listing nothing. Run it again an it works
>> (usually). Now the problems are getting worse. I tried to "rm" a file
>> that I own and it didn't fully delete it. It
Frodak wrote:
> Back up your stuff.
>
> This happened to me before days before ntfs.sys
> deleted itself. I then asked my boss for a new
> hard-drive and then did a fresh windows install.
>
> I had bizarre issues.
>
> Amongst what you described that happened for a while,
> the following occurr
Chuck wrote:
Larry Hall (Cygwin) wrote:
Chuck wrote:
At first I thought my recent problems with cygwin were limited to the
occasional "ls" command listing nothing. Run it again an it works
(usually). Now the problems are getting worse. I tried to "rm" a file
that I own and it didn't fully delet
--- Chuck wrote:
> Larry Hall (Cygwin) wrote:
>
> >
> > Have you checked if you can do similar operations
> with DOS commands? I
> > believe what you're seeing here is a hardware
> (probably disk) problem.
> > Years ago I had a failing disk pick off files
> randomly for a while until
> > the w
Chuck wrote:
At first I thought my recent problems with cygwin were limited to the
occasional "ls" command listing nothing. Run it again an it works
(usually). Now the problems are getting worse. I tried to "rm" a file
that I own and it didn't fully delete it. It corrupted it. An ls of the
file s
Chuck wrote:
Larry Hall (Cygwin) wrote:
Chuck wrote:
HD scan shows no errors.
I'm beginning to think I need to remove and reinstall every cygwin
package, but I'm not certain that will fix it either. I've already
reinstalled both coreutils and cygwin itself. I've even tried rolling
bot
Larry Hall (Cygwin) wrote:
> Chuck wrote:
>> At first I thought my recent problems with cygwin were limited to the
>> occasional "ls" command listing nothing. Run it again an it works
>> (usually). Now the problems are getting worse. I tried to "rm" a file
>> that I own and it didn't fully delete i
Larry Hall (Cygwin) wrote:
>
> Have you checked if you can do similar operations with DOS commands? I
> believe what you're seeing here is a hardware (probably disk) problem.
> Years ago I had a failing disk pick off files randomly for a while until
> the whole thing finally went.
>
>
Everyth
Chuck wrote:
At first I thought my recent problems with cygwin were limited to the
occasional "ls" command listing nothing. Run it again an it works
(usually). Now the problems are getting worse. I tried to "rm" a file
that I own and it didn't fully delete it. It corrupted it. An ls of the
file s
27 matches
Mail list logo