Hello all, I was able to reproduce this bug on the first try. However, the machine did not reboot until after the ping had finished. (I did a ping -t). In addition, it seems to work with most programs that trap keyboard input. I tested it with traceroute (again, it worked only after the program exited), ping, dir /s /a, and all had the same result; as soon as the program exited, it would be run again, and then reboot. In general, the output looks like this: C:\> tracert yahoo.com <program output> <program output> <program output> <program output> C:\> C:\> C:\> C:\> C:\> C:\> C:\> tracert yahoo.com (reset occurs) It appears to be the result of windows trapping the input and feeding it to the command interpreter (cmd.exe) all at once. F7 displays a list of the most recent commands, so it appears that windows is trying to run several copies of an identical command simultaneously and that's making it very unhappy. Surprising that we don't at least get a BSOD. Cheers, Kevin Thayer Network Operations Engineer PayPal Network Operations > -----Original Message----- > > Hello, this is a new bug found in W2K in all flavors, works > with all levels > of users. > > Here is the proof of concept: > > Open a Cmd Window > Ping to any host (for example ping 10.100.2.1 preferred a > host in your LAN), > no switch needed. Just ping > Now press F7 and Enter (try a couple of times quickly...less > than ten , and > you can see what a meaning) > The machine reboots, from nothing a warm reboot. > Please let me know if you have the same bug. I tried this in > W2k sp2 English > and Spanish. >
This archive was generated by hypermail 2b30 : Sat Jul 28 2001 - 20:14:41 PDT