Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Parallels Beta Adds Boot Camp, Desktop

Posted by CmdrTaco on Sun Dec 03, 2006 12:08 PM
from the stuff-to-play-with dept.
Verunks writes "Parallels has released a new beta of its virtualization product for Mac OS X. This new release includes one major new feature, something Parallels calls Coherency: "Shows Windows applications as if they were Mac ones. Try it and enjoy best of both worlds truly at the same time. No more switching between Windows to Mac OS." Check out this Screenshot" More interesting to me is the Boot Camp support so you can have a single partition to run IE7 in Parallels to test compatibility of a website but reboot to play video games that need a little more juice.
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Incidentally... (Score:5, Insightful)

    by BluhDeBluh (805090) on Sunday December 03 2006, @12:11PM (#17089650)
    I've been wondering why a Linux distro doesn't do this automagically with WINE. It seems like such an obvious feature to implement, and would be great for people new to Linux or even those whose who don't know how to use it if it just ran as if native...
    • Re:Incidentally... (Score:5, Informative)

      by MustardMan (52102) on Sunday December 03 2006, @12:21PM (#17089728)
      Wine is not the same thing as parallels - parallels is a virtualization environment that runs the full windows xp operating system concurrently with mac os x. Wine is a from-scratch implementation of the windows API. There is a wine-derivative package for mac (crossover from codeweavers), so people can pick-and-choose the best solution for them.
    • Re:Incidentally... (Score:5, Informative)

      by AchiIIe (974900) on Sunday December 03 2006, @12:40PM (#17089894)
      This is a very early beta. Essentially the way they allow one to boot from the "Boot Camp" partition is by adding an extra field in the Boot.ini file and by creating a new hardware profile (mainly used on docked notebooks)

      The beta is far from complete, I just tried it on my boot camp partition and the mouse/keyboard were unresponsive. (Even after installing the given tools)

      Moreover each time you switch between parallels and boot camp Windows is deactivated Thus I have to go through the reactivation procedure each time !!! i've done this about three times already and I'm afraid it'll just stop allowing me to reactivate it (even though it's a legitimate license)
    • Re:Incidentally... (Score:4, Informative)

      by friedmud (512466) on Sunday December 03 2006, @01:21PM (#17090298) Homepage
      what do you mean?

      This is the default with Wine... and I believe it's also the way crossover office works. You have to go in and specify that you want a "desktop" to get one. Also... the window borders with wine are actually drawn using your window manager in linux... so you don't even get the ugly XP titlebar and stuff.

      So what "feature" is it that is missing from Wine that you see here?

      Friedmud
  • by Anonymous Coward on Sunday December 03 2006, @12:19PM (#17089714)
    The constant improvement that this product has seen in its short existence is astounding. When you consider that it costs only $80 and has no competition at this time, it almost seems like they're working too hard on it.

    If Parallels was publicly traded, I'd be buying up a lot of their stock. These features are too damned useful for Apple to not add to OS X at some point, and the best way would be for them to just whip out the checkbook and buy the company.
  • by waldoj (8229) <<waldo> <at> <jaquith.org>> on Sunday December 03 2006, @12:30PM (#17089810) Homepage Journal
    I installed this as soon as it came out, as did many other Mac users. My Mac (mini DP Intel 1.67GHz, 2GB RAM) slowed to a crawl as soon as I launched it. I had to yank the power cable. I uninstalled it and all was well. This is a common experience [macintouch.com]. If you're just going to try out a new version, cool, go for it, maybe it'll go well. But please understand that it's a beta -- don't plan on getting any work done with this.
  • by GreatDrok (684119) on Sunday December 03 2006, @12:42PM (#17089912) Journal
    I've installed it and it is very similar to Classic on PPC macs under OS X. As with OS 9 apps on OS X, a full copy of the operating system is running, but the windows are drawn directly to the desktop (or at least appear to, with some glitching at the moment). I have the Windows task bar running down the left hand side of my screen so it doesn't get in the way of my dock (at the bottom) and desktop icons (to the right). Running Windows with the classic theme looks better as the shaped edges of Windows apps leave a little triangle of the Windows desktop which looks a bit poor. Lighten up the theme and it works quite nicely on the OS X desktop.

    Apple really needs to buy Parallels or do something similar. It would make a huge difference to people moving from Windows to the Mac and eventually, Windows could go the same way as Classic MacOS has under OS X and just fade away. I don't think MS would be very pleased with this development though :-)
        • by Nothinman (22765) on Sunday December 03 2006, @04:15PM (#17091952)
          IIRC the only version with the "don't run this in a VM" clause was Home Basic, all of the higher versions can run in a VM perfectly legally. And it's purely a licensing restriction, Vista Home Basic will still install in the VM just as well as the other versions.
  • Windows activation? (Score:4, Interesting)

    by mccalli (323026) on Sunday December 03 2006, @01:09PM (#17090172) Homepage
    I'm running this beta build right now - have been doing all day as I do the exciting task of catching up with my accounts (Quicken UK, Windows only). There's some graphical improvements to the interface - I like the better laid-out screen for picking the VM. There's still some interface no-nos (ok button on the left? Nope, shouldn't be the case on OS X) and I think the dock icon is trying just that bit too hard when it turns into a dancing egg timer as you save a machine's state, but overall things are better and things are fine.

    I upgraded from a previous install, which means I had a disk image of Windows installed rather than a real partition. What I'm wondering is how Windows would cope with being booted for real on MacBook Pro hardware one moment, then booted again in Parallels another moment. Surely that would kick Windows activation into life?

    Cheers,
    Ian
  • by ronanbear (924575) on Sunday December 03 2006, @01:40PM (#17090542)
    This is really good for Parallels and will be important for the company in several ways.

    Obviously it is a big feature for users who might be interested in Boot Camp and Parallels. One license, keeping the same settings etc.

    The thing that will bring the real benefits to Parallels though are related to development. Working with Boot Camp means that Parallels can access the Boot Camp drivers for Windows that Apple writes. Every time Apple updates their hardware they'll update Boot Camp with new drivers. This will make it much easier for Parallels to keep up with new hardware.

    Boot Camp adds a driver for the touchpad that includes Apple's right click implementation. Suddenly it's in Parallels automagically. Apple ads a driver to operate the inbuilt iSight. Parallels can start using it too.

    Shared documents are potentially great. Apple should work with Parallels to ensure things like the iTunes library (and iTS purchased music) is available in the Windows partition.

    Apple have already said that they are not going to include virtualisation in Leopard because they are so happy with the performance of Parallels.

    If necessary they'd buy Parallels to ensure that development keeps going on. They might do it anyway to reduce the costs.

    • by cnettel (836611) on Sunday December 03 2006, @02:05PM (#17090782)
      Native hardware drivers available doesn't mean it's a piece of cake to get it working in virtualization. It might be if you, say, was ready to give up the iSight completely in OS X, and only expose it to Parallels (then you could "simply" forward the specific hardware access, instead of providing virtualized hardware), but to get it working properly, where any app, no matter what OS it's running on, can access any piece of hardware, you need much more tinkering with the hardware on the guest and/or host side than just proper native drivers for that piece of hardware in the two environments.
    • Re:Slowdowns? (Score:5, Interesting)

      by MustardMan (52102) on Sunday December 03 2006, @12:23PM (#17089748)
      Actually, with modern multi-core processors and oodles of RAM, virtualization kicks pretty much ass. When I run parallels in fullscreen mode on my macbook, you pretty much can't tell it's virtualized. It's more responsive than the dell desktop sitting in my office at work. The only thing you really notice is that the video card doesn't support hardware acceleration, so stuff like games suck. Then again, the video card in my macbook is pretty crappy, so even with 3d support they would suck =/
        • Re:GPU access (Score:5, Informative)

          by Poltras (680608) on Sunday December 03 2006, @01:00PM (#17090074) Homepage
          This is under development by major virtualization companies. VMWare supports it for windows as guest (in beta), and Parallels has said that it was under development for a future release. This is harder than it looks though, since you have to develop a full blown 3d driver for windows and Linux (used inside your virtualized environment) that will send the calls to the host operating systems, in the case of windows transferring DirectX calls to the OpenGL API. If you want to stay generic (to work on both hardware nvidia and ati), you have to limits the possibilities of the card, or else you'll have to make a driver for each type of card you want to support. That's the theory.
    • by MicrosoftRepresentit (1002310) on Sunday December 03 2006, @12:26PM (#17089778)
      MacBooks and MacBookPro's do support right mouse buttons. Tap one finger on the touch pad for left click, tap two fingers for right click (and drag two fingers around the trackpad for scrolling, or zooming with Control pressed).
    • by SoulRank (990597) on Sunday December 03 2006, @12:32PM (#17089824)
      I came *THIS CLOSE* (holds fingers close together) to buying a Macbook Pro a month ago - it was the lack of a right mouse button and non-native support for Linux that killed it for me.
      Something tells me your intent to buy the Macbook Pro wasnt put off by the lack of the right mouse button. Firstly the Macbook Pro doenst come with mouse because it's a notebook. Secondly, OSX supports just about any USB 2 and 3 button mice.
        • Re: (Score:3, Interesting)

          Well, my solution may be a bit much for some people but, I bought one of those miniature cordless travel mice with the little usb stick that you plug in and just disassembled the little mouse to make it as small as possible (basically a circuit board and a couple of buttons) then just stuck it on my mac beside the trackpad just far enough to be out of the way but with the right and middle mouse buttons conveniently located to use when necessary.

          It's so small, it doesn't get in the way at all. I used the

    • by silverdr (779097) on Sunday December 03 2006, @12:40PM (#17089896)
      What do you call "non-native support for Linux"?! Apple laptops run linux _as natively as it goes_ for ages and this doesn't exclude the Intel based machines. I even could setup a triple-boot on an Intel based Mac (vs. all the dual-boots I had in the past). All running "natively" of course
    • by bgerlich (1035008) on Sunday December 03 2006, @12:51PM (#17089990)
      Can you imagine IE 7 and IE6 as standalone programs on a KDE desktop?!
      I did, once. Woke up sweaty and screaming.
    • Re: (Score:3, Insightful)

      or let Mac users run our app from Parallels...
      Good luck with that. As a Mac user, there is no way I would buy an app that didn't integrate properly with the rest of my desktop, much less one that required parallels. Unless you wanted to bundle the $80 Parallels license and the $100 Windows license with your app, of course...
    • Uh, because you think it is the best environment in which to develop? Other than the market share of the platform that's the only other relevant consideration. It may actually make Apple work harder to make Cocoa more appealing.

      P.S. You also lose points for having zero originality. This argument is ancient and all of the trade-offs are well known.
    • by idiot900 (166952) * on Sunday December 03 2006, @12:57PM (#17090054)

      or let Mac users run our app from Parallels...
      Not this Mac user. I bought a Mac because I like the way a Mac works. To use your app, I'd have buy a copy of Windows and a copy of Parallels, and then run them - and some people think the Java VM is bloated! And I'd have to deal with the Windows app not being well integrated with the rest of the system. The only way this will work is if there is no serious competition in your market segment.
        • by wootest (694923) on Sunday December 03 2006, @04:31PM (#17092086)
          The Objective-C-to-Java bridge is being abandoned because it really didn't make things easier for Java developers and because it was a pain in the ass to write code with for everyone and to maintain for Apple. (However, RubyCocoa will ship with the next version of Mac OS X because it's a lesser pain in the ass on all accounts.)

          You may know more people who have VPC or Parallels than not (I do too), but how sure are you that those people will be representative to the entire Mac market? To the market you want to aim your product at? (Unless it's "technologically competent user who has ever heard of Slashdot", fat chance.)

          There's also psychology in it. At its core, the people that are now switching to Macs are not switching *because you can run Windows on it*. They are switching *because you can run Mac OS X on it*; the ability to run Windows on it just pushed them over the edge because Mac OS X doesn't have a 90%+ market share. If they were indifferent to what software they preferred, they'd be using a different brand of computers, and run Windows, not Mac OS X.

          Most Mac users, even the ones propped up with VPC or Parallels (I plead guilty), ultimately want to run Mac-native software rather than Windows software. Parallels is life-support for existing software that people need to run, and even if it was free and shipped with all Macs and took up half the memory and disk space that it does today, it doesn't make Windows software into Mac software.

          You don't need to think that Mac software is superior to Windows software to concede that Mac software has an advantage over Windows software running in a Mac simply because it gets access to all system APIs to things like address books and keychains and hardware support and preferences, and because it looks like everything else you run. Windows software just think it's running on an isolated box and won't become aware of the Mac OS X side of your computer unless you as a user go to some length and the software itself supports it, at which point the developer will already need to make way in their timeplan and budget for Mac-specific testing.

          Still not convinced?

          1. Mac market share is currently surging. More people, not fewer, will arrive at the Mac platform in the next few years, and building a dedicated version (and almost no well-designed application will need to be rewritten entirely from scratch) is becoming more and more economically feasible.

          2. Would you want to bet your entire Mac user base on a competitor not releasing a native Mac version? Unless it's a turd, people will switch to that in a heartbeat. You will lose out months of sales as you rush a native product to market, or need to pull out of a market completely.