Seagate to Drop IDE Drives by Year End

ianare writes "Seagate plans to cease manufacturing IDE hard drives by the end of the year and will focus exclusively on SATA-based products. Seagate is the first major hard drive manufacturer to announce such plans, though others will likely follow suit. That's not to say support for the 21-year-old PATA standard is going to vanish overnight; similar to how ISA slots were available long after most of us had ditched our old ISA peripherals."

Comments

You'd think they'd know better

[Anonymous Coward]

Dropping hard drives can really damage them.

Good

[Espectr0]

At the least, this will drive the price of SATA drive down. Maybe it will be the same like RAM, where DDR2 is actually cheaper than the old DDR memory standard.

Re:Does it really matter?

[CastrTroy]

Exactly. Good riddance. It's not as though these things are in high demand. Sure some company will keep on producing them for people that are into legacy hardware, but I fully expected that the main manufacturers (Seagate, Maxtor, WD, et al) would stop producing these things eventually.

but the motherboards!

[Doppler00]

Poor motherboard manufactures still have to support all the existing legacy devices, even though new devices uses new I/O standards. I always find it amusing to see serial, parallel ports, and floppy connectors on new motherboards. Of course, until DVD drive manufacturers switch to SATA, we'll still see IDE connectors on mothboards. Do the SATA controllers really cost that much more?

Re:but the motherboards!

[CastrTroy]

I remember about a year back reading about state of the art motherboards that got rid of all this crap we don't need. I seriously think that more manufacturers should do this. I have no use for a serial, parallel, ps2, floppy connectors, IDE connectors, and all the other legacy junk they insist on putting on motherboards. Every one of those ports takes away 1 (or several in the case of parallel/ide) ports that could be something useful, such as USB, FireWire, SATA, or something that people will actually use. If people want to hook up ancient hardware, let them use PCI adapter cards and port replecators.

Re:Does it really matter?

[Dunbal]

The Amish still use horses and buggies and don't want anything to do with those new-fangled horseless carriages. Your point is? Technology moves ahead. Stay with your system, or upgrade. But no one will stop progress because you complain.

Re:Does it really matter?

[jimbug]

does this mean if I use IDE I can grow a beard now?

Re:What about osdev?

[larry bagina]

As a consumer, I'd rather get rid of the legacy shit (ATA, ps2 keyboards, bios, DOS/Windows :-). But for hardware hacking/os writing, a USB stack, firewire stack, etc are more work (and don't provide the immediate feedback like 100 lines of assembly to read the raw keystrokes).

You an still have fun with an ARM breadboard kit, though :-)

It's a bad idea

[Weaselmancer]

Hardware: Seagate to Drop IDE Drives by Year End

They don't work so well after dropping them. I, for one, will not buy one of these dropped drives at any price.

Re:PS2 keyboards

[ozmanjusri]

You can have my Model M keyboard when you pry it from my cold dead fingers....

Your proposal is acceptable.

Re:well, shit.

[Short Circuit]

can I get a hand?

0 . ^ .0 0
0.l l l l0 0
l l l l 1/^0
0\ . . . ./0
0 \ . . ./0
 
000101010000
011010101000
101010101110
0 10000000010
001000000100

There ya go. Pretty easy, once you get through the blasted lameness filter. I'd use lorem ipsum, but I don't Slashdotters would appreciate it much. So far, in the time it's taken me to get this past the lameness filter, your post went from a "2 Funny" to a "3 Funny". I wonder how many other people are attempting to craft a response as well. Let's see if using 'l's will get me past the "Too many junk characters" filter. Yup. Now I see that Slashdot doesn't support <pre>, and <tt> is broken. How about <ecode<? Nope. Gotta find something for those spaces. Ah! How about alternating periods and asterisks for a dark background? Ah! Too many junk characters again. Let's alternate the asterisks with spaces. Nope...Replacing the asterisks with zeros works, but now you can't really see the hand. Ah, heck. Let's make a 0/1 bitmap. That's funny...it added a space in the middle of one of the (short!) lines. Let's append spaces to each line...Didn't work. Ah hell, now your post is at "4 Funny". I'll leave both hands up.

Long story short, don't bother with the ascii art.

Re:PS2 keyboards

[dotgain]

Having USB ports for the mouse & keyboard would take the fun out of that!

Don't worry, the speed at which WinXP handles booting up with the mouse and keyboard in different ports than last time more than makes up for that.

Re:PS2 keyboards

[afidel]

The reason to drop PS/2 is that then you can remove the ISA emulation logic from the Southbridge. On most modern designs the PS/2 controller is the only component still using that part of the chip so you can drop it if you drop the ports.

Re:What about osdev?

[Xiph1980]

By jonwil (467024)

The #1 reason I want something like EFI is to eliminate the world of proprietary bootloaders/selection mechanisms for good. Essentially the BIOS would be the one that displays the list of boot options.

Unfortunatly no vendor that supports EFI (including all Linux distros I have seen) gets it totally right (where any boot time configuration options are handled through EFI and not through another bootloader)
Well, EFI may not be the best way to get away from proprietary stuff. It seems that EFI explicitly vacilitates such behaviour by hardware manufacturers:

Interview with Ronald G. Minnich (Google cache)

What are your thoughts on the Extensible Firmware Interface (EFI)?

I have spoken with the EFI authors at length. They make no secret of the fact that a "core value" of EFI is the preservation of intellectual property related to chipset programming and internal architecture. To put it another way, EFI is dedicated to the preservation of "Hard" hardware (as defined above), and the provision of binary interfaces and subsystems to BIOS vendors and others.
It is not really possible to build a full open-source BIOS if EFI is involved. The Tiano system, which Intel claims is an open source BIOS, can not be used to build a BIOS unless it is attached to proprietary, binary-only BIOS code provided by a vendor.

Another important thing to realize about EFI is that it also contemplates enabling chipset features that will trap certain OS operations to an EFI-based control system running in System Management Mode. In other words, under EFI, there is no guarantee that the OS owns the platform.
Accesses to IDE I/O addresses, or certain memory addresses, can be trapped to EFI code and potentially examined and modified or aborted. Many see this as an effort to build a "DRM BIOS".
I am not sure what the real intent of this design is, but is is a real concern in secure environments (such as those found in governments, banks, and large search engine companies). A number of vendors and users have told me that they are not sure they can ship an EFI system they are willing to trust in a secure environment.