Windows 2K Pro SP4

After copying a file to the floppy disk and then trying
to delete the file the error "Cannot delete <file> the
file is in use" appears. This is happening when students
in a lab are doing an exercise for this process. The
problem is very unpredictable as it will happen on a
machine one time and then on the same machine it won't
happen the next. It has happened on many different
machines with many different student disks and the
problem goes away if the machine is restarted. (Same disk
as before, only change is the machine restarting.) From
this, I don't think it is a hardware problem.

After the error happens, all access to the floppy returns
the same error if the access involves some modification
to ANY file on the disk, ie: copy, move, rename, delete.
Again, all the problems go away when the machine is
restarted.

Any ideas?

Thanks
Don

I guess the first question is "What process has an open handle to the
file?". Because you can reproduce this after a reboot, I'll recommend
oh.exe from us:
http://www.microsoft.com/windows2000...sting/oh-o.asp
SysInternals.com has some free tools that have similar capabilities. One of
them (Process Explorer) is UI instead of cmdline, though, if you're more
comfortable with that.
--
Drew Cooper [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


"Don Bossung" <(E-Mail Removed)> wrote in message
news:990201c3eb44$4604f7a0$(E-Mail Removed)...
> Windows 2K Pro SP4
>
> After copying a file to the floppy disk and then trying
> to delete the file the error "Cannot delete <file> the
> file is in use" appears. This is happening when students
> in a lab are doing an exercise for this process. The
> problem is very unpredictable as it will happen on a
> machine one time and then on the same machine it won't
> happen the next. It has happened on many different
> machines with many different student disks and the
> problem goes away if the machine is restarted. (Same disk
> as before, only change is the machine restarting.) From
> this, I don't think it is a hardware problem.
>
> After the error happens, all access to the floppy returns
> the same error if the access involves some modification
> to ANY file on the disk, ie: copy, move, rename, delete.
> Again, all the problems go away when the machine is
> restarted.
>
> Any ideas?
>
> Thanks
> Don
>

Thank you Drew, I will get oh.exe and try to identify the
process. One correction, we CANNOT reproduce the problem
after reboot (until it 'randomly' appears again).

Thanks for the tip

Don

>-----Original Message-----
>I guess the first question is "What process has an open
handle to the
>file?". Because you can reproduce this after a reboot,
I'll recommend
>oh.exe from us:
>http://www.microsoft.com/windows2000...fo/reskit/tool
s/existing/oh-o.asp
>SysInternals.com has some free tools that have similar
capabilities. One of
>them (Process Explorer) is UI instead of cmdline,
though, if you're more
>comfortable with that.
>--
>Drew Cooper [MSFT]
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"Don Bossung" <(E-Mail Removed)>
wrote in message
>news:990201c3eb44$4604f7a0$(E-Mail Removed)...
>> Windows 2K Pro SP4
>>
>> After copying a file to the floppy disk and then trying
>> to delete the file the error "Cannot delete <file> the
>> file is in use" appears. This is happening when
students
>> in a lab are doing an exercise for this process. The
>> problem is very unpredictable as it will happen on a
>> machine one time and then on the same machine it won't
>> happen the next. It has happened on many different
>> machines with many different student disks and the
>> problem goes away if the machine is restarted. (Same
disk
>> as before, only change is the machine restarting.) From
>> this, I don't think it is a hardware problem.
>>
>> After the error happens, all access to the floppy
returns
>> the same error if the access involves some modification
>> to ANY file on the disk, ie: copy, move, rename,
delete.
>> Again, all the problems go away when the machine is
>> restarted.
>>
>> Any ideas?
>>
>> Thanks
>> Don
>>
>
>
>.
>