Daniel.Webb@p0.f7.n391.z1.fidonet.org (Daniel Webb) (08/24/90)
I have used different versions of MS-DOS for many years now, but I have never had this error before: Sharing Violation Error Reading Drive C Abort, Retry, Fail This happened when I tried to delete a file that had the same attributes as the rest of the files in the directory, and I was able to delete the rest of the files. The difference was that this file was created by a DES encryption program. DESQview, X00.sys (communications driver), and Shield (virus protection) were all in memory. I was able to delete the file with any other program such as PcTools, but not with the DOS delete command. If Fail was entered after the error it said "Access denied". Also, the program list said "Access Denied". Again, checking with both Norton Util and PcTools, there was no read-only bit. Anybody got a suggestion? Could this be the side effects of a virus?
strobl@gmdzi.UUCP (Wolfgang Strobl) (08/25/90)
Daniel.Webb@p0.f7.n391.z1.fidonet.org (Daniel Webb) writes: > I have used different versions of MS-DOS for many years now, but I have >never had this error before: >Sharing Violation Error Reading Drive C > Abort, Retry, Fail >This happened when I tried to delete a file that had the same attributes as >the rest of the files in the directory, and I was able to delete the rest of >the files. > The difference was that this file was created by a DES encryption program. > DESQview, X00.sys (communications driver), and Shield (virus protection) >were all in memory. I was able to delete the file with any other program >such as PcTools, but not with the DOS delete command. > If Fail was entered after the error it said "Access denied". Also, >the program list said "Access Denied". Again, checking with both Norton >Util and PcTools, there was no read-only bit. > Anybody got a suggestion? > Could this be the side effects of a virus? > I think it is not an error within DOS, but, on the contrary, a programming/user error. In order to delete a file, you have to have exclusive access to it. Perhaps the encryption prog opened the file with sharing mode SH_DENYRW or something, and it wasn't closed, yet. If other programs allow deleting of a locked file, they are broken. This has nothing to do with the read-only bit. Wolfgang Strobl #include <std.disclaimer.hpp>