Slashdot Mirror

jsse writes: "Robocode is a game that teaches you Java while you build killer Java-Battle-Bots that fight each other to the death in an arena. The newest Robocode league in town, Robocode Rumble has just been launched. It's a joint effort by alphaWorks and developerWorks. If you're just getting started with Robocode, don't miss "Rock 'em, sock 'em Robocode!" An excellent hands-on starter. In addition "Secrets from the Robocode masters" a collection of tips from the experts, presents more advanced techniques and strategies to help destroy all and be the Java-Battle-Bot King. Previous slashdot story on Robocode can be found here."

Dejected @Work writes "IBM developerWorks just ran this article on Verizon's partial 3G network set up in some areas of the US, most of the North East. The article goes into some good technical background about these fatter pipes called Express Network. Has anyone tried this out?"

Maxim writes: "An unprecedented billion-atom calculation has enabled a team of IBM and Lawrence Livermore National Laboratory (LLNL) scientists to demonstrate a major advance in using supercomputers to simulate the strength of materials. Check out the video."

Lots of people and institutions have apparently good claims on the invention of the digital computer, and many more when that's reduced to just a broader definition of "computer." Few, though, have a better claim to what we think of as a digital computer than John Mauchly. Not as famous as Turing or von Neuman, and with his name no longer on any current computers, it's likely you've never heard of Mauchly (rhymes with "broccoli") -- but you almost certainly have heard of his most famous machine, and the first general-purpose large-scale electronic computer: the ENIAC. Filmmaker Paul David sorted through decades of newsreel footage, old videotape from the vaults at UNISYS and photo archives, and shot hours of new interviews with many of the people who watched and participated in Mauchly's quest. The result is a documentary film which lets the players tell their own stories: it's put together so smoothly that no omniscient narrator appears, or needs to. If you're interested in the history of computing, technology in general, or even World War II, The Computer and the Skateboard is engrossing. (Read on for more.)

The skateboard? The Computer part of the title is easy: though there are a lot of computers and proto-computers mentioned in the film, the one at its core is the ENIAC, or Electronic Numerical Integrator and Computer, the number-crunching roomful of glowing tubes and toggle switches built at the University of Pennsylvania's Moore School of Electrical Engineering in 1944.

So where does the skateboard come in? One clue to the title is flashed on-screen at the beginning of the film, an intriguing snippet from the ill-fated Omni magazine, which asserts that both the computer and the skateboard are artifacts which "accidentally dispose a culture toward anarchy." While that's a intriguing, enigmatic idea, there's another more concrete reason why he put "skateboard" in the title.

Though it's recounted only skeptically by the film's living subjects, there's a story that Mauchly invented the skateboard -- wheels mounted on a plank, as classroom apparatus rather than recreational transport -- and this claim is part of what inspired the film. David says that he "began research for this documentary around 1995 when a longtime friend mentioned casually that his granddad built the first computer. A couple of weeks later he told me that he also constructed the first skateboard. The computer thing was kind of impressive but the skateboard --that's really something." Mauchly certainly wasn't riding halfpipes, but in an alternate universe, he'd probably be a good candidate.

Mauchly didn't create the ENIAC on his own, of course: academic collaborator and eventual business partner J. Presper Eckert (his name contributed half the name of their Mauchly-Eckert Computer Co.) was an electronic genius in his own right, and would be worthy of a documentary all to himself. An enthusiastic corps of programmers, engineers and others helped, too, as did generous Army funding for the project -- but the ENIAC's conception belongs to Mauchly.

Cast of Characters Since he began researching the film in 1995, David managed to meet with many of the key participants in the history of ENIAC, and each of them fills in some of the story.

• Joe Chapline, technical writer, Eckert-Mauchly Co. Chapline calls ENIAC "The second miracle of Philadelphia," and muses aloud whether the electronic computer or the forging of the United States Constitution has had the greatest impact. Chapline played a key role early in the development of what would become ENIAC by introducing the Army to his inventor friend Mauchly, and then later by writing the ENIAC's specification document (all from diagrams, and according to Chapline in a single burst of intellectual clarity) which allowed programmers to exploit its potential.

• John Mauchly's widowed wife Kay Mauchly. Kay Mauchly (introduced on-screen only as "programmer") is one of the stars of the film, describing matter-of-factly in several of the interview segments the steps which led her husband from early investigations in meteorology to the creation of ENIAC and the machines that followed. Mrs. Mauchly is no outsider looking in: she was one of the handful of women recruited by the to work on the Army's differential analyzer, soon to be supplanted by Mauchly's electronic analyzer. Once Mauchly and his brainchild became involved, she became one of the machine's first programmers, and this is how she met her eventual husband.

• Through the miracle of videotape, John Mauchly himself. Though Mauchly died more than 20 years ago, he's represented in the film with clips taken from a 1977 videotaped interview, as well as in newsreel footage from decades before.

• Mitchell Marcus, professor of artificial intelligence at Penn. Mitchell is one of the few subjects in the film who did not participate in ENIAC's creation, but his lucid explanations of Mauchly's machine architecture is a welcome addition.

• A number of other Mauchly friends and associates who tell stories about Mauchly's enthusiastic shepherding of his years-long project.

A timeline twisted by war. John Mauchly's research into weather patterns in the 1930s required some of his students (he was teaching at Ursinus College) to tediously enter logged weather data by hand, an error-prone process under the best of circumstances. Kay Mauchly describes the key insight that led to the development of the digital computer:

"He ran into a problem, and that was the students who were copying the data didn't always copy what they saw, and if they were using an adding machine they didn't always copy down the exact answers they got, they sometimes reversed the numbers and so on. So he thought, 'Gee there must be some way we can develop some kind of a computing machine' -- well, he didn't call it a computing machine -- 'but any kind of a machine where there would not be so much operator intervention.'

"At the same time, there were some of his student friends who had been students with him at Ursinus College, who had gone into nuclear physics. They were in the process of counting cosmic rays, which occur about one million per second. How were they doing this? They were doing this by little electronic counters which they made themselves, using electronic tubes. So John went to several of their laboratories and observed this going on, and his feeling was 'Hey, if you can count cosmic rays, then you can count anything. It doesn't make any difference what you put into the machine.'"

This insight led him to construct his own counting devices at Ursinus, also using vacuum tubes. On video, Mauchly recounts his thoughts:

"If you can count, [if you can] distinguish pulses which are occurring at rates which are sometimes as close together as a millionth of second ... If you can keep track of these things, it seemed obvious to me that those same abilities of vacuum tube circuits could be used for just the mere act of computation. Generate your own pulses your own way, not have them necessarily become the result of some measurement of nature's cosmic rays or nature's nuclear experiments. Just generate your pulses on purpose to represent numbers. and then you get these counting circuits, or scaling circuits as they called them, to operate on these numbers, get them to multiply and divide as well as add and subtract. Why not? And nobody had any answers to that 'Why not?'"

In the summer of 1941, Mauchly took an electronics course at University of Pennsylvania, which is where he met J. Presper Eckert, who was in charge of his electronics laboratory course. Because Mauchly had already learned on his own many of the things taught in the course, he and Eckert found themselves free to spend most of their class time talking computers and tinkering. The Moore School offered Mauchly a teaching position after that summer, and he accepted.

Like many other colleges and universities, the University of Pennsylvania shifted focus in the early 40s from pure academics to the war effort. An Army team from the Aberdeen Proving Grounds moved in to take over Penn's Differential Analyzer in June 1942, and things began to speed up. The Differential Analyzer was a huge mechanical calculator which the Army was using to do trajectory calculations, one by tedious one.

Kay Mauchly recounts: "When Mauchly saw what the Army was using the differential analyzer for, he thought 'Oh my goodness, that's the sort of thing they could use for my computer, if they could ever get it built."

Prompted by his friend (and then-boarder) Joe Chapline, in 1942 Mauchly proposed applying his expertise with electronics to speed up the calculations being done by the Army -- an analyzer built with tubes would be far faster than any mechanically operated one. The proposal was accepted by Lt. Herman Goldstine, who headed the Aberdeen team. Mauchly and Eckert set to work, and the result was the ENIAC, a massively parallel computer that could manipulate numbers faster than any alternatives then available.

Patent Fight In 1946, the war over, the Army decided to publicize their electronic marvel, and institutions all over the world began to inquire whether they could build ENIACs of their own -- and the Moore school was suddenly famous. Looking beyond academic uses, the University of Pennsylvania saw the commercial possibilities of electronic computers. Irven Travis, a professor who had returned from his wartime service in the Navy to resume his position overseeing all patents at the University, pressed the two to sign over the commercial patent rights.

Given 10 days to sign away their rights to commercial production of similar machines, Eckert and Mauchly balked. The Moore school fired the pair -- and though they had no jobs to go to, they soon created jobs by forming their own company in a building on Philadelphia's Walnut street. Eckert and Mauchly's decision to go off on their own ended up clearing much of the department, because many of the brightest faculty decided to go with them. Even with uncertain prospects, they knew that Mauchly and Eckert were onto something.

Professor Mitchell describes the firing and subsequent departmental losses as "as fundamental error that we're still recovering from." The details of this fight are reason enough to seek out this movie for their insight into the value (and difficulty) of preserving the rights to one's own work.

The rest of the story. The company that the two stubborn Penn professors founded was called Electronic Controls Company, and in 1948 renamed Eckert-Mauchly Computer Corporation (EMCC). Among other things, the company introduced the world's first magnetic (rather than punchcard) computer storage. No matter how innovate, though, business was thin -- not surprising in a world where digital computers were still more curiosity than necessity -- and was sold in 1950 to Remington-Rand. Rather than ENIAC, the machines the company made now were called UNIVAC.

Mauchly left the company to form yet another (Mauchly Associates), and to head two more companies (Dynatrend and Marketrend) before his death after surgery in 1980.

This isn't Wargames. The Computer and the Skateboard is not a fancy movie in content or presentation. The story is laid out plainly, not padded with teases -- the drama is mostly in the background. The actual actors may not be universally humble, but they seem too down-to-earth to make a big deal about contributing to the Allies' victory in World War II, or changing nearly every aspect of the modern world.

There also aren't many special effects, outside of a funky sci-fi sounding background audio track; transitions between scenes are simple, and most of the interviews are quite static; the viewer is left to interpret the subjects' words on his own, with no Leonard Nimoy intoning conclusions or trying to smooth together different aspects of the narrative. David is obviously limited in parts by the quality of the original sources he was able to track down (especially the audio), and it's to his credit that he let these segments stand, because they add historical glances which might otherwise remain locked in company vaults.

The style and subject matter taken together mean that (no surprise) this film has a niche audience. I doubt my sister would much enjoy it, but my electrical-engineer father sure got a kick out of it. Watching this movie is like watching an intelligent professor tell a story without overtelling it -- your concentration will be rewarded.

The film is available for institutional viewing at $295 and at a lower price for home video. The title is also available in university libraries and repertory video stores. Readers interested in the ENIAC's history may also want to look at this excellent collection of documents available from IBM, one of the many good online resources available.

MJArrison writes "Yahoo is carrying a Reuters story about a laptop that isn't much more than a foldable LCD screen. It's very small screen 6.7"x5" appears to be a strange black on green monochrome, so it better be cheap. It's made by Samsung and will be launched in Korea first." It's a start; I can't wait for them to integrate an IBM 701cs style camber for both screen and keyboard. T. adds: Rather than a general-purpose laptop, it looks like this is being pushed as an specialized device for reading e-texts.

UncleJosh writes "Today's NY Times (free reg rq'd) has a story about the first Kuiper Belt Object (KBO) with a moon, 1998 WW31. The hubble telescope has been used to get information about the size and orbit of the moon. Seems lots of things have moons. Coming more than 20 years after the discovery of Pluto's moon Charon the discovery of a KBO with a moon also follows the discovery of asteroid Ida's moon Dactyl and other moons of asteriods."

UncleJosh writes: "The New York Times (free reg rq'd) has a story about a $25-30 fee to be added to the price of a new PC to cover the cost of recycling it. Sort of like a bottle deposit, but you don't get the money back." What if I just want to buy the case?

Dejected @Work writes: "At JavaOne it was hinted that Sun and the Apache Software Foundation have worked out how open source software could participate in the JCP (Java Community Process) but the precise resolution was not disclosed. This developerWorks interview with Jason Hunter (Apache rep. for the JCP) clear things up a little and specifically explains what this means for open source developers and the JCP."

Irish writes: "One of the biggest complaints about Web services is the security issues. IBM and Microsoft just released specifications describing Web Services Security (WS-Security), or enhancements to SOAP messaging to provide quality of protection through message confidentiality and authentication. There is an developerWorks overview document and a whitepaper describing this Web service security model."

Irish writes: "One of the biggest complaints about Web services is the security issues. IBM and Microsoft just released specifications describing Web Services Security (WS-Security), or enhancements to SOAP messaging to provide quality of protection through message confidentiality and authentication. There is an developerWorks overview document and a whitepaper describing this Web service security model."

ChunKing writes "The Computer History Simulation Project is a loose Internet-based collective of people interested in restoring historically significant computer hardware and software systems by simulation. The goal of the project is to create highly portable system simulators and to publish them as freeware on the Internet, with freely available copies of significant or representative software. I can't wait 'til someone fixes me an OS/390 emulator to remind me of the days when I used to be an Ops Analyst for a major bank..."

totallygeek writes "Redefining the term vaporware, research scientists at Lost Alamos and Lawrence Livermore Labs detonated two computer simulations. ASCI White, the world's fastest supercomputer, ran the simulations of nuclear explosions. Scientists can now study nuclear weapon replacement components without violating the nuclear test ban, in effect since 1992. Each simulation used more than 6.6 million CPU hours, which would take home machines 1000 years to complete. The data for each experiment was equivalent to 35 times the information available in the Library of Congress. ASCI White currently operates at 12 teraflops, but by early next year, Los Alamos expects to operate at 30 teraflops. The seven month research project ended last Friday, and now the system is ready for use, after its sucessful testing."

PeterMAN writes: "If you want to learn how to share your systems on a heterogeneous local network and how to use it to compare and test applications on different operating systems and architectures, then take a look at these two articles that compare SSH, remote X, VNC, and other technologies as ways of remotely running applications." That link is to the second part of the series; here's the first installlment.

PeterMAN writes: "If you want to learn how to share your systems on a heterogeneous local network and how to use it to compare and test applications on different operating systems and architectures, then take a look at these two articles that compare SSH, remote X, VNC, and other technologies as ways of remotely running applications." That link is to the second part of the series; here's the first installlment.

Irish writes "This IBM developerWorks article discusses the theoretical underpinnings of SOAP's type system. Its a good article for anyone who wants to learn more about SOAP's programmatic support or to simply better understand Apache's SOAP."

Irish writes "This IBM developerWorks article discusses the theoretical underpinnings of SOAP's type system. Its a good article for anyone who wants to learn more about SOAP's programmatic support or to simply better understand Apache's SOAP."

Ches2000Pro writes "Via Wired News, IBM has announced a new Linux scripting environment called SashXB. From their description: SashXB is an open source application environment that exposes native functionality to JavaScript. It's ideal for web developers with HTML and JS skills who want to write full-featured native applications, as well as experienced programmers who'd appreciate the convenience of rapid application development. SashXB is being released under the LGPL license." It's not exactly new, but seems to be quite usable now. Has anyone used this?

Ches2000Pro writes "Via Wired News, IBM has announced a new Linux scripting environment called SashXB. From their description: SashXB is an open source application environment that exposes native functionality to JavaScript. It's ideal for web developers with HTML and JS skills who want to write full-featured native applications, as well as experienced programmers who'd appreciate the convenience of rapid application development. SashXB is being released under the LGPL license." It's not exactly new, but seems to be quite usable now. Has anyone used this?

quick_dry_3 writes: "IBM's ViaVoice list moderator says that "IBM continues to support the Linux community by integrating Linux into all key products. The Linux desktop dictation product is still available and will continue to be sold. At this time, we have decided to discontinue our SDK for developing desktop Linux voice-enabled applications." Full copy of email is here."

Frank writes: "There's an interview over at developerWorks Linux Zone with Linus's latest lieutenant Marcelo Tosatti. He talks about what it takes to be the maintainer of the Linux kernel, what his plans are for 2.4 and his favorite hack." If you missed it, you may also want to visit the answers Marcelo gave to Slashdot readers.

Frank writes: "There's an interview over at developerWorks Linux Zone with Linus's latest lieutenant Marcelo Tosatti. He talks about what it takes to be the maintainer of the Linux kernel, what his plans are for 2.4 and his favorite hack." If you missed it, you may also want to visit the answers Marcelo gave to Slashdot readers.

Frank writes: "There's an interview over at developerWorks Linux Zone with Linus's latest lieutenant Marcelo Tosatti. He talks about what it takes to be the maintainer of the Linux kernel, what his plans are for 2.4 and his favorite hack." If you missed it, you may also want to visit the answers Marcelo gave to Slashdot readers.

drfickle writes: "Although there has not yet been a formal announcement, David Merrill has stepped down as the Linux Documentation Project Collection Editor & Review Coordinator and appointed Joy Yokley Goodreau as his replacement. Joy has been very active in the LDP community for well over a year and has represented the LDP at many Linux conferences. She is an employee of the IBM Linux Technology Center on the LDoc team."

drfickle writes: "Although there has not yet been a formal announcement, David Merrill has stepped down as the Linux Documentation Project Collection Editor & Review Coordinator and appointed Joy Yokley Goodreau as his replacement. Joy has been very active in the LDP community for well over a year and has represented the LDP at many Linux conferences. She is an employee of the IBM Linux Technology Center on the LDoc team."

Suhani writes "The dream of using your remote control to interact with television broadcast shows has finally become a reality, thanks to interactive television (iTV). Here, John Papageorge explores the opportunities and challenges of creating applications for the set-top box platforms (such as OpenTV, AOLTV, and Worldgate) that allow for interactive television."

squiggleslash writes: "IBM's Developer Domain is hosting an article on how to port software written for OS/2 over to Linux. Bottom line -- it's easy, as long as you use an abstraction layer. Hopefully this'll mean the huge amount of OS/2 software out there will start being ported, helping make Linux even more ready for the desktop. Lotus, are you reading?"

jscribner writes "Data these days tends to an unstructured form, be it text (like the web, email, or books), spoken word, or even in DB's with unique organization (and thus a discrete language). There's a new article on Unstructured Data in Think Research; it's an overview of the challenges, progress, and potential rewards in this area. I'm leaving on your doorstep because, to me, it's a good launching point for discussion of several interesting possibilities: /. as a minable DB of ideas, email identified by interpretation rather than keywords, emotive XML, etc."

jscribner writes "Data these days tends to an unstructured form, be it text (like the web, email, or books), spoken word, or even in DB's with unique organization (and thus a discrete language). There's a new article on Unstructured Data in Think Research; it's an overview of the challenges, progress, and potential rewards in this area. I'm leaving on your doorstep because, to me, it's a good launching point for discussion of several interesting possibilities: /. as a minable DB of ideas, email identified by interpretation rather than keywords, emotive XML, etc."

jscribner writes "Data these days tends to an unstructured form, be it text (like the web, email, or books), spoken word, or even in DB's with unique organization (and thus a discrete language). There's a new article on Unstructured Data in Think Research; it's an overview of the challenges, progress, and potential rewards in this area. I'm leaving on your doorstep because, to me, it's a good launching point for discussion of several interesting possibilities: /. as a minable DB of ideas, email identified by interpretation rather than keywords, emotive XML, etc."

AustinSaltLick writes: "Open Source projects can now compile their code on the first compiler farm in the open source community that runs on an IBM eServer zSeries server. The zSeries is the world's first dedicated Linux mainframe server. This article explains how project administrators can request access for their team."

AustinSaltLick writes: "Open Source projects can now compile their code on the first compiler farm in the open source community that runs on an IBM eServer zSeries server. The zSeries is the world's first dedicated Linux mainframe server. This article explains how project administrators can request access for their team."

sl956 writes: "We all know that anybody using the words 'tamper resistant' to describe a software-based solution is incompetent at best. But some of the big players in the DRM field are believing in software-only protection schemes (see Cloakware, Hitachi, IBM or Intel). A mostly unnoticed paper presented to CRYPTO'01 (Santa Barbara, CA, August 19-23, 2001, LNCS vol.2139) *proved* the impossibility of efficiently obfuscating programs. It is the mathematical proof of the impossibility of a software-only DRM system on an untrusted client such as a PC. There are also a lot of interesting theoretical side-effects. You can read the html abstract here, or the postcript full paper here." The paper is from last year, but that doesn't make its conclusion less interesting. (Of course, even hardware isn't always all that secure, either.)

martial writes: "Available on the IBM developperWorks web site, is the 3rd part of the "OpenSSH key management" series (Part 1, Part 2) discussed in /. some time ago"

martial writes: "Available on the IBM developperWorks web site, is the 3rd part of the "OpenSSH key management" series (Part 1, Part 2) discussed in /. some time ago"

martial writes: "Available on the IBM developperWorks web site, is the 3rd part of the "OpenSSH key management" series (Part 1, Part 2) discussed in /. some time ago"

martial writes: "Available on the IBM developperWorks web site, is the 3rd part of the "OpenSSH key management" series (Part 1, Part 2) discussed in /. some time ago"

Dejected @Work writes "If wireless technology ever kicks off you may be getting spam phone calls - "hot deals 10 feet away". If so you will have to use techniques like RMI, BrightMail, and latest e-mail filters to keep phone spam free. This article examines some of these tools and programming concepts."

Todd Heidesch writes: "'IBM announced it has created the world's fastest semiconductor circuit, operating at speeds of over 110 GigaHertz (GHz) and processing an electrical signal in 4.3 trillionths of a second.' IBM expects the new technology to be pumping out 100 gigabit/sec network switching chips by the end of the year (on an optimistic schedule, I presume)." dr_zeus contributes a link to this Reuters article running on Wired (also fairly thin) on the release, writing: "Granted, this isn't a PC chip, but one wonders how long it will be before we hear 'dude, you've got a 110GHz Dell!'"

Saint Aardvark writes: "Something interesting from the SecurityFocus Honeypot mailing list: a couple of honeypots for spammers. This message has a link to a how-to page for setting up a Sendmail honeypot to trap spammers, and the status page for a honeypot in Moscow that's trapped spam meant for >1.7 million recipients. The author mentions using a honeypot in conjunction with the Distributed Checksum Clearinghouse -- this seems like a great way identify both spammers and their messages."

And C-Moan writes: "Wireless spam volume is likely to increase in the coming years. But smart use of spam-fighting measures can go a long way toward eliminating the problem. This article provides info about the latest crop of e-mail filters and enhanced mail client options, as well as two roll-your-own programming platforms that could help keep your in-boxes spam free."

wrinkledshirt writes "IBM DeveloperWorks has an article here about coding with KParts, KDE's component architecture. It's a little thin, but given that no single component technology has claimed victory yet for Linux, just thought this might be an interesting read for some. It also might lead to some good discussion comparing people's experiences with KParts, ORBit ^? , Bonobo ^? , or Kylix ^? 's CLX..."

An Anonymous Coward writes: "DeveloperWorks has an interesting article about compiling Java apps to run as native appplications on the target machine without the need for a JVM."

An Anonymous Coward writes: "DeveloperWorks has an interesting article about compiling Java apps to run as native appplications on the target machine without the need for a JVM."

Irish writes "The wireless world had some surprises last year. WLANs, with easy but unsecure bandwidth, may disrupt the adoption of regulated/limited 3G networks. DoCoMo's iMode surprised many gaining 27 million users while Europe was disappointing. This developerWorks article takes a look at the big wireless security stories of 2001 and tries to offer some predictions on the future."

A reader writes "The new Z-series mainframe for Linux, which costs $400,000 and is aimed at processing transactions at large businesses, is IBM's first mainframe computer sold without IBM's traditional z/OS mainframe operating system. More info at the IBM zSeries page" This is something that IBM and others of Big Iron vendors of *NIX have said - as Linux grows in maturity, they want to replace their *NIX with Linux. However, there's still work to be done in that area.

Music listener and Slashdot author chrisd has prepared a review of the new Nex II CF based mp3 player from Hong Kong based Frontier Labs. He declares it the best MP3 player he's owned, so read the whole review if you'd like to learn more. I have always preferred the Compact Flash memory format. I'm not alone, either. It's always baffled me that the MP3 player market has been dominated by SmartMedia-based players. It's clearly a throwback to the first Rio that Diamond released a few years back (which I still have in a box somewhere in the basement); It's always been a big problem in my mind. I find the SmartMedia format to be too small in capacity and flimsy in packaging to be appropriate for serious music listening or digital photography.

In digital photography, I've pretty much stuck with the CF-based Nikon Coolpix series of digital cameras, so I had scads of CF memory cards lying about. I also have an IBM Microdrive which I use when taking TIFFs using the Nikon. So I wanted an MP3 player able to handle not just Compact Flash, but also the Microdrive. The Microdrive is tricky because it both consumes much more power than solid-state CF cards, but also is slower to respond and larger, demanding the taller CF-II slot.

Until the i2go ego, there wasn't a mp3 player that could handle the Microdrive. I had owned and immediately given away the original, incredibly flawed, RCA Lyra because it simply stank so much I couldn't stand to own the thing. If RCA wants to send one of the new ones, I'd be pleased to check it out, but the shoddy original made me vow never to give RCA more MP3 player money.

The i2go ego (still sold some places, although I think the company that made it is defunct, look look here to see one) wasn't all bad. It played, and it acted as a pretty basic voice recorder, and it allowed for two CF cards to be inserted, at least if you bought a funny daughter board. But its build quality was such that it would spontaneously lose power if jostled. Also, it had the most annoying bug ever: the player would remember the card's contents from before, even if you changed said card's contents. It would try to play them too. It also -- at random --wouldn't notice songs that were on the card. It was very annoying, besides which it was enormous for an MP3 player.

I had been checking out the Nex II for a few months and with a long trip coming up, I decided I needed a MP3 player for the trip. I wanted to have a player that was smartly designed and able to run the microdrive. The Nex II seemed to fit the bill, so I ordered one (with a 256mb card included) for $239 (plus $15 shipping).

It arrived promptly 3 days after order from Frontier Labs' shop in Hong Kong; I've been using it for about a week now, and I have to say it's the best player I've ever owned. The display, an LCD (the letters are not blurry on the actual display) with a blue electro-luminescent backlight, is very readable, and the interface is super easy to use, with a rocker button on the right for track control above the volume buttons and the stop and the "fn" button on the left, under the headphone jack.

Conveniently, the Nex II also acts as a plain vanilla USB drive, so I can upload and download songs (or other files) under Linux with no problem. You can chose from two types of display while the song is playing (status or spectrographic display), which is fun. I stick with the status screen, which shows all pertinent information, including track length, quality in kbps, song title and time elapsed. The player has been able to handle any data rate I've thrown at it, and the specs says it can play WMA files, but I can't verify that. Also, I was able to pass the card to the camera and back with no problem, as neither the nikon nor the player are too controlling of the disk format.

Physically about the size of thick deck of playing cards, the Nex II allows you to change the color of the area around the LCD by sliding in thin colored pieces of glossy paper. You can buy more of these skins for $10, including the unfortunately named "mutant sperm" skin. It also comes with a snappy little neoprene case which has transparent portions covering the LCD and buttons so you can see what's up.

Despite all its good points, the Nex isn't perfect, it lacks some basic features, namely any sort of external power connector. You must always run it with 2 AA batteries. Mind you, it lasts 12 hours when using solid state CF and 5 when using a microdrive, so this is less inconvenient than it sounds. Also, the included headphones are not to my taste at all. The battery cover should be redesigned completely so the latches aren't as flimsy -- every time I change the batteries, I picture scotch tape in my future. Many would probably also like to see it be able to play Ogg Vorbis files, but that wasn't a deal breaker for me.

Another quirk of the Nex II is that to play Microdrives well, you need to load the 1.4(m) firmware available from the FrontierLabs website. It's odd that they didn't make this the default firmware, as the 1.4m firmware seems to work equally well with solid state cards and microdrives, while the firmware it ships with works poorly with microdrives.

So if you're looking for a decent mp3 player, you should check it out. The Nex II is an excellent value, and it sounds terrific.

Frank writes: "This series of articles on developerWorks comprises a complete guide to better programming in Perl. In this fourth installment, Teodor introduces functional programming and several essential Perl idioms important for Perl programmers looking for speed and elegance in their code, such as the map() and grep() functions, and the Schwartzian and Guttman-Rosler transforms."

Frank writes: "This series of articles on developerWorks comprises a complete guide to better programming in Perl. In this fourth installment, Teodor introduces functional programming and several essential Perl idioms important for Perl programmers looking for speed and elegance in their code, such as the map() and grep() functions, and the Schwartzian and Guttman-Rosler transforms."

WAD-Dawg writes: "Linux security is a topic of much concern and investigation lately. Here are a few white papers that cover important Linux security topics. This white paper contains informtaion, code examples, and proven strategy on securing Linux Servers for Service Providers. And this article covers PKCS #11 openCryptoki, an API that is rapidly becoming the de facto, non-Windows-platform industry standard for interfacing between cryptographic hardware and user space applications. Both are very well written and provide important and timely information on Linux security."

WAD-Dawg writes: "Linux security is a topic of much concern and investigation lately. Here are a few white papers that cover important Linux security topics. This white paper contains informtaion, code examples, and proven strategy on securing Linux Servers for Service Providers. And this article covers PKCS #11 openCryptoki, an API that is rapidly becoming the de facto, non-Windows-platform industry standard for interfacing between cryptographic hardware and user space applications. Both are very well written and provide important and timely information on Linux security."

chasmosis asks: "My company's decision to go with a heterogeneous SAN setup has our DataCenter Engineers banging their head's against a wall. Interoperability nightmares include matching microcode for various components to achieve some level of stability. One of the biggest current problems is with SAN connected StorageTek tape libraries, anytime a server scans the SAN for devices (ie on NT system boot, an AIX machine running cfgmgr , etc...) it accesses the tape drives, interrupting any currently running backups. What have others done to make their SANs more dependable, especially for backups/tapes?"