B
Bonno Bloksma
Guest
Hi,
A few months ago I installed the Windows 2003 resource kit tools on my
server. At first I did not see any adverse effect but today I found out it
did do one thing, very sneaky. ;-(
I use the unix sleep command in several of my batchfiles to space commands
in time. The original syntax for the sleep command is:
"sleep <n>" where n is the number of seconds
For at least a very long time, many years at least, the following syntax has
also been valid
sleep <n>s (to indicate n seconds)
sleep <n>m (to indicate n minutes)
sleep <n>h (to indicate n hours)
and even
sleep <n>d (to indicate n days)
Unfortunatly the sleep command in the resource kit does not know this syntax
*AND* being a Microsoft program it claims to be the most important
program(s) and installs itself at the beginning of the Path variable. It
therefore overruled the default sleep command with a version that does not
comply to the long standing syntax of the sleep command. :-(
In case someone else is bitten by this, at least now you know the cause.
Where does one suggest a change in syntax for a program in the Resource kit
tools?
Where does one make suggestions for MS programs at all? The only places I've
been able to find is in existing beta programs where members can suggest
something.
Bonno Bloksma
Netherlands
A few months ago I installed the Windows 2003 resource kit tools on my
server. At first I did not see any adverse effect but today I found out it
did do one thing, very sneaky. ;-(
I use the unix sleep command in several of my batchfiles to space commands
in time. The original syntax for the sleep command is:
"sleep <n>" where n is the number of seconds
For at least a very long time, many years at least, the following syntax has
also been valid
sleep <n>s (to indicate n seconds)
sleep <n>m (to indicate n minutes)
sleep <n>h (to indicate n hours)
and even
sleep <n>d (to indicate n days)
Unfortunatly the sleep command in the resource kit does not know this syntax
*AND* being a Microsoft program it claims to be the most important
program(s) and installs itself at the beginning of the Path variable. It
therefore overruled the default sleep command with a version that does not
comply to the long standing syntax of the sleep command. :-(
In case someone else is bitten by this, at least now you know the cause.
Where does one suggest a change in syntax for a program in the Resource kit
tools?
Where does one make suggestions for MS programs at all? The only places I've
been able to find is in existing beta programs where members can suggest
something.
Bonno Bloksma
Netherlands