On Mon, Oct 19, 2009 at 16:51, Ben Scott <[email protected]> wrote: > On Mon, Oct 19, 2009 at 7:38 PM, Matthew W. Ross > <[email protected]> wrote: >> But do you need to quote the device? Since you didn't, did you reset >> _ALL_OF_THEM_? Sm:)e > > And we have a winner! :-) > > The command I issued: > > DEVCON restart PCI\VEN_8086&DEV_27CC > > contains an ampersand (&). At the NT command prompt, an ampersand is > a separator for running multiple commands, in series. So the above > gets parsed as two commands: > > DEVCON restart PCI\VEN_8086 > > DEV_27CC > > The second command isn't a valid command, but it never got that far. > The first command attempts to restart every PCI device in the system > with a vendor ID of 8086. > > PCI Vendor ID 8086 is Intel Corporation. > > On this PC, Intel makes the controllers for main memory, DMA, SATA, > PATA, PCI, PCI Express, USB, Ethernet, LPC bus, SM bus... > > I had to do a 120-reset to get the system usable again. > > Moral being: *Watch those shell meta-characters*. CMD.EXE might not > be /bin/sh, but it ain't COMMAND.COM either! :-) > > For the record, the proper command would have been: > > DEVCON restart "PCI\VEN_8086&DEV_27CC" > > -- Ben
Ewwww... A single backtick as a delimiter? I don't think I've run into devcon before - I'm glad you've done my experimentation for me, though. Heh. Kurt ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
