You are correct. Hydrogen is a method of storing energy, not generating it. Nuke plants are great for producing hydrogen, but any power source can be technically used to do it. I'm not sure that any of the "renewable" sources listed above lends itself to such as well as nuke does, or significantly better than the others.
CowboyNeal is my passport. Verify me.
I love the irony here. Icebrain is asking what snow is, so I can actually say "it's a powdered version of what you have inside your head."
In the US, they are also deductible. Essentially, you subtract the interest you pay on your home from your income. Assuming a 50% tax rate, your 6% home interest rate is costing you only 3% in spendable dollars (not counting principal).
Some people stop there. You have to look at it from the other side though. For every $1.00 you give the bank, the government gives you back $.50. Some people think this is a good idea, even if they could stop paying the interest at all. I haven't figured out why.
Even on a paid-off house, you still have property tax, house insurance, maintenance costs (repairs, lawn care, snow removal...)
Yes, the maintenance costs generally go down if you DIY, but you're still spending time, and that's a cost too. You can also not carry insurance (if you have no mortgage) but that increases the risk of some serious maintenance costs in the event of fire, break-in, etc.
Housing is never really free. Even living in your parents' basement, you've got some form of cost, even if not financial. (Sanity? That's what you get in your shoes when you walk on a beach, right?)
Last octet of the static IP is based on the position in the alphabet of each hostname and the NIC number in the system (Addled =
My suggestion is thus:
1-25 workstations: be creative. Use names that you can remember.
25-100 workstations: create groups of rooms or departments based on themes, and be creative within the themes. Tag hostnames on cases.
100+ workstations: use an asset-tag type scheme, possibly including location (campus-level, not cube-level) information that won't change, and perhaps user. Tag hostnames on cases. Reimage and rename systems when repurposing. Use a database to track specifics of the systems.
At the moment, the least popular answer is the least popular, so it is the only one you can choose without triggering a logic bomb.
Finally, a poll to weed out all the substandard I that has been reading
Fixed that for you.
Problem with Hawkeye is you would die on the operating table while he talked about how much he hates war, violence, etc. Am I right people?!
No, you're not. Hawkeye hates the war, but when he's operating he's operating. Yes he gripes while doing it, but he's one of the best doctors in the Army. The 4077 had the best record of any MASH unit and Hawkeye was the best doctor they had, as confirmed by numerous people numerous times.
Assuming the disk works at all: Work on a clone, not the original.
If you are working on a 2nd generation clone you can afford to take risks in restoring the filesystem. "Oh it that didn't work, fire up another clone and try something else".
This is what I have done using Ghost. There was an option to take a bit-for-bit copy of the drive. It didn't always work, but it would sometimes let you make a backup of the bad drive and restore it onto a good one, and then take a proper ghost image if necessary and recover your files. Any files which were corrupted on the original would still be corrupted, but anything else on the drive was suddenly readable and writable, meaning you can not only recover your data but even repair Windows if necessary and keep using the same drive image so there was typically no need to completely rebuild the system.