At work I have dual monitors but with my docking station can also use my laptop as a 3rd monitor which is great. The thing that always annoyed me was my laptop was my third monitor and was located all the way to the right, so to get to it I had to mouse all the way to the right. A minor annoyance for the convenience of having 3 monitors. I mentioned something to someone about this the other day and they asked why I didn’t position my laptop monitor as below the dual monitors and I said “I would if I could”. Then I opened up the monitor control panel and tried to drag the monitor below and lo and behold it worked! I’m not sure why I never thought of this before as it seems so obvious now.
This would also work if you have one external monitor positioned directly above your laptop. Rather than scrolling to the right to get to the 2nd screen you can scroll verticallywhich is a lot more intuitive. This works with the Intel Control Panel and also with the GeForce Experience Control Panel.
One of internet users biggest annoyances has been resolved in Chrome 33. When a tab starts playing audio Google Chrome version 33 adds a speaker icon to the tab.
From all the testing I did, the speaker icon is the last thing to disappear when you have a bunch of tabs and it works whether you have multiple tabs with audio, if the audio is paused and isn’t dependent on your system sound be
ing turned on.
At work we have a lot of computers/servers that need to be remotely managed. If a computer has frozen for some reason, PS Tools is a great program to help determine what the issue is and if necessary remotely reboot the computer. There are 12 different programs that come with PS Tools, but pslist and pskill are the two used most frequently.
All PS Tools programs are ran via the command line. I unzipped all the programs to c:\pstools, so I can use
cd c:\pstools in the command prompt to get to my directory from there you can type pslist to get a list of all running processes on a computer.
pslist \\mattbusche is the command to find all running processes on my computer
Normally if a rogue process is the problem with the computer it will have an extremely high CPU time. Idle and system will always have high times, so those can always be ignored. To kill a process you need the pid from the pslist command. You will need to reference the computer in this command as well
pskill \\mattbusche -t 344
That command would terminate pid 344 smss. If the offending process isn’t something you’ve heard of, you probably shouldn’t just go and kill it. We have a ton of VB programs, so those are fairly easy to identify (i.e. pre-trip approval, email reader, etc)
If for some reason the process cannot be killed then you will need to use psshutdown which I will cover in a later post.