Slashdot Mirror
Legacy-Free PCs
JeffM2001 writes "InformationWeek is running a story by Fred Langa which gives an overview of the ways to create a true-Legacy-free computer. Finally we can have a PC not based on twenty year old technology." Update: 04/07 17:34 GMT by T : Pages past the first one of this article seem just to loop; here's the printable version, which has the whole article in one go.
It seems as though the PC crowd has this obsession over the worry that someday they might have to use something which is twenty years old or more. Thus, in mainstream machines, you'll see things like ISA slots or floppy drives still. Heck; the whole x86 architecture is basically just bolt-on instructions to the previous architecture, with a lineage going all the way back to the Intel 4004. And while some of the backward-compatibility feats they've pulled are nothing short of miraculous, our blind insistence on backward-compatibility is at the point where it's holding back the state of the art more than advancing it.
This is the sort of thing emulation and hardware adapters were made for.
Guess what I had absolutely 0 problems with: yes, Windows XP.
My point is that when you buy a non-legacy free motherboard you have a CHOICE of using usb / usb2 / firewire rather than serial parallel and ps2 but if you get stuck with an OS that does not really support it, well, you are truly stuck!
Mother is the best bet and don't let Satan draw you too fast.
Does anyone know if EFI is an OpenFirmware implementation? If it isn't, we don't want it! At the risk of sounding "with the crowd", OpenProm and other OpenFirmware implementations are so much nicer than all PC-BIOS concepts I've seen to date. Add a simple psuedo-GUI shell in front of the prompt, and you'll make users happy. Besides, your average user doesn't want to play in the BIOS anyway. But for those of us that have *real* networks to work off of, and have real needs in OS installation and hardware maintenece, nothing is better than OpenFirmware systems.
Javascript + Nintendo DSi = DSiCade
I link up charities with corporate donations of computers. The hottest machines in my inventory are P3-733 machines from IBM's NetVista line which are reasonably legacy free. Why won't they move? Nobody wants the things because they can't hook up their parallel printer or scanner, serial modem, etc, etc. They've just got 5 USB ports for hooking up externals. Yes, there are USB adapters for all of these things and I've tried to give them away with the machines but even then people look too skeptical at such an obviously deficient computer that it doesn't even have a printer port. If you could wave a magic budget wand and replace every component at the same time then these new legacy free systems rock. Otherwise there aren't many takers. Sad, but true. No, you may not have one; I can only redistribute them to a 501c3.
Why do we need a GUI on the BIOS configuration ? Why do we need to replace a simple, perfectly usable and debugged PC start up system ? I can think one major reason: they need to implement a fancy pants encryption and verfication system from the moment power hits the chip so that a secure computing environment (DRM) can be implemented. I think the GUI config tools are a lame marketing bullet point to make you think you need this stuff. I just don't get it.
Yes, but with anti-lock, disc brakes, electronically controlled suspension, and tires that weigh half what their counterparts just ten years ago did...
We're still using Turing machines, true, but without tapes...
That having been said it's a lot easier to slap RS232 on a device than it is USB... but that's just a question of time before the USB chips become as cheap/easy as UART's...
I've been running a legacy-free computer since 1987 when I bought my first Mac.
See a trend here? Seems the x86 world is just now getting around to solving legacy issues that Apple solved long ago. Welcome to the future, folks.
Learn from the mistakes of others. You won't live long enough to make them all yourself.
I'm all for abandoning useless legacy features in "typical" PCs if they make them cheaper and more stable.
For example, abandoning the ISA standard in favor of PCI was overall a good, if a bit late (and contrived, with VESA and EISA, etc), development. Although I regretted losing a few good expansion cards, there was really not much lost beyond sentimental value.
PCI is showing its age, and the transition to PCI-Express (or whatever name it ends up having) will be welcome.
Serial ATA, once it's mature, will be also a welcome change. No need for those big cables in the case, at least.
I've been operating without a floppy disk drive for years now, with only minor inconveniences whenever some BIOS update, old DOS driver or utility demands a "boot disk" the old-fashioned way. There's no reason to assume it's there anymore, and it's a useless expense in both money and space.
Those are good changes. But this is not always the case.
Case 1: Legacy Ports
No more PS/2 ports, no more serial ports? USB and Firewire all the way!!
Sure, sounds great if it works. Except that it almost never does.
USB support in PCs is "decent" now, but it's not 100% reliable, and one can't afford to be left with no input device because the BIOS/OS/random-thing-I-don't-know-of has problems with USB today.
My current PC has a bunch of unused USB ports, but I'm still sticking to PS/2 mouse and keyboards. The reason is that every week or so someone calls me because they have a problem with their computer and it happens to be the USB mouse and/or keyboard which just stops working.
I reduced my "family technical support" calls by 50% just by putting a USB->Serial adapter on my father's keyboards and mouses.
I have the same problem one or twice a month with almost all USB devices I use: printers, cameras, etc. I use USB for them because they need the bandwidth, and because I can afford to tinker with them every so often.
Sometimes all it requires is plugging and unplugging. Sometimes turning the device on or off (printers and wireless devices). Sometimes rebooting the machine. Sometimes it just starts working again without a clear cause. It rarely takes more than 2 minutes, so it's not a problem (if you have a traditional mouse/keyboard with you).
This doesn't apply to basic input devices:
I don't need MB/s of bandwidth to type or move a cursor, and I certainly can't afford to lose my input devices because the USB controller, or BIOS, or the OS, or whatever causes the problem had a bad hair day. Particularly because it can take more than 2 minutes to fix when you have no input devices to figure what's going on.
On the other hand, if my PS/2 keyboard stops responding, I know it's a hardware issue. Replace keyboard, or, at worst, replace port.
This is just within the Windows world. I had enough trouble getting USB support working in a few Linux installations not to bother trying anymore, as I haven't really needed to.
Maybe it works flawlessly and automatically from some distributions now, but I wouldn't risk anything going wrong there.
Basic I/O has to work flawlessly, and in PCs, even in brand-new machines, I just don't trust USB that much. Maybe it's precisely because of the legacy support, I don't know, but I think it's been long enough for BIOS/OSes/etc to get it right.
Case 2: Legacy BIOS
They want to make the BIOS an OS? What happened to small and simple?
I guess having it programmed in C would be an advantage, and I'm sure there are technical limitations with the current BIOS technology that could use an update, but I'm worried about this approach.
If you need an OS, that's what the OS is for. If you need diagnostic utilities et al, get an OS and run diagnostic utilities on it.
Why do you need to put this in the firmware layer? Firmware should be small and stable. If something fails in firmware, you're normally in deep trouble.
A BIOS is not something
Freedom is the freedom to say 2+2=4, everything else follows...