Where I sit (and most people aren't like this, I'll admit) I'm tired of it all, I just want it to work.
The alternative, of course, is to simply buy new hardware every year.
android is very good at the write once run anywhere thing, though. its apps really do run on a wide array of very different handsets.
I justwant to know what to look for in the router config.
yes, all thats what you're searching.
the big problem is the 'noob workaround language' you need to backtrace.
some routers have an 'expert mode' that unveils such n00b unfriendly features.
"Is there a name for using dhcp to serve static ip addresses?"
On my router, you go to the DHCP tab and enter what they label a 'static entry'. It maps a MAC address to an IP address and a name (not sure how the name is used, honestly).
I'm using a Linksys RV082 router, which is kinda pricey, but works reasonably well.
At the first corporate desktop support job I had, their entire network was done on an assigned basis; the desktops were configured for DHCP, but you always got the same address because the DHCP servers had a manual entry for every box on the network. I still wonder if the perceived benefits outweighed the administrative headache.
Instead of having to visit every box, you just manage everything in one place. Seems okay to me.
I've preferred it, myself.
It's been nearly ten years now, but I mostly remember it being a headache every time a system moved from one location to another (whether the user was moving, or the box was re-purposed, or whatever). Different teams had jurisdiction over different subnets; moving from one to another was a non-trivial task. I can only guess there was some perceived security benefit.
Is there a name for the concept of setting a dchp server (or more
importantly my wireless router) to hand out the same ip address to a
particular mac address every time it connects. effectively giving it a
static ip without changing anything on the client?
The official name for that is a "reservation." But as has been mentioned in the last few messages, it's often called other things depending on who built your DHCP server software.
You go http://translate.google.com/translate_tts?q=text (where 'text' is the phrase you want it to say) and you get back an MP3. It works with any string up to 100 characters.
Playing with my g1 and reading some articles about it they're getting big into tts and voice recognition, the idea being you can just interact with your device.
The only reason it even half works well is because the sound recorder program is real snappy about getting the data to google. Google can of course churn on it within a second or two and only has to send back a few bytes of text.
Certainly it takes a lot of horsepower, but still would rather do it on my PC which has plenty of horses itself.