VirtualPC 2004 Versus VMWare 4.5?
BackNBlack writes "Ars Technica has an interesting comparison shootout between Microsoft's VirtualPC 2004 and VMWare Workstation 4.5. Has VirtualPC improved since Microsoft bought it from Connectix? It looks as though VMWare is really the choice of those who can afford it. I'm also a little surprised that Microsoft is not as compatible as it could be, given the competition."
For me, that is all that matters.
that comment about compatibility in the lead-in kinda surprised me. After all, didn't they purchase VirtualPC because server consolidation was hurting Windows Server sales? They made tons of money when people realized they needed a seperate BOX for each server process run on Windows( they sold more OS licenses ) but now the cats out of the bag and TCO cost are killing them.
So, why would Microsoft care about anything but how this works on Windows and targetted apps? They don't. IMHO.
LoB
"Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
Not only that, but they can run previous versions of Windows -- or at least some of the sub-systems -- under Longhorn, thereby allowing backwards compatibility without having to design it directly into Longhorn's own APIs. (Like Apple did when they went to OS X, I believe).
They could also the technology for sandboxing "untrusted" applications and isolate them from the main system.
C:\CYGWIN\usr\X11R6\bin\run.exe XWin.exe -multiwindow -clipboard
This runs the X server in a rootless mode that does not require a window manager (Windows is your window manager - this instructs the X server to in turn instruct windows to draw decorations around your X client windows) and which performs clipboard integration. There are some other switches you can set, see man XWin for more information. In particular people with multiple displays will want to set another switch to support that, and there is also a switch to specify that all clipboard contents should be 8 bit (no unicode support.) It's not the fastest nor the best* X server out there, but it certainly does the job. If you are going to be running X clients locally, which you probably will if you install cygwin, you will want to add "DISPLAY=localhost:0" to your environment.
* Actually, cygwin's X server might have recently become the best X server around. It uses directdraw to draw windows, it properly handles the clipboard now which X-Win32 still can't seem to get right after an update they explicitly claimed would solve my clipboard problem, and it uses standard X tools like xhost for management.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
The only thing that has been a problem so far is getting the VMWare client utils installed if the virtual OS is running the 2.6.x kernel.