Apple Support: Boot Camp Beta expires as soon as Leopard's released.

[Nermal]

This is not true. In fact users of MS Visual Studio 2003 and 2005 cannot work on a project together! I use Parallels to load up VS and all of our developers had to switch to the latest VS at the same time because once you convert a project you can't go back.

At least they've corrected this problem in 2008: You can work on framework 2, 3 and 3.5 apps within the 2008 IDE (and in some cases gain new features even when still targeting framework 2).

 

[BTW]

------
This is not true. In fact users of MS Visual Studio 2003 and 2005 cannot work on a project together! I use Parallels to load up VS and all of our developers had to switch to the latest VS at the same time because once you convert a project you can't go back.

As for the Core API and XCode changes. I welcome them. I don't think Apple should spend time retro-fitting it for older OS X.

Finally there are lots of features for Vista and is not available for XP and I don't mean the BS Microsoft is pulling with the Games for Vista Only just to push the platform. I mean functions that would take longer to develop or even hampered by the need to support multiple OS Versions.

Are you talking about web projects in VS? I've not experienced that on non-web projects. Even so I can still run VS 2005 on 2000, XP, and Vista. Xcode 3.0 is Leopard only.

At least I can get the .Net 3.0 framework for XP even though it is distributed with the Vista OS. Why shouldn't Core Animation be backward compatible with Tiger? Greed?

 

[gnasher729]

Well, technically, shrink-wrap and "click through" license agreements are legally a questionable, gray-area, all in all.

(EG. If you have to simply click an "OK" or "I agree" button to move past one, what if you just let one of your kids do it for you? They're not of legal age to be held to a binding contract, right? ).

It can be argued that the kids have been acting as your agent; so telling them to click on "I agree" is as good as doing it yourself.

A better method: Find the bit in the installer where the text "I agree" is stored, change it to "I disagree". Start the installer, and click on the "I disagree" button.

Or this method: Turn off your monitor, then start the installer. Click around blindly on your black screen until installation begins.

 

[TBi]

A better method: Find the bit in the installer where the text "I agree" is stored, change it to "I disagree". Start the installer, and click on the "I disagree" button.

I'm pretty sure that modifying the install file like this is illegal for most programs.

 

[PhilS1121]

It can be argued that the kids have been acting as your agent; so telling them to click on "I agree" is as good as doing it yourself.

Always good to get the kiddies involved in "fraud" at an early age.

 

[jdechko]

Maybe this will spur on advancement for OnMac, the project without which Boot Camp would likely never have existed...

I really don't buy that Apple/Intel didn't already know how to (basically) emulate a BIOS from within EFI (the only "tricky" step to Bootcamp). Between the two corporations, I'm sure they'd already figured it out before the official switch announcement was ever made. Apple & Co. were just sitting back, letting the competition run its course. Kinda like a puzzle. After the OnMac competition was over, Apple said, "see, here's the easy way..."

 

[SolRayz]

When I decide to upgrade to Leopard will I have to scrap my current bootcamp partition and reinstall, in my case, Vista? My inclination is no, but I am not sure. I would hate to have to reinstall Windoze as I only really use it for Flight Sim. So basicaly install Leopard on main partition, update Bootcamp partion drivers in Windows afterwards, correct?

 

[Westside guy]

People should be careful as Apple might brick their Mac's in similar fashion to the iPhones. Makes me nervous, I wouldn't update tiger for a while after leopard launches just to be safe. Apple has shown that they do not mind "permanently disabling" your device if they feel you are outside of the EULA. Bite me once shame on you, Bite me twice shame on me.

Yes, Lord knows it must've been an intentionally malicious decision by Apple. There can't possibly be another explanation.

Oh, and if you're ever using a Haxie on OS X, and after an OS update things stop working - that's intentional on Apple's part as well.

Conspiracy theories are really handy. They are self-consistent, and don't require a lot of intellectual effort to maintain.