Re: File problems

genedale wrote:
Back when I purchased my first computer with Windows 98 SE, 3 or 4
times a week I would get an error message when I tried to move,
rename, or delete a file that informed me that I could not do the
above function because someone else was using the file. No one else
had ever touched that computer but the people who built it and
shipped it to me. So no one else could have been using those files.

Now with my new computer and the installed XP Home Edition, I get the
same error message, but now it is 6 or more times A DAY.

Please post the complete text of this repeating "error message."


.

Relevant Pages

  • RE: Entry point RtlHashUnicodestring could not be located in the n
    ... Just tried it out and the error message is no longer appeared. ... Now it is just a matter of discovering the application which did install it ... two .Net-built applications on multiple Windows 2000 machines. ... should rename. ...
    (microsoft.public.win2000.general)
  • RE: Word 2000 Will Not Open
    ... I would say that the best soluiton is to rename NORMAL.dot. ... When you try to start Word, you may receive the following error message: ... Microsoft Word has encountered a problem and needs to close. ... Remove the Compatibility Mode Setting in Windows XP ...
    (microsoft.public.word.application.errors)
  • Re: avi file wont delete
    ... success with that on older Windows boxes where delete didn't work.) ... I get a standard error message that the program ... The router works as expected and even the Dell XP Pro box works ... If you rename them to something without an extension they will usually ...
    (rec.video.desktop)
  • Re: Cannot Delete File
    ... I am unable to rename the file (same error message as when trying delete), ... How about trying to remove it while in safe mode? ... When I try to delete the folder, ...
    (microsoft.public.windowsxp.general)
  • Re: DETAILS SOUGHT: Renaming this user-defined function removes any existing permissions and extend
    ... > receive the following error message ... > I think this caution could explain why drop and create was selected to use ... rename, both approaches will protect against ... and trying to let access rename it (using create/drop under the hood) ...
    (microsoft.public.access.adp.sqlserver)