Post a Comment
*Sigh* Now all the comments of Digg and Slashdot are going to get repeated here.
= Yes, there is a valid reason for this
= No, Macs are not shit
= No, Windows is not shit
= No, the Apple fanbois are not mad
= No, the windows fanbois are not jealous
= No, you don't buy a Mac just to put windows on it, there's more to it than that
= Yes, games do matter actually.
= No, this is not pointless; again.
The trolls will definitely be out though, even OSNews has them. I can't quite understand why people don't see how this (XP on Macintel) is useful; granted it might not be useful to them, per se, but some people just have to use Windows sometimes, whether they like it or not; and carrying one laptop, sure beats carrying two. OSX is much better for the daily non-work stuff (if your work is Windows-centric). And not forgetting gaming on Windows of course.
edit: "on windows"
Edited 2006-03-14 19:01
Not really. See the organizers blog at: http://www.pintmaster.com/wordpress/
the page is back up: http://www.winxponmac.com
no changes...?!
edit: ok, the forums are STILL down though.
Edited 2006-03-14 19:29
I remember reading that either Grub or Lilo already had EFI support, in which case all it would take is a boot CD that would find all the partitions, determine which is OS X and which is Windows and install the bootloader with the correct configuration. I wouldn't be surprised if after the first few releases it was even skinned in such a way as to look like it belongs in there.
I really would like to replace my Dell laptop with an Apple one, but I need to be able to do my business work. All of that is on Windows, not OSX. Having to boot into Windows for work sessions and then back into OSX for personal ones would be fine. Better still would be running the two somewhat simultaneously where you hibernate one operating system or the other for fast switching between the two. I'm looking forward to dual boot. This way I can have a Mac at home and at work.
I have been a big fan and user of Crossover Office on Linux for a while. Now that OS X is running on Intel Chips, Codeweavers is getting ready to launch Crossover Office for OSX. I have been contacted to be in thier Beta program.
What this means for business is that you can run a number of Windows office apps natively (more or less) in OS X.
www.codeweavers.com to check out the list of apps that run. This could make switching to Macs a viable alternative for some functions in some businesses.
Windows Office apps already run natively in Mac OS X.
http://www.microsoft.com/mac/
So, I'm curious, why would you need/want to run MS Office for windows through crossover office when the native applications are already there for OS X?
Also, looking through the list of apps, I didn't see anything that didn't either (A) already have a Mac OS X native app, or (B) have an OS X alternative in existence that was as good.
Yes, I can see its use for *nix, but I don't think the market is there for OS X.
Why use Crossover Office? MS Office for Mac is hindered because it is missing one tiny little app... Access. I would love to be able to use my Mac all the time, but beings how my office is almost completely run off of Access it is hard to migrate completely so I end up having to have atleast two different computers if I want to do any work from home instead of working all late and crap all the time.
Why would I run Windows on a Mac?
Why would anyone care whether or not you are interested in running Windows on a Mac? And really, why would someone not run Windows on a Mac? Aside from the tiresome anything-but-Microsoft kiddies who find the idea somehow offensive, that is.
For 1 simple reason. Boot screen is wrong ! It is now a white background with a windows logo, but a black background and a windows logo on boot time.
And the strange point is that the video is blurry for showing interesting part : back of iMac, panel in windows.
So, next, please ?
This may in fact be a fake, but there is a bit more to getting windows to run on a mac than just bootstrapping the OS and faking some BIOS calls. One also has to deal with the fact that the Mac boot time video is not the same as Windows (the processor might not even run in the necessary Real Mode during bootup), so they'd also have to write some sort of video driver to make it work. Probably they don't have that yet, so they substituted a white logo screen for the startup video. BSODs probably don't work either in this setup. I wonder if they were able to get the kernel debugger working.





