After dismissing the nag screen once again, I decided that I would upgrade my Parallels installation to version 6.
I generally don’t have problems with Parallels on my Mac, but thought that the performance improvements would be nice. I also want to try out the iPhone/iPad App and see if that would allow me to access a Java application that I need to use for work.
It was pretty easy to set up, requiring a login of my Parallels account on both the Mac and the iPad. And though Windows 7 is not designed for a touch interface, at least if needed I can access Windows through my iPad!
The key test will be over wifi outside my home network and over 3G. In the olden days in my previous job, I would VPN into my office network and use Microsoft Remote Desktop Connection to connect to my office PC when I was out on the road with my (then) PowerBook. Use to do that to find old e-mails and files. Also used the VPN so I could watch BBC News on the website when I was on a trip to Finland.
Now I have a fast broadband connection at home I hope that I will find less latency problems that I had with the VPN and RDC method.
One side effect of the installation was finding out the number of virtual machines on my iMac. More than I thought I had, so a fair few were culled.
Will use it a little more and see what improvements there are with version 6.
Now printing documents from Parallels should be a simple affair. The Windows VM should just print and go…
Parallels installs the following printer…
Which then should be delivered to the printer attached to the Mac, which in my case is a Canon MP600r.
The print job does read the Canon print queue… However the Mac decides to HOLD the print job and when you try and RESUME it, I get the following error.
The error says:
pstopdffilter/pstocupsraster failed with err number -31000
Now at this time I have no idea how to resolve this, except to either print direct from the VM to the Canon (as the Canon is wireless and on the network) or to use one of my printer sharing tricks.
Would be nice to know what’s causing the problem though and initial searches through Google don’t seem to resolve it.
The more I use Parallels the more I prefer it over rebooting into Boot Camp. From a speed perspective I know that Boot Camp has to be “faster” however for most things I do on Windows, virtualization is usually sufficient.
I am sure that part of this is that my new 27″ iMac with 8GB of RAM is now fast enough to support what I do in OS X and run Parallels at the same time. With my older iMac I would normally run Parallels, but would avoid doing too much else on OS X as it would be rather slow. The new iMac is so much more powerful and faster.
I am in the main using Windows 7, though now and again I do boot into Windows XP.
If you are using Boot Camp, I would recommend you give Parallels a go.
Do you use Parallels (or other VM software)?
Do you prefer “hiding” Windows in a window, or do you hide Windows by integrating with OS X and use Coherence Mode?
In this mode the virtual machine’s desktop is invisible so that you can see the virtual machine’s application windows in Mac OS X and work with them side by side with your Mac OS X applications.
Personally I do not like Coherence Mode and will either use Windows in a Window or in Full Screen Mode.
How do you use Windows on a Mac?
On my home iMac I run a variety of flavours of Windows through Parallels. In the main to test Windows software and to access some sites which only really work on IE.
Over the last few months I have been running in the main Windows 7 or Windows Vista.
A couple of days ago I started the Windows XP VM on Parallels and started getting a WMI crashing error.
A Google search brought up this solution however despite trying this (including deleting the relevant files from Parallels Explorer.
It was suggested to me that it might be a virus, but even my AV software then started to crash.
The only solution was to delete the VM and create a new VM and install Windows XP all over again. Not a quick solution as there are quite a few updates to install like SP3.
Seems to be working now.