Apple Keyboard Layout for Windows XP/ Vista / 7 & 8

Thank you to http://parkernet.com for originally posting this I have added post below as a point of reference…

Compatible with all Apple aluminium and Apple Pro Keyboards

Now available – XP 32-bit and 64-bit, Vista 32-bit and 64-bit, Win7 32-bit and 64-bit compatible.

Do you use the UK Apple Pro Keyboard or the aluminium Apple Keyboards with Windows XP, Windows Vista or Windows 7?

Are you severely annoyed because none of the supplied keyboard layouts in Windows XP, Vista or Windows 7 match up with the key legends on the keyboard, even when you use the US English or US Extended English layouts?

I was, so I decided to remedy the situation so I could use the keyboard without getting # instead of £ or @ instead of ” whenever I was working on a document or email or anything at all.

So after extensive research I discovered the best thing to do was create a specific keyboard layout for myself, as far as I can tell no one has created one before – which I find strange.

So here it is, and it’s free of charge for home or commercial use. But if you find it useful, you are welcome to make a small donation as a token of gratitude via PayPal. Click here to make a donation.

Download

Download the installation package Apple_Pro_KBD_v2.zip

System requirements

Windows XP, Windows Vista, Windows 7, 32-bit or 64-bit versions. Apple Pro Keyboard or aluminium Apple Keyboards. Untested with wireless keyboards but it should work okay.

Installation

After unZipping the Apple_Pro_KBD_v2.zip file, open the Apple Pro KBD v2 directory and run the Setup.exe installation file.

The installer will run and automatically install the keyboard layout .dll file into the correct location for your operating system.

To remove the keyboard layout simply run the installer again.

Configuration

Use the Windows XP Regional and Language Options control panel to select the new keyboard layout. Full details are included in the read me text file included in the ZIP download.

For those of you who want a step-by-step guide with pictures that you can print out, click here.

Sorry there’s no Vista or Windows 7 step by step but it’s pretty much the same process.

Keystrokes

All keys now operate as per the legends printed upon them.

Shift-2 = @

Ctrl-Alt-2 = €

Shift-3 = £

Ctrl-Alt-3 = #

READ ME – Update
The link to the zip file has become broken please download from downloads.cnet.com 
(Word of warning: cnet tries to trick you into installing other software, toolbars and change your home page, when the dialog box opens read the instructions carefully as you can choose to not install the extra rubbish.) At some point I will try and host the zip file somewhere but don’t have time just yet. Hope this helped.

Advertisements

Getting into it…

So I have started looking at trying…yes the operative word is “trying” to learn Objective C so that I can start building my own iPhone apps…yeah I know what you are saying. Your a bit late, people rode that wave in yonks ago.

I know…but it’s never too late…and boy has it been a challenge. But that’s what it’s all about. I just need to persevere! Anyway this was always going to be a short one. I am tired and have geek eye. So need to shut them down!

Permanently delete ‘Work Items’ from TFS 2008 / 2010

To delete or destroy a ‘Work Item’, you will need TFS 2008/2010 and you will need the relevant version of Microsoft Team Foundation  Server 20^^ Power Tools; found here.

The command is:

destroywi – You can use this to delete or destroy one or multiple work items.

In TFS 2008:

In the command prompt locate the 2008 Power Tools location should be similar to this:

C:\Program Files\Microsoft Team Foundation Server 2008 Power Tools>

or

C:\Program Files (x86)\Microsoft Team Foundation Server 2008 Power Tools>

From here, you will need to use the tfpt command with destroywi command. To get all options for these comands use: tfpt destroywi /?

i.e. C:\Program Files\Microsoft Team Foundation Server 2008 Power Tools>tfpt destroywi /?

Once work items have been destroyed they are physically deleted and cannot be restored (all traces).

Options:

/server (TFS Server and is required)
/workitemid (ID’s of work items to destroy and is also required)
/noprompt (Optional, if specified user is not prompted to confirm destroying the work item)

Use example:

C:\Program Files\Microsoft Team Foundation…>tfpt destroywi /server:tfsservername /workitemid:value1[,value2…] [/noprompt]

In TFS 2010:

Similar but obviously uses 2010 power tools. Uses command witadmin destroywi /?

Options:

/collection (Specifies the Team Foundation project collection and is required. Use fully specified URL such as http://servername:8080/tfs/Collection0)
/id (Specifies the ID of the work item to destroy and is required. Supports multiple IDs delimited by commas such as 12,15,23 (with no whitespace).)
/noprompt (Optional, if specified user is not prompted to confirm destroying the work item)

Use Example

C:\Program Files\Microsoft Team Foundation…>witadmin destroywi /collection:collectionurl /id:id [/noprompt]

Deploying a Sharepoint 2010 .wsp file in Powershell

To deploy a .wsp file to a remote server

Create a folder in the root of your C:\ where your sharepoint 2010 farm is located, and call it what you like. [Sharepoint/Code…] You will then need to copy the .wsp file to that location.

Use the following commands in Sharepoint 2010’s Powershell

To add and deploy a solution, we use the following commands:

Add-SPSolution “C:\…\SharePointWebPart.wsp”
Install-SPSolution –Identity SharePointWebPart.wsp –WebApplication http://mywebapp –GACDeployment

If you would like to add the solution as sandboxed, you would use the Install-SPUserSolution command instead. To upgrade a solution, we specify which solution is to be updated and with which new solution file:

Update-SPSolution –Identity SharePointWebPart.wsp –LiteralPath “C:\…\SharePointWebPart.wsp” –GacDeployment

To retract and remove a solution, we use the following commands:

Uninstall-SPSolution –Identity SharePointWebPart.wsp –WebApplication http://mywebapp
Remove-SPSolution –Identity SharePointWebPart.wsp