Open up a second PowerShell, ps my way to a list of running processes, find the ID of the other PowerShell (which has less than a minute of CPU time, and no CPU usage) and kill the gonads off of it.Go to the "processes" tab of the task manager, and end the entire tree of proceses for that window.It asked for confirmation, and then did nothing. Bring up the task manager with Ctrl-Alt-Del, asking it to terminate the application.This caused no apparent change in the window, which is as immobile and present as ever. Close the powershell window by clicking on the top right red cross.Press "escape" (and, in a linux geek reflex, ^C) to retrieve control of the powershell.The computer is completely usable: I can minimize the powershell and go on with my work. Now, my powershell is just hanging there on the screen of my laptop, still not returning from the above query. That is, until my home server rebooted due to a power supply issue. This would copy my two MSDNAA Visual Studio 2005 Professional Edition disc images from my central server to the laptop, along with a zipped mount-ISO-as-drive utility. Yarlathothep\data\programs\dev C:\users\admin -recurse The first thing I did was to install the PowerShell from microsoft. I have recently received my new Windows Vista Laptop, with-at long last-a shader-supporting video card.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |