A Site that Lists Systems w/o DRM? 49
timdaly asks: "I'm about to purchase new hardware. I understand that DRM has been added to the BIOS of some systems. Is anyone aware of a site that lists which systems are DRM-disabled? I don't want to purchase hardware that has any DRM. Like unique keys on CPUs the DRM technology seems to be more of a threat than a useful tool."
Simple... (Score:2, Informative)
Re:Simple... (Score:4, Insightful)
Re:Simple... (Score:4, Funny)
Apple is as pure and clean as the wind-driven snow.
If my iMac gave me electric shocks for looking at the Dell website, I would thank Steve Jobs for setting me straight.
Re:Simple... (Score:1)
Re:Simple... (Score:2, Insightful)
Re:Simple... (Score:1)
AAC does not *use* DRM, it is simply DRM capable. True, AAC files off of ITMS will have DRM. But, AAC files ripped off of CD's that you own will not have any DRM.
Re:Simple... (Score:1)
no posts? (Score:2, Interesting)
I'd also like to know if we can keep track of the DRM "infection". I don't see DRM as being good at all for the consumer. Perhaps in some very small ways, like having control over a hateful email sent to someone else, but no one should be doing such things anyway.
Stay away. Stay far far away. (Score:5, Interesting)
If you absolutely insist on sticking to PC/Windows, consider supporting the OpenBIOS [openbios.org] project, but it's not available as a hardware BIOS, nor in any motherboards that I know of, it's an after-the-purchase flash update (plus god only knows if it works properly). And since you're trying to flash away the DRM in the BIOS, you never know, it may not be allowed in the future. After all, we have to keep "viruses" from flashing our BIOSes now don't we? So lets make sure those flashes are cryptographically signed by Award/Phoenix/AMI...
Re:Stay away. Stay far far away. (Score:5, Insightful)
Interestingly enough, there's a front page article [slashdot.org] on the LinuxBios [linuxbios.org] project. According to the linked article:
LinuxBIOS works on 64-bit and 32-bit CPUs. CPUs supported include the Alpha, K8, K7, PowerPC, P4, PIII, PII, Cyrix (VIA), Geode (now AMD) and SC520 (AMD). Chipsets are too numerous to list. Form factors of mainboards range from the smallest PC/104 systems to the largest K8 systems. An IBM PPC 970 port is in progress.
As for Apple, trading software lock-in for hardware lock-in is hardly a solution.
From the LinuxBios docs... (Score:4, Informative)
NOTE: BE ADVISED THAT THIS STEP CAN HURT OR KILL YOU! YOU ARE WORKING WITH A POWERED-ON COMPUTER AT THIS POINT. THE COMPUTER NEEDS TO BE OPENED UP, AND YOU NEED TO REMOVE A CHIP WHILE THE COMPUTER IS ON. IF YOU HAVE NOT DONE THIS TYPE OF WORK, DO NOT DO IT! WE TAKE NO RESPONSIBILITY FOR ANYTHING THAT HAPPENS AT THIS STEP. BEFORE DOING THIS STEP WITH POWER ON, YOU SHOULD TRY IT WITH POWER OFF.
Figure out if you're going to burn the DoC on the build or LinuxBIOS machine. It has to be the machine with MTD modules.
Open the machine (LEAVE THE POWER ON), yank the flash, and plug in the DoC. We recommend you practice this first with the power off. Make sure that whatever you do, you are not shorting things out. Avoid using a metal tool!
NOTE: YOU CAN HURT YOURSELF AT THIS STEP. We can't take any responsibility for what happens to you here. If you haven't done this, or are not trained, or have a history of getting hurt by hardware, DON'T DO IT.
While I don't think 12 volts will electrocute me, I'm a little reluctant to swap a chip in a running machine. Until this project is at the point where I can just flash the BIOS with a DOS floppy or similar, I'll stick with what works.
Re:From the LinuxBios docs... (Score:5, Informative)
Re:From the LinuxBios docs... (Score:1)
Putting it in backwards... (Score:1)
Re:From the LinuxBios docs... (Score:2, Informative)
Electricity is very dangerous at almost any voltage, if the right conditions are met.
Don't kid yourself. Unless you understand the voltage current relationship and what parts of your body electricity can kill you with, you are playing russian roulette.
In this case, most of the voltages and currents are low enough to not kill you, but electricity has a way of finding harmful places to shock you... don't underestimate it's potential (no pun intended) to kill
Re:From the LinuxBios docs... (Score:1)
But: seriously, do you think a computer power source could supply enough current under so low voltage?
12 Volts at 1/2 Amp is plenty (Score:2, Insightful)
The "problem" is getting the current to flow through your relatively nonconductive or highly resistive skin. This is why the famous CPR/defib paddles are energized with relatively higher voltages, so that the current can penetrate the skin. The low voltage "solution" is sweaty palms and sharp contact points. Can you say nervous? Can you say stamped metal cas
Re:Stay away. Stay far far away. (Score:2)
LinuxBios, good catch. I think that may have been what I was thinking of when I typed 'openbios' into google, but both look interesting.
As for Apple, trading software lock-in for hardware lock-in is hardly a solution.
It's more like trading a screwdriver that only allows you to unscrew the screws on particular objects, for a screwdriver that only accepts a few particular brands of hex bit. They're both potentially draconian
Re: Vote with dollars (Score:1)
Re: Vote with dollars (Score:2, Interesting)
As an owner of a Dual AthlonMP 2800+ rig, I can tell you that the extra $1000 for the SMP would be worth it...once you go SMP you can never go back. And SMP should be an extra $1000 (unless you can only get SMP on the highest end G5 and compare that price against a slightly lower end model). All in all it only cost me about $300 more for the SMP system ($70 more for the board + $100 for the extra proc + $30 for the extra HSF + $100 more for the RAM since the board only takes Registered ECC).
Having two ogg
The sky isn't falling (Score:5, Interesting)
Oh, for *Christ's sake*. Look, you silly ninny. Part of the TCPA spec is that it be *user-disablable*. A user *must* be able to flip off TCPA on a system that uses it.
Now, to this I've heard two counterarguments:
a) Compatibility. "Yes, but the vendors will just make their software not *run* without TCPA because they insist on having TCPA-based protection for their product." Fine. Buying a PPC or a SPARC or some oddball x86 box isn't going to do a damned thing to help you here. If a vendor isn't willing to make a product that works without TCPA, they aren't going to make that product that works without TCPA. It means people that have x86 boxes with TCPA off *and* Mac/Solaris/etc users are simply excluded from using that product. You gain nothing by switching platforms.
b) Slippery Slope. "Oh, but they don't have it on *today*, but I've seen someone speculate that the TCPA spec will be changed someday to *prevent* people from disabling TCPA!" Okay. For starters, this is astoundingly unlikely. There is *zero* reason for any BIOS vendor, OEM, or software publisher to want to prevent you from disabling TCPA. They simply have no incentive. It doesn't help them an iota. If they want their software not to run on a TCPA-less system, they won't let it run on a TCPA-less system. It doesn't help prevent piracy or let anyone charge higher prices, or do a single thing for anyone, and a few people will complain bitterly about it. Why bother? In the second place, no barriers are being erected that will make it harder to switch if such an unlikely event did take place. If the whole world suddenly says "no TCPA disabling for you!"...fine. You can switch.
The main group of people that I've seen ranting about TCPA have been overzealous Apple fans, who are apparently trying to confuse and worry people into switching to the Mac.
Oh, yes. This doesn't affect Linux users in the least, either. The only possible people who would be affected would be Windows users.
Finally, I just don't see the fuss over TCPA. It's useless for securing media (far too many ways to break it in any kind of a real-world implementation, it only takes one break to let media be spread across the Internet, etc). It may have minimal use (extremely minimal, since it is interfaced with in a standard manner) in securing software, but people already happily crack things using SafeCD and similar pieces of software -- players pirating software already frequently use cracked or modified copies. All they need to do is crack and distribute a copy that doesn't require TCPA (just like copies of software that check validity over the network or copies of software that use CD protection or whatnot.
TCPA is the most overblown fear that people here have had for *ages*. It's really amazing. If you want to get LinuxBIOS or something, great -- but be realistic, and do it for the fast-boot benefits and other nice things in LinuxBIOS, not because of some phantom fears that people have managed to raise about an Orwellian computing environment. It's just not going to happen.
Re:The sky isn't falling (Score:3, Insightful)
In other words, almost everybody.
if non out there.... (Score:5, Interesting)
- nondrm.slashdot.org
hey, I don't recall another site that dislikes DRM as much as the slashdot crowd... so why don't we make an effort and do a 'nondrm' zone, a zone that is stuffed with 'how to circumvent' DRM'd-anythingRe:if non out there.... (Score:2)
I'd say Against TCPA is such a site? (Score:3, Informative)
Heh (Score:1)
Re:Heh (Score:5, Insightful)
DRM watch list (Score:5, Funny)
Hmm.. Thats strange. I can't enter the URL for [REDACTED].
Oh, [REDACTED]! This new machine from [REDACTED] must have one of those damn [REDACTED] enabled BIOSes. No more [REDACTED] for me. [REDACTED]!
Here it is (Score:1, Funny)
Hardware without DRM: Everything else.
Re:Here it is (Score:1)
Re:Here it is (Score:1)
You'd be foolish to think it will stay this way.
Re:Here it is (Score:2)
M-x tinfoil-hat-mode
Then again, what would stop IBM from letting their hardware run only THEIR version of Linux. Good thing I don't have to go up this hill... it's slippery
Re:Here it is (Score:1)
But if it's the ThinkPad Security Chip [ibm.com] you're referring to, then you're wrong again -- there is preinstalled software to use it. I know so because a colleague of mine has tested it (on his T40 [ibm.com]).
My TP (T23) doesn't have a security chip, nor would I think it necessary to use one.
But DRM? I'm quite certain they don't have that.
Elaborate on CPUs? (Score:1)
Can anyone give a specific example of how this is so?
For a while, about 6? 4? years ago, (Score:4, Insightful)
see for example, this link at intel for the faq [intel.com] or this link where intel started defending it [internetwk.com] or this link, last updated 4/28/2000 [bigbrotherinside.org] talking about the fact that psn's (pentium serial numbers) will not be in the next generation of pentiums that last link has many bits about why the PSN was a headache.
Re:For a while, about 6? 4? years ago, (Score:1, Troll)
Re:For a while, about 6? 4? years ago, (Score:2)
do you have a cite for your claim that p 4's have individual serial numbers?
Re:For a while, about 6? 4? years ago, (Score:1)
Re:For a while, about 6? 4? years ago, (Score:4, Informative)
These serials are used to track down bad areas on the waffers and other things in the manufacturing process.
MAC addresses (Score:1)
Re:MAC addresses (Score:3, Informative)
Now we do: www.DRMfree.com (Score:5, Informative)
Mac addresses (Score:1)