Microsoft Virtual PC 2004 Removes Linux Support
Psykechan writes "MSFN has got themselves a beta of the new MS Virtual PC 2004 which should be out at the end of this year. Most notable in their 'fixes' is the removal of Linux, BSD, Netware, and Solaris from the supported OS list. They may still work, they just aren't supported. We all thought that this would happen after MS bought Connectix but this just makes it official."
is still in there, you select "Other" in the hard drive image set up, and just have to format the image yourself, rather than VPC doing it for you. End of discussion.
"I would say that 99 per cent of what my father has written about his own life is false." - L. Ron Hubbard Jr.
Ummm.. Because it allows Mac OS users to run Windows applications? What other application does that (reliably)? SoftWindows has died, SoftPC had the same fate and RealPC is completely destroyed. Did you even consider that before posting?
The only hope now lies in Bochs, an open source PC emulator/virtual machine thingy. Currently it's quite hard to configure and has very low compatibility with existing x86 OS's, but at least it somewhat works and the source is out there.
I run GSX at home, it rocks..but $2,500 is a little more pricey.
But then again, $300 for an unlimited number of PC's, what a bargain.
I think a lot of /.ers are collectively saying, "I told you so."
Sticking feathers up your butt does not make you a chicken - Tyler Durden
No. VMWare is a virtualiser rather than an emulator. You need to emulate the ix86 instruction set on a Mac in order to run ix86 software.
Oceania has always been at war with Eastasia.
Also, if Virtual PC supports Mac OSX, couldn't it also support some of the BSDs since OSX has at least some BSD components underneath?
Like another commenter said... it could be a Carbon app which BSD doesn't have.
BSD ALSO doesn't have a Quartz windowing environment. The app is not X11 so you maybe could run it but not see anything displayed. It also probably requires many Apple runtime libraries.
In the case of Bungie and Halo it wasn't that the ports got behind. Halo's primary platform was the Mac, work on the PC version was also ongoing but not as far along. When MS bought Bungie effectively all development work stopped on the PC and Mac and they ported it to X-Box and finished development there.
So much was planned for the original that didn't make it because they had a major platform shift mid-development
At the time Bungie had a big following and there were a number of web sites tracking everything Marathon and Halo. Jason and others at Bungie would occassionally throw in a tid-bit as to what was happening.
Then it was sprung on the community that MS had bought Bungie
Unfortunately we'll never get the game Halo was supposed to be, we just got the cut down, rushed X-Box port
Quite understandably many of us felt shafted
Don't blame me - this
Its hard to configure, doesnt support 'real' graphic modes.. is slow...
Its a great project and its a lot of work, but isnt 'quite there', yet...
So i still use VMware personally..
---- Booth was a patriot ----
As one of the other posters alluded too, developers LOVE virtual pc for debugging apps on legacy platforms (Win9x/ME). At least I do. It also makes testing software on various platforms MUCH easier (especially w/automated testing) while using fewer machines.
I'm actually very impressed with VPC. It is a very slick piece of software; only problem is that it is slow as dirt...:) (no surprise there)
Microsoft has released a gratingly repetitive support document on this issue.
The blue box was fiction. No such work was ever "started at NeXT".
The Blue Box, in fact, existed as part of OSX server. Before Jobs closed off the Rhapsody on Intel product, the Red Box would have let users run Win32 apps, The Blue Box later became the TrueBlueEnvironment, and the Yellow Box became Cocoa.