M
Michael R. Copeland
Guest
I've been using XP (SP2) for some time, and everything has been okay
afaics. I also use Visual Studion 6.0 to develop C/C++ appplications,
again without any real difficulty. A program I've been
developing/maintaining for years no longer compiles - because the
compiler can't write to the .exe after creating it. That is, when I try
to recompile the program, the Linker can't write over the existing
program filr.
I can't delete that file, either - I get an error that indicates the
file is "in use" or locked somehow. This is completely new behavior.
I can, however, rename the file and then recompile and run. Even so,
the next time I try to compile it, the same failures occur.
I've tried to go to Windows Explorer and examine the file's
attributes: nothing is checked. When I examine the attributes of the
directory (Debug), the "Read Only" attribute has a green blob in the
checkbox. I can toggle and apply the change, and I can retoggle several
times to get the check mark, blank, green blob...whatever. But when I
finally try to set the check box to unchecked, the .exe file still can't
be removed.
I can move the file (as well as rename it), and then compile - once.
Rebooting doesn't help, except that I can then remove the file(s)
I've created. It seems that something has changed the behavior of my
system...but the only installation actions that's occurred is the latest
Security Update from Microsoft. Having no idea what could be in those
changes, I can only guess that something in the update has munged my
system.
I don't know what to do, and the renaming/moving options are not at
all tolerable. I have a sick feeling I will encounter other problems
this issue has caused/will cause, and I'd like to deal with it asap.
Any thoughts? TIA...
afaics. I also use Visual Studion 6.0 to develop C/C++ appplications,
again without any real difficulty. A program I've been
developing/maintaining for years no longer compiles - because the
compiler can't write to the .exe after creating it. That is, when I try
to recompile the program, the Linker can't write over the existing
program filr.
I can't delete that file, either - I get an error that indicates the
file is "in use" or locked somehow. This is completely new behavior.
I can, however, rename the file and then recompile and run. Even so,
the next time I try to compile it, the same failures occur.
I've tried to go to Windows Explorer and examine the file's
attributes: nothing is checked. When I examine the attributes of the
directory (Debug), the "Read Only" attribute has a green blob in the
checkbox. I can toggle and apply the change, and I can retoggle several
times to get the check mark, blank, green blob...whatever. But when I
finally try to set the check box to unchecked, the .exe file still can't
be removed.
I can move the file (as well as rename it), and then compile - once.
Rebooting doesn't help, except that I can then remove the file(s)
I've created. It seems that something has changed the behavior of my
system...but the only installation actions that's occurred is the latest
Security Update from Microsoft. Having no idea what could be in those
changes, I can only guess that something in the update has munged my
system.
I don't know what to do, and the renaming/moving options are not at
all tolerable. I have a sick feeling I will encounter other problems
this issue has caused/will cause, and I'd like to deal with it asap.
Any thoughts? TIA...