?
=?iso-8859-1?Q?olof_h=E5nell?=
I've installed ms antispyware and have this version:
Microsoft AntiSpyware Version: 1.0.501
Spyware Definition Version: 5680 (2005-01-08 14:25:40)
The problem is as follows:
I have a .bat-file that i compile some .cs-files into dlls
with which contains this(amongst other things):
mkdir "..\bin"
copy *.dll "..\bin\"
del *.dll
this is just to copy the dlls into the bin folder and then
delete the compiled ones. very simple. Anyway, after I've
installed the antispyware software it, as it should,
complains that a scriptfile is going to run and i could
choose Yes or No. I choosed Yes since I really wanted to
compile. But something strange happened, suddenly the dos-
window started to print dll-named that did not belong to
my project, I aborted the batch-file as fast as I could
and began to thing about what happend actually.
After some investigation i found a bin-folder in
c:\windows\ containing lot's of dlls... So what I think is
that the bat-file was actually runned in
c:\windows\system32\ and not in the folder from which i
double-clicked it. I'm very very happy that i aborted the
batch-file since otherwise the "del *.dll" would have
runned.
This "bug"? doues only occur the first time, when i run
the bat-file now it runs in the same folder as it is in.
Microsoft AntiSpyware Version: 1.0.501
Spyware Definition Version: 5680 (2005-01-08 14:25:40)
The problem is as follows:
I have a .bat-file that i compile some .cs-files into dlls
with which contains this(amongst other things):
mkdir "..\bin"
copy *.dll "..\bin\"
del *.dll
this is just to copy the dlls into the bin folder and then
delete the compiled ones. very simple. Anyway, after I've
installed the antispyware software it, as it should,
complains that a scriptfile is going to run and i could
choose Yes or No. I choosed Yes since I really wanted to
compile. But something strange happened, suddenly the dos-
window started to print dll-named that did not belong to
my project, I aborted the batch-file as fast as I could
and began to thing about what happend actually.
After some investigation i found a bin-folder in
c:\windows\ containing lot's of dlls... So what I think is
that the bat-file was actually runned in
c:\windows\system32\ and not in the folder from which i
double-clicked it. I'm very very happy that i aborted the
batch-file since otherwise the "del *.dll" would have
runned.
This "bug"? doues only occur the first time, when i run
the bat-file now it runs in the same folder as it is in.