Print Screen with MacBook keyboard in Boot Camp Windows

-

First off, Happy New Year to you!  I hope you had a great Christmas.

My day to day laptop is a white Apple MacBook which runs Snow Leopard and Windows 7 Ultimate using Boot Camp.  This is fab as it enables me to go out to both Mac and PC customers and bring just one laptop.  However, I’ve often needed to take a screen grab when in Windows mode and couldn’t figure out the keyboard shortcut, here it is:

fn + shift + F11

For the full list of these shortcut follow the link below, it’s for MacBook Pros but gives a good idea…

http://support.apple.com/kb/HT1220

Note: If you have a USB PC keyboard connected the PrtScr button should work fine.

Comments

Anonymous said…
Thank you. It was very useful.
20 June 2012 at 17:56
Post a Comment

Popular posts from this blog

Where are SCANPST.EXE and/or SCANOST.EXE?

-
Image
I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted.  Very often the fix is to run SCANPST.EXE on the offending PST/OST file.   However, every time I go to do this I forget where the two executable files are.  Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.
Read more

APC PowerChute Network Shutdown - Authentication Phrase

-
Image
​Was installing  APC PowerChute Network Shutdown (PCNS) on a customer’s server and couldn’t find a record of the Authentication Passphrase that I set ages back on their Smart UPSes Network Management 2 Card. So I went to reset it on the card and start anew… it took a lot of digging to find it on their particular release of firmware: Go into the UPS tab, then into “shutdown” inside the “Configuration” category: You may then need to change the passphrase being used on other servers. To do this, open up PCNS in your browser and click into the area shown below:
Read more

WSUS Issues

-
Image
Was configuring WSUS on a Server 2016 VM for a customer recently and found the performance to be very sluggish and most of the time the client PCs would time-out and throw an error message when trying to check for updates. After much digging on different forums I came across a fix that worked nicely: Open Internet Information Services (IIS) Manager and click on Application Pools Then Right-Click on your WsusPool instance and choose Advanced Settings Scroll down to Private Memory Limit (KB) and change it from the default of 1843200 to 0 which means unlimited. Then right-click and stop the WsusPool and then start it again. Hope this works for you.
Read more