PDA

View Full Version : How to get your keyboard layout right


rptb1
Jul 3, 2007, 03:00 PM
There are many threads on the forum about keyboard layout problems under Windows within Parallels on a Mac. I have a simple requirement: I want my keyboard to produce (as near as possible) they symbols that are printed on the keyboard. I don't think that's asking much. I have a (US) Mac keyboard and I want to use it!

I have found a solution that might work for some of you: install the Boot Camp drivers for Windows in your VM even if you're not using Boot Camp! The Boot Camp drivers do something to make the keys come out right, and seem otherwise benign.

This probably only works for US keyboard layouts. The British layout is the same except that SHIFT-3 produces "#" instead of "£". (If you're a techie like me you'll already be using the US layout.)

Here's a step by step guide:

1. Download and install the Boot Camp Assistant from Apple.

2. Right-click on Boot Camp Assistant in the Utilities folder. Select "Show Package Contents". Open the "Resources" folder. You'll find a file called "DiskImage.dmg". This is the CD-ROM image that contains the drivers.

3. Snapshot your VM so you can back out if this goes wrong!

4. Drag "DiskImage.dmg" to the CD icon at the bottom of your Parallels window.

5. Follow the instructions in the Windows VM to install the drivers. Windows will complain that some of the software isn't signed by Microsoft. Well, it came from Apple.

6. Reboot Windows when prompted.

7. Enjoy being able to type backslash, backquote, etc. without getting confused.

Now, I think Parallels ought to provide a solution for this. I've read various arguments saying it's not their problem, but I think it is. Most Mac users want a backslash to come out when they press backslash.

Secondly, it would be useful to have a response from a Parallels techie about whether this procedure is likely to cause problems.

w7ox
Jul 7, 2007, 12:02 AM
I'm puzzled. Now using Parallels 3 and was using v. 2 before with WinXP Pro on a MacBook

The only keyboard workaround I've needed to use is SHIFT-CTRL-Click to get a right click from the MacBook keyboard. All the issues mentioned above have never existed for me.

Did I just luck out or are some Mac keyboards more of a problem?

Phil

Eru Ithildur
Jul 7, 2007, 12:14 PM
I think some installations have issues with the tools, we never had an issue on any of our computers.

john.
Jul 10, 2007, 06:42 PM
I have a major issue with the @ and the " depending on which app I am using these keys seem to swap and it is very confusing. I am in the UK but the keyboard is the standard MAC USA version with the nuemeric key pad to get the british pund symbol we have to select shift 3 to get £

IS this nromal or will this suggested fix resolve my problems ?

THX

John

Timharvey
Jul 11, 2007, 07:27 AM
I have a major issue with the @ and the " depending on which app I am using these keys seem to swap and it is very confusing. I am in the UK but the keyboard is the standard MAC USA version with the nuemeric key pad to get the british pund symbol we have to select shift 3 to get £

IS this nromal or will this suggested fix resolve my problems ?

THX

John
Hi All
Yes I am struggling. How do I get the @ to work or a quick workaround?

I just want to be able to use the @ on Vista using Office programmes.

TIA

vontech
Jul 15, 2007, 03:33 PM
Just use the DOUBLE QUOTE MARK key (two keys to the right of "L" on my keyboard.

Fun, huh?

rptb1
Sep 4, 2007, 10:38 AM
My main problem has always been the backslash key, which produces a '#' until I add the Boot Camp drivers. Similarly, '|' produces '~', '~' produces '¬', etc.

But I'm mainly writing to say that this approach no longer works! It worked with Boot Camp 1.1.2, but I recently tried it with Boot Camp 1.4 and was unable to mount the disk image. I tried converting the image and managed to mount it, but then the installer refused to run, complaining of an unspecified "problem". Apple have done something which prevents the installation under Parallels -- deliberately or not I cannot tell. I still have my Boot Camp 1.1.2 download and used that instead, but this workaround has kind of expired.

So the ball is back in Parallels' court.