doug
January 21st, 2004, 01:26
Hello, here's something that happened to me today:
As I was learning on the "Rich"-stuff that ms link.exe adds on exe files (and tips on shrinking exes size), I downloaded a STUB.exe to use with the LINK's /STUB switch.
I did the following:
Extract file to desktop, hex edit file.. etc.. Close hex editor
When I try to delete it, Windows tells me a sharing error ("... In use in some other program?"
..
Buggy hex editor I thought..
reboot
try to delete file, still windows file protection problem.. (wtf!)
The file is locked but I can still edit/save change to it..
Every monitoring tool I tried from sysinternals failed to tell me which process had an handle to the file (see later)
Bit annoying to have these files laying around the desktop permanently. To remove the file, I hex edited the file(s) and I pasted the code from a 'normal' PE exe. Rebooted, file can now be deleted!
Seems like a weird thing to me.. Does windows assume old dos files shouldnt be deleted?
Since no tool could report an opened handle, I'm guessing there is some kind of check performed on the file before it's given the okay to be deleted?
Os: Windows XP SP1.
Is this a documented issue? did anyone else have that problem?
As I was learning on the "Rich"-stuff that ms link.exe adds on exe files (and tips on shrinking exes size), I downloaded a STUB.exe to use with the LINK's /STUB switch.
I did the following:
Extract file to desktop, hex edit file.. etc.. Close hex editor
When I try to delete it, Windows tells me a sharing error ("... In use in some other program?"

Buggy hex editor I thought..
reboot
try to delete file, still windows file protection problem.. (wtf!)
The file is locked but I can still edit/save change to it..
Every monitoring tool I tried from sysinternals failed to tell me which process had an handle to the file (see later)
Bit annoying to have these files laying around the desktop permanently. To remove the file, I hex edited the file(s) and I pasted the code from a 'normal' PE exe. Rebooted, file can now be deleted!
Seems like a weird thing to me.. Does windows assume old dos files shouldnt be deleted?
Since no tool could report an opened handle, I'm guessing there is some kind of check performed on the file before it's given the okay to be deleted?
Os: Windows XP SP1.
Is this a documented issue? did anyone else have that problem?