P
Papa
Sarcastic?? Doug was just offering you the truth.
Harry Ohrn said:No you can't always decide what you want to do with what you
purchase. I purchased my house. If I decide I want to add a room
I must get a building permit from the City first.
I buy a car. I
decide to leave it unlocked, running with the keys in the
ignition. Someone steals it. In my town you are fined for
leaving an unlocked running car with the keys in the ignition.
My car right?, My house right? I hardly think so. For some
convoluted reason we think that we have full and total rights to
something because we paid cash for it. Human vanity.
The earth was here a billion years before we
walked the planet and it will be here a billion years after all
of us are dead and we think we *own* the parcel of land we sit
on. We own nothing.
D.Currie said:There are all sorts of restrictions on products that you
probably never even think about. Some of it has to do with
safety or warranty ("do not use in bathtub" "For home use
only").
I've purchased products that seem
like they'd do what I want, but when I get them home, they
aren't capable of it for one reason or another. The problem
certainly isn't restricted to computers or software.
You can disobey those rules, of course, as there's no way for
most products to keep you from dumping it in the tub or taking
it to work with you.
And you can tweak your car engine, if you
know how.
Other restrictions protect the copyright owner's rights.
Needless to say, if you can't live with those restrictions, you
shouldn't buy e-books and just stick to the free ones and only
buy paper copies that don't have the technical restrictions on
them.
If it came WITH the computer, you'd have to return the whole
computer, most likely, or haggle with the computer manufacturer
to let you have the computer without their pre-installed OS.
That would be up to them. If it was retail, you could easily
return it directly to MS.
That's pretty much the case with a lot of things that come with
licenses, leases, contracts, or warranties. It's true that most
people don't read the fine print, but that doesn't mean that its
not binding. If you start reading that stuff, you might be
surprised at what you're agreeing to by using certain products.
The restrictions have always been in place with MSs operating
systems, it's just that there hasn't been a way to enforce it
very well. So people got used to buying one copy of Windows and
putting it on 3 computers.
I think it's interesting that people think software purchases
should be different than other things they buy. For one thing,
they think that if they lose the software, they should get a
free replacement, if they haven't lost all of the components.
So
I bought a new padlock and lost it, but I still have the key.
Should the company give me a new padlock? Unless there's some
sort of replacement insurance, if you lose something, it's lost.
The manufacturer doesn't replace it. Or at least not without a
fee.
Or they lose data, and they expect someone else to take care of
that. "I bought a new wallet, and it fell out of my pocket and
all my money blew away. Who is going to replace the money?
And people expect all sorts of free technical help with
computers that they wouldn't get elsewhere. Go tear apart your
car engine, scatter the pieces in the garage, then start calling
the dealership, the car manufacturer, and the engine
manufacturer and see who offers free phone support.
If you break a new product by using it in a way that the
warranty doesn't cover, you won't get a replacement. Most people
wouldn't argue that. They used the carving knife to open a paint
can, and now it's bent. Oops. But if you "break" the software by
using it in a way not covered by the fine print, it's sort of
the same situation. That OEM copy of windows from Compaq isn't
supposed to run on your old Gateway. Or that new copy of XP
isn't going to run on your 486.
If you buy a new car, you don't expect that you can start
ripping parts out of the old one and adding them to the new one.
And the bigger the age difference, the less likely it is that
parts will be compatible. The tires might not fit, the leaded
fuel could be a problem, etc. But people expect that every piece
of hardware and every bit of software they own should transfer
flawlessly to a new computer with a new OS. Some stuff will
transfer, some won't.
It's a pity,
There are software programs that are more restrictive and more
annoying than what MS has implemented. Those other programs tend
to have a smaller market share or special segment of the market,
though, so most people haven't run into them.
You'll probably
see more companies do what MS has done.
If that's not your cup of tea, there's always Linux. It will run
on the hardware you have.
Ally said:What's the nature of those restrictions? What would happen
(legally) if I did use "it" in a bathtub?
[snip]
(It was neither; it was a full installation CD for system builders,
and in and of itself not tied to a specific mainboard. The computer
I installed it on is from '99 or so. But yes, I should've taken the
time to fully understand the intricacies of the EULA, and then try
to return it.)
Or on one computer at a time, spanning three computers. Right, it
wouldn't have occured to me that something like that might be
against the license until I encountered the WPA. I used to think
"don't pirate the thing, and it'll be okay."
[snippety]
I think it's interesting that people think software purchases
should be different than other things they buy. For one thing,
they think that if they lose the software, they should get a
free replacement, if they haven't lost all of the components.
And not _entirely_ unreasonably so since, unlike a padlock,
duplicating something immaterial like software doesn't exactly cost
anyone much. But no, I suppose it's not up to the customer to
decide whether such a service should be offered.
I'm not sure I understand why you're bringing up these examples
now. I didn't lose or break anything. I didn't get support with XP
anyway, so I'm not demanding any either.
It's a full installation CD and it _will_, most likely, transfer.
It won't neccessarily "activate", though. That's what bugs me. Not
that a compatibility problem wouldn't, but this isn't one.
Maybe the software vendor could have had the decency to point out
that "no support from MS" isn't the _only_ difference between the
"system builder"/OEM and retail versions.
Then again, the people who're supposed to buy these versions (i.e.
OEMs) no doubt already know what they're getting _their_ customers
into.