Mail Archives: djgpp/2003/12/31/08:15:55
On 31 Dec 2003 07:53:40 +0200, Eli Zaretskii <eliz AT elta DOT co DOT il> wrote:
>> From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
>> Newsgroups: comp.os.msdos.djgpp
>> Date: Tue, 30 Dec 2003 21:17:55 CST
>>
>> This sounds like NTVDM is not closing the file handle. To see if this
>> is the problem look for NTVDM.EXE in the task manager list and stop
>> the process (you may have one for each command window which has run
>> a DOS image). If you can then delete the file after stoping NTVDM, it's
>> a matter of figuring out what has gone wrong with NTVDM. I found that
>> if
>> you have problems killing NTVDM will fix lots of problems (using a
>> command
>> line WIN32 kill utility is helpful).
>
> There are also some fine utilities floating around that will show you
> the list of files open by each running process. Using one of them
> could shed some light on this problem.
ntvdm.exe is not running. I don't think it can leave the file open,
because a reboot doesn't help, only the secure mode console. I tried two
tools from sysinternals (handle and Process Explorer), but the files
aren't open in any process. I think the windows error message is
misleading. When I try to rm the files, I get "rm: cannot unlink
`damp.exe': Operation not permitted (EPERM)".
I check the dates of the binarys and only cat and grep (and some other
file utilitys) are dated before december 2000. Which package could that
be? fileutils?
I'm pretty sure I got updated packages for win2k, but I will try a fresh
install when I have access to a bigger internet pipe.
Regards,
Florian Schulze
- Raw text -