I realized I never made it clear as to why I was doing this. It appears that on Windows 7 32 and 64 bit, you can run into scenarios where choice will never timeout even though it is supposed to.

The problem shows up when the window gets and loses focus when the prompt is showing on screen. Unfortunately, we run into it somewhat often due to scripts we use. Since we jump back and forth between windows it is possible to encounter this problem multiple times in a script run. I ran into once today and it has been encountered by other members of my team.

It appears that on Windows 7 32 and 64 bit, you can run into scenarios where choice will never timeout even though it is supposed to.

Hm. Can't reproduce that.

It's also pretty implausible that a sleep within a console application would in any way be affected by whether the console it is running in has focus or not.

But if your Perl script works for you; that's all that matters :0

---

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

What is interesting is that the problem does not appear to be a sleep at all but the actual Microsoft choice program.

The batch scripts don't use sleeps when calling choice since it handles all of that itself. The batch scripts just wait for return codes.

Either way, I have been able to make the code much more CPU efficient but I am running into some other problems with Win32 support of signals. It also helps in that it gives me more learning opportunities.