Hi Guys. First i do NOT have a bootcamp as I had always thought that I would not need a Bootcamp partition as long as I do not need to boot into windows directly (the real boot). As I always boot into Mac OS, and when i need some windows app, I use VMware 3. I installed a Windows XP with it, and all the win software I needed. And I have also been look into WINE. Since I heard WINE could be a more efficient app to run windows softwares. But I still haven't totally figured how to play with it. So I was watching some youtube clips demonstrating how to use WINE and other virtual machines for running windows apps on mac. And I noticed those guys all had a Bootcamp partition installed a Windows. And they run their windows app from the bootcamp. And even VMware Fushion 3 detects if you have a bootcamp partition too. There was a video showing how to use Wine/Winebottler to run the CPU-Z for windows, but his files was on a Bootcamp windows. The CPU-Z was working perfect as it is natively from a windows box. But when I do it with Winebottler the CPU-Z window could show but most hardware information was not shown (left in blank -- I tried to read the SPD info of my RAMs) . Here, the only difference is i run the Wine from Mac's own filesystem and there was no Bootcamp. So i am wondering if the problem was i did not have a boot camp? So the questions: 1. what's the merit of having a bootcamp with an actual windows installation comparing to pure virtual machine install on Mac, given the premise that i will only boot into Mac and use WIndows apps only from a virtual machine from Mac OS -- consider I use VMware Fusion 3 and WINE? 2. For VMware Fusion 3, what's the difference between (i) use a windows installed on a bootcamp (ii) a Windows installed to VWware ? 3. For windows apps like CPU-Z that needs low level hardware access (like reading your CPU info and your RAM chip manufacturer information), does a boot camp windows does any good?