This page has reader reports on using the free "Q" emulator to run Windows on Macs.
Note: the latest version as of July 2006 is 0.8.1a35 (new network card support and some bug fixes) but check the Q homepage for updates in the future.

Reader Reports on Q: (most recent first) I welcome other reports on using "Q" to run Windows, Linux, OS/2, etc. on Macs (performance, compatibility notes, etc.). let me know what Mac and OS you're using.

Guide to installing Q

(3/21/2006)
" Thought this might be of interest to folks - I managed to get Windows XP to install and run (reasonably snappily, too) on my Intel iMac:
http://www.beatnikpad.com/archives/2006/03/20/windows-mac-q
-Neil "

NOTE: Apple has now released their own utility/bootloader for running Windows XP (SP2) on Intel CPU Macs called BootCamp. See the BootCamp User Reports/Tips page here for tips, links and feedback.)

Running OS 2/Warp with free Q emulator, Another Win98/NT4 report (from 3/1/2006 news page)

" Thought I would drop a line and let you know I got Q (free "Q" emulator) to do something I couldn't with VirtualPC7: I now have an IBM OS/2 Warp Ver 4 system running on my PowerMac 1.6 Ghz machine.
Had to use VPC to make the bootdisks images, but the install went smoother than the Win98se install - no system hangs during or after the install reboots.
Can only get VGA though, more than 16 colors would be nice.
-Darrell F. "

(from Feb. 25th mail)
"I was bored tonight and decided to check out Q. My OS of choice with VPC has been NT 4 for a long time; I simply haven't found a faster, more stable version of Windows to run in virtualization, and most modern programs generally work with it. I converted the disk image and it booted up, but then NT 4 kernel paniced at the initial blue start up screen (after it detects the CPU type, etc.) I'm not using a compressed disk image.

I tried Win98SE after that, which booted up with no problem. It did seem a little slower than VPC, but honestly -- if given the option of paying for VPC and just using Q, I'd probably go with the latter -- especially since I can go months without needing to boot into Windows.

It looks like a promising project, though there are definitely some rough edges. My VPC XP disk image is of SP2, so I didn't bother trying that. I'm using a Quicksilver with a 1.4ghz CPU, Sonnet (FirmTek) SATA adapter, and 1gb RAM.
-Haroon "

More info on removing VirtualPC extensions from VPC images Several readers asked for more information on a Q user's earlier comment on removing VPC extensions from his windows disk image. I wrote him to ask he send more details:

" ... There is an "Install or update additions" command in the VPC "PC" menu. If additions are installed doing this command on a running (in VPC) VPC image will remove them. If they are not installed, it will install them. You can tell when "additions" are not installed because without them the mouse cursor will not move out of the VPC window until you press the "apple" key.

What I did was to open the VPC image (I used a copy of one) I wanted to import into Q, removed the additions, turned it off without saving and imported it into Q.

I might mention that my Win98se image was a "dynamically expanding" type so they work. (But I wonder if this feature was disabled after removing VPC extensions. And previous posts said compressed images were not recommended.-Mike)

Also, when my Win98se image opened in Q, it had to correct the video resolution which means it needed a Win98se CD which, luckily, I had on my image (on C:). It would probably be a pain to get one that Q could see/use if it were not in the image already.

Also, the above procedure did not work for my WinXP image. It still failed to boot. giving the message "missing or corrupt biosinfo.inf". If I want to see XP on Q, I will probably have to do a clean XP install as an XP boot CD repair did not fix the image either.
-Al P. "

Unfortunately nothing seems to be a universal fix for everyone trying to use VPC windows installs with Q however. (Several mails noted problems trying to use them although some were successful - most often it seems with Win9x.)

A tip on removing VirtualPC extensions that a reader said helped with this Win98SE VPC disk:

" Q worked for me with an imported Win98se VirtualPC7 image. However, I did have to remove the VPC extensions from the image and shutdown (when opened in VP7) the PC without "saving". (I asked him for more details on removing the extensions - see his later reply above.-Mike) The same image with extensions and "saved" would not boot up after importing into Q, crashing with a message that a device driver is corrupted.
(I'd forgotten about that VPC shutdown 'feature'. it also caused problems with VPC updates in the past.-Mike)

I might add that the Q image ran about 75 - 95% as fast as when in VPC7 on my iMac G4. Also I am running 10.4.5.

My XPsp2 image also crashed with a driver problem. I will let you know if it works after removing extensions and a complete 'non-saved" shutdown in VP7. (his later post above noted it didn't solve the problem.)
-Al P.
Baton Rouge "

If anyone else finds this tip helps with their Q/VPC disk problems, let me know.

" My experience parallels that reported by Kevan (yesterday - noted "inaccessable boot device" error).
I've repeatedly attempted to run XP Home on Q by importing a VPC7 Windows XP Home "guest". During the conversion process there is a rather long delay with a progress bar showing "Windows XP Home Converting Harddisk_0.vhd". When the conversion is finally completed, attempts at starting up XP result in the message: "Invalid boot .INI file." Then there is the message, "Windows cannot start because the following file is missing or corrupt: <Windows root> \system32\hal.dll"

I will retry after converting my VPC7 image from expanding to fixed size. (Q notes say not to use compressed images)
-John "

I also wrote John about the reader tips above (removing VPC extensions, etc.).

Although a lot of recent reports have mentioned problems (with VPC images typically) - here's another report on success with an older version of Windows:

" Hi Mike, First up: I've been a long time reader of your site, ever since I've gotten my first Mac (Performa 6200 in 1998). Your site and infos has helped me much during the years with various Mac's and peripherals.

I've been trying "Q" yesterday nite on my 12" iBook G4 1,33 GHZ/1GB RAM with 10.4.5. Using Q was easy as 1-2-3. :-)
I downloaded a DOS-floopy-Boot image with CD-Rom-Driver (.img) from bootdisk.com.
After unzipping Q could already boot from the .img floppy bott image (I didn't even had to convert it to a .iso). I placed my old Win95 Install CD in my iBook. Fdisk'ed and formated the c:, rebooted. "Q" was instantly able to use the pysical-cd (didn't have to create a image from the cd first, like other readers from your site), so that was very convinient.

Win95-Install took about 30 Minutes. So I have to say I am very happy with "Q". Performance is good on the iBook with Win95.

I also configured the virtual network card (ne2000-compatible) under Win95 as described in the help manual of "Q" and installed the "Q-network".exe. So than I could even access the files in my mac as a networked/mapped-Drive in Win95.

It is a very good solution with no hastle at all (at least for me). So I am very pleased with Q, as far as performance, installation and of course price and avoiding a "Virtual PC".
Cheers from Berlin, Germany...
-Christian "

" I downloaded Q to give it a go so I could add my comments on the subject. However, I only did this as I already have XP and 200 VPC7 images. I went through the installation of XP from CD with another Emulator and it made me suicidal. Q imported these images, which I know to be fully up to date, virus etc free and running perfectly, but both imported images result in errors during booting from Q.
XP barely begins to boot before the screen goes black, the window resizes and the process starts again. 2000 progresses a bit further and gives up a bit more info when it goes to the blue crash screen. I suppose it is entirely possible that the error given by 2000 is what is affecting XP. The error is along the lines of... "INACCESSIBLE_BOOT DEVICE"

The only thing maybe slightly unusual about my setup is that I boot from a RAID 0 array consisting of 2 internal 250GB SATA HD's. My Mac spec is as follows; Dual 2.5Ghz G5, 2.5GB RAM, 500GB RAID 0, Airport Extreme and Bluetooth, ATI 9800XT, 16X DVDRW OS X 10.4.5.

As I already run VPC 7 I would really like to do a comparison. Would love any suggestions that might solve this issue. Thanks.
Kevan G., Fix My Mac "

I'd check with the author of Q but if any reader has a suggestion for Kevan let me know. BTW - one of the earlier reports here (but didn't note using images from VPC or RAID ) mentioned :

" ... I had Win2k installed after a few steps. The only requirement was using a not compressed disk and enabling --win2k-hack parameter under advanced virtual PC options. Everthing else is quite easy.... "

Update - several readers replied to Kevan's post (above), including a note in the Q FAQ:

" If you look at the FAQ for Q on the web http://qemu.dad-answers.com/viewtopic.php?t=801, you'll find that this problem is known, and does indeed have to do with not having the right drivers.
They suggest that a *possible* fix is to convert the VPC disk image from expanding to fixed size (using VPC's "Virtual Disk Assistant"). Well, I tried doing this, but unfortunately it is only a "possible" solution, and at least for me, it didn't help. I still get the "inaccessible disk" error at startup.
The FAQ also mentions that fresh installs of Windows will work, so basically it sounds like you have to have a Windows install CD to get Windows running on Q. Anyone know of a cheap source for (legal) Window 2000 install CD's?
-Steve "

The cheapest Windows (legit) CDs usually are the "OEM" ones, although most dealers require you to also buy something like a motherboard to qualify for them.
(BTW - See Friday's news for a later note from a reader on removing the VPC Extensions which he said helped with a converted Win98SE image.)

" I have seen that "INACCESSIBLE_BOOT DEVICE" error in win2k, in legitimate installs on real PC's after moving the hard drive to a new/ different controller, with out installing a driver for it, into windows. (i.e. moving from an Intel ATA controller to a Promise Controller)
-Bryan B. "

" I recognize the (inaccessible boot device) error. I've seen it happen on Win2000 installations that are moved from one motherboard to another. What it's really saying is that the Windows Hard drive controller driver is not applicable to the hardware it's trying to run on (and hence, it can't find the hard drive). I can imagine that the different emulators emulate a different hard drive controller, so he's running into an analogous problem.

There is a procedure (registry edit, file removal) out there on the net that describes what you have to do on a Win2000 installation before you move it from one motherboard (hard drive controller chipset) to another. I can't go digging for it right now, but it should be relatively easy to find.
-Chase T. "

" I too have the same problem as Kevan. I have been so far unsuccessful using Q. I tried importing my XP and 2000 VPC7 images and have the same error. It never makes it through the startup sequence and is stuck in everlasting restart mode.

As well, I have not been able to get either to install from CD. XP fails authentication check and 2000 gets stuck in a restart cycle. I tried both with and without the -win200 hack parameter.
-Chris "

I asked Chris if he'd previously installed from the same CD (My last homebrew PC system install of XP required getting another code from them after upgrading the video card, adding more ram and then just moving a wireless PCI card to a different PCI slot - same card, but a different IRQ used. I had to call MS and get another (very very long) code to enter.)

" I have the exact same issue after converting VP7 Win2K disk images.
I converted one on a G4 1.6ghz laptop, and on a dual 2gz G5.
I tried both the current Q, and the experimental Q. I used the --win2k_hack option on the experimental Q. I was able to convert a win98 VP7 image and use it, but not Win2K.
Maybe if you started from scratch it would work, but the conversion doesn't.
Thanks, Ben "

" Heya. I've loaded Q and played around with it a bit. Here is my system specs:
Dual 800 G4 Quicksilver, 1.25 Gb RAM
OS X 10.3

I'd say it runs about as fast as Win98 did when it first came out. It boots up in under a minute, and the menus are usually fairly responsive. Playing Heretic (an old 3-D FPS) is painful, though. VPC 5 definitely has the edge as far as that goes. The SB16 produces really distorted sound, probably a half-octave lower and twice as long as the original sound; the other sound cards don't work. The Cirrus VGA emulation works fine.

It took about 1.5 hours to install, which isn't bad.
I installed it by creating an ISO disk image (Disk Utility -> Damage Isolation) of a Win98 boot CD, and using an ISO boot floppy image from the Net somewhere. To load other CDs into the running Win98 system, I just created ISO disk images of them, too. It took me a bit of playing around to figure that out, but once I did, no problem.
If they could increase the speed 10-20%, they would kill VPC dead, at least on older G4s, in my opinion. Great site!
-Mike T. "

" I tried installing Windows 2000 using Q on a 12" Powerbook G4 1.33Ghz, and it seemed to go pretty well up until the point where I had to enter registration information. The keyboard mapping got all screwed up, so I would hit the "q" key and it would type a "/" and other such nonsense. I wasn't able to enter my name or my registration key because of this, so I aborted the mission.
The only anomaly in my process was that I had to suspend the virtual machine once during install because it was taking so long. I brought it back up and it continued on accessing the CD and installing with no complaint. However, perhaps I activated some weirdness by doing this.
-Mark E. "

Update - reader replied to Mark's post:

" To Mark E
The problem with the keyboard is most probably that it was recognized as a french AZERTY keyboard instead of a QWERTY US keeyboard.
Then the mapping is changed.
You have:
a instead of q, z instead of w, m instead of ;
-Patrick D. "

" I'm using Q.app to run Windows XP. My experience is that it works about as well as Virtual PC as far as compatibility, but is a little clumsier (for example, you have to manually mount CDs) and quite a bit slower.
PowerMac G5 Quad, 2.5 GB RAM, Windows XP Pro, Mac OS X 10.4.5.
(he later wrote)
I wrote to you yesterday about running Q.app on my PowerMac G5 Quad. I reported that Q was much slower than VPC but seemed to have similar compatibility.
Just after sending that email, I spent some more time with Q.
Unfortunately, I hit a major bug. I was running Windows XP Pro and tried to install SP2 from the Microsoft update CD. The system took over an hour to unpack everything, write the files, save the backups, etc, and then gave an error message saying that it couldn't finish. VPC 7.0.1 had no problems with installing SP2.
I'll stick with VPC at least until Q goes through another revision or two.
Regards, Joe R. "

" PowerBook G4 Ti 667 MHz 1 GB RAM OSX 10.4.5
Running "Q" as a 128 MB x86 PC with Windows95.
Took me a little while to get this going as I didn't have an already "working" VPC disk image. So had to do it from scratch.

It was a little "chicken and egg" scenario ... I couldn't access the CD until I'd loaded Windows, and I couldn't install Windows until I could access the CD ...

In the end I used "Winimage" on a PC to generate a 1.44 MB Win95 boot floppy image. Onto that I loaded "cdgod" software so I could choose the "generic ATAPI" CD driver after booting from the floppy. That allowed me to then load a CD image of the Windows95 CD, and install onto a suitably formatted hard disk image.

As described in the Q documentation, Windows95 doesn't discover the network card or soundcard. But the documented installation does work. I found that Win95 on its reboot after install tried unsuccessfully to load the Cirrus drivers for the video ... probably because it tried to do it prior to the CD driver being loaded. After cancelling the "Find file" dialogues, it carried on booting fine, then I could tell it manually (right click on desktop, Properties etc etc) to go find the drivers from the now available CD.

Things I haven't sussed yet ...

1. Having booted into Windows95, I can't now access the A: drive ... even booting with a floppy image loaded, it refuses to acknowledge it's there.

2. Similar to #1 I can't access a physical CD ... Q is set to "use Real CDROM" which I thought means that it will see the Mac's CDROM drive, but it doesn't. It does though see my Win95 CD image as E: when told to load that in the Q setup. So maybe I have to image any CD I want to use.

3. Can't access the "Q Shared Files" apparently intended for the Q: drive. I see a brief error message flash up and immediately disappear in a DOS window when running the Q.bat script. No chance to read what it says though.
-Mark "

I welcome other reports on using "Q" to run Windows on Macs (performance, compatibility notes, etc.). let me know what Mac and OS you're using.

" (Q) It works pretty nice! However developer is still waiting for his MacBook Pro and new versions are not released as fast as they should since he has to test using VNC access.

I had Win2k installed after a few steps. The only requirement was using a not compressed disk and enabling --win2k-hack parameter under advanced virtual PC options. Everthing else is quite easy.

I purchased WinTel 2.0.1 and ran awfully since it was basically Bochs running under Rosetta .... when I asked for a refund they refused it. More about it at http://qemu.dad-answers.com/viewtopic.php?t=847
Best regards, George "

"... I'm not running it on an Intel CPU yet, but I have been following Project Q for a few months and running Windows XP on it on my old G4. It performs better than I expected it to and is a great free alternative to VirtualPC.
Q was very easy to setup compared to Bochs. About the same as VirtualPC.
-Keith C. "

" Mike, I also tried Q (the public, free one) on my dual G5 after seeing it mentioned on your site.
I managed to import a VPC7 virtual PC with Windows ME into it, but I got an error message about the graphics display not being configured properly (an emulated Cirrus Logic in Q) so it only ran at VGA mode, 16 color. I tried reconfiguring it into the generic SVGA display but got the same error. Aside from this problem, it seemed quite fast compared to VPC. Maybe a fresh Win ME install would help with the display problem.

Next, I tried a fresh install of Win XP into a fresh (compressed) disk image. It installed fine (but slow), but upon the final reboot, it hung on the Win XP loading screen. I'll try later the non-compressed disk image trick that the other guy mentioned on your site. (see report above)

The real purpose of my writing is to mention that the Q developer noted on his web site that virtualization (a separate module) is not there yet in the universal binary. So on a Mac Intel, it is still emulating a PC within a PC (although apparently faster than on a G5). Once the virtualization module is working (fingers crossed), it should run WinXP at almost native speed on a Mac Intel, similar to Vmware on Linux/x86 running WinXP.

There is also a petition on slashdot or somewhere to get Vmware ported to Mac OS X Intel (Darwin Intel using X11 would do).

Microsoft's (Connectix's) VPC for Windows (host) is a virtualization layer, not an emulator. So it is also well within their capabilities to port a VPC for Mac Intel virtualization engine.
Thanks. - Paul "

" I just wanted to report a big problem with "Q" on a PoweBook G4 Titanium 1 GHz and a PowerMac G5 DualCore 2.0 GHz, both running Tiger 10.4.5 and with at least 1 GB RAM each: "Create PC" does nothing but close the window. No new PC, nothing !
(he later wrote)
I found the cause to my problem with Q not working on my two Macs:
Q doesn't follow the alias I have for my Documents folder, it requires a real Documents folder in the user's home folder to put its QEMU folder in !
Is it really that difficult to correctly use the file system API ?
Regards, A. Frank "

I welcome other reports on using "Q" to run Windows on Macs (performance, compatibility notes, etc.). let me know what Mac and OS you're using.
(BTW - Another reader with a bad experience with WinTel sent a note that before buying it, you should read the user reports at VT on Wintel (and OpenOSX Office) and MU also has a page on WinTel with user ratings. There's also a old page here from 2001 (last updated in 2003) with WinTel/Boch X86 Emulator Feedback but it's not been updated since 2003. This also reminded me of a very old page here from 1999 with feedback on the first "Blue Label" emulator. And many feel it's also not kosher to charge for products that use open source software.)