Nick, I'm definitely interested in your OpenLCD project.   I started playing around with a 16x2 display last night, starting with the 8 bit interface and then going to 4, and then this morning I was thinking that it should be simple (and cheap) to delegate control to another Arduino chip.  Lo and behold, I stumble upon this thread!  ;D  So, please keep us posted on your progress!  I'd love to see some code in the SF SVN repository... (hint, hint! )

This might be the mother lode: the Micro Gust Thermal Anemometer.

http://www.gellerlabs.com/MGTA%20kits.htm
and
http://www.nutsvolts.com/index.php?/magazine/article/micro_gust_thermal_anemometer_mgta

It would appear that the LM399 diode is obsolete, and I don't see a replacement.

Found another link while searching for "thermal anemometer": http://www.fonema.se/anemom/anemom.html

Here's something that builds on the idea, and has a readable schematic: http://electronicdesign.com/Articles/Index.cfm?AD=1&ArticleID=1978, and there's another version by the same author here: http://ww1.microchip.com/downloads/en/AppNotes/91044a.pdf

I'm not able to find that Cyntec se102 thermistor...

Not to be pedantic, but I googled for "solid state anemometer" and found this: http://www.accessmylibrary.com/coms2/summary_0286-9311675_ITM
It looks like it might fit the bill...

What's the physical wiring of your sensors look like?  There are some app-notes from Maxim/Dallas that discuss overall network topology and the limitations you'll run into with wire length, as well as some mitigation strategies.  I don't have the app-note location handy, however.  I ran into similar problems as you when wiring sensors up in my house and ended up having to run two separate networks.  That may be the case for you, as well...

Awesome! Thanks!

Can you update the playground, please?

I got around the problem by using two 1-Wire buses.

What's the bug?  Where's it detailed?  I ran into a problem where I was unable to resolve more than three devices on the bus, but I thought that was due to a poor wiring job on my part (I have DS18B20s running all over my house with some hefty wiring runs).  I was getting CRC errors when scanning the bus.  Is that what's happening here?  I see that the sample code above isn't performing a checksum...

That looks very similar to the humidity sensors we discussed in this thread:
http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1253792412

I know, but thanks for keeping an eye on me. I just thought your post would be helpful to others, and it moved with no forwarding address.

I'm breadboarding my sensor with a 555 timer right this very moment.  Here goes nothin'…

… aaand that helpful blog post has moved to here: http://1024.cjb.net/2009/10/rh-measurement-resistive-avr/

I'm not entirely sure this is relevant, but I bought a handful of HCH-1000 capacitive humidity sensors thinking I'd be able to drive it with DC and a resistor and measure the charge-time directly with the Arduino's ADC.  Then, after seeing this thread, I went back and re-read the datasheet and see that it's the same design as the sensors mentioned in this thread. *grumble*

I've found a number of interesting discussions and thought I might pass them along:
There's a user on electro-tech-online.com named blueroomelectronics who is building a thermostat kit with humidity sensing.  Here are discussions around his kit and adding that functionality.  This is the schematic of the kit; note the fairly simple arrangement of the 555 timer for generating a frequency based on relative humidity and how it's input to the PIC.  This is a presentation from Honeywell that contains several sample circuits, including a couple that appear to output a voltage based on %RH, using a couple of 555s and a pair of op-amps.

The simple frequency-generating 555 circuit looks like the simplest.  What are your thoughts on that one, Mike?

It took me a while to track this file down, but I think this might be relevant:

1.10 Automatic Sleep Mode
A unique feature of the SanDisk MultiMediaCard/RS-MultiMediaCard is automatic
entrance and exit from sleep mode. Upon completion of an operation, the card enters the
sleep mode to conserve power if no further commands are received in less than five
milliseconds (ms). The host does not have to take any action for this to occur. However, in
order to achieve the lowest sleep current, the host needs to shut down its clock to the card.
In most systems, the MultiMediaCard/RS-MultiMediaCard is in sleep mode except when
the host is accessing it, thus conserving power.
When the host is ready to access the card in sleep mode, any command issued to it will
cause it to exit sleep, and respond.

From ProdManRS-MMCv1.3.pdf, which was originally published by SanDisk; it's since 404'd on their site.