OK, I think with your help I've discovered what happened although I had to get into windows to fix it.
Seems my "D" drive is almost full and ripping in-a-godda-da-vida probably filled it up and the drive locked up. In windows I could write and delete files OK so I ran scan disk, no errors found but back in Linux I could write OK - that is until I think I filled up the drive again. I tried mattrib but it didn't work, also fsch.vfat but again it didn't work. Both are probably user error. The mattrib didn't like /D or D or anything like that. Thanks and if someone can give me better (simpiler/comlete) instructions for running the linux version of scan disk that would be great. Brad On Sun, 6 Jul 2003, Jan L. Peterson wrote: > > If the system knows it needs to be checked, but it can't figure how to > > check it, it will make it read-only until it's been checked. > > If you read his followup, he could write to other directories on the > filesystem. There was a particular subtree that he couldn't write to. > > It probably wouldn't hurt, though, to boot windows and run a disk check. > > -jan- > ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
