It's supported, but only available to subscribers. If you're not logged on as a subscriber, it redirects you to the insecure version.

Nice touch, eh?

Yeah, I have a Motorola Milestone (GSM version of the same device) and it is also 550 MHz. My battery is about 30-40% when I plug it in at night, and if an app decides to misbehave, the phone is sometimes flat even before I get home from work.

MCPR.exe hasn't failed for me yet. That said, with regards to resource hogging -- I'll give you that. One of the many reasons we have switched to Sophos at work. 50 PCs now running Sophos -- we're never looking back.

In a perfect world, we'd be running some kind of Unix that doesn't encourage you to run as root all day long, but until that day arrives, we're stuck with supporting those that haven't yet made the switch.

My apologies — the end of my message seems to have been cut off. I can't remember what I was going to write, but hey. You should get the gist.

You do not need to sign up for Internode's IPv6 trial.

All you have to do is change the domain in your username from "internode.on.net" to "ipv6.internode.on.net". Then, make sure IPv6 is enabled in your pppd config (e.g. check the "IPv6" box on your router, or on Debian, just add a line "ipv6 ," to /etc/ppp/peers/dsl-provider) and you should be away.

You'll also need to run a DHCPv6-PD client if you want the static /60 subnet, which if you bought one of the IPv6-ready routers from Internode wiil already be supported. Or on, say, Debian, just install the wide-dhcpv6-client software and you will get the static /60 subnet they are allocating.

(If your router is anything like my OpenWrt one, if you don't run DHCPv6-PD, you'll get a dynamic /64 address on the ppp0 interface, but nothing on your LAN interface. You *could* then manually advertise that on the eth0 interface

You've never heard of SSH keys?

I've never typed a password to log on to any of my machines with ConnectBot. Nor am I planning to. There is no need for a password remembering feature (nor can I imagine there ever will be), because SSH keys makes that redundant.

And hire a qualified electrician to install cabling inside the house, to reinforce your point.

People try to draw a line between electric cabling and using a computer, based on the false assumption that if you screw up electric cabling you die, whereas if you screw up your own computer, it only affects you.

That's a bogus assumption because the reality is that we have this thing called the "Internet". You know, a community of networks, where computers actually talk to each other. And, you know, cause havoc on each other's networks.

If you crash the car in your own paddock, that's okay -- it's your car, and your paddock. But if you drive irresponsibly on the road, especially a highway, which is a commons of road drivers, you suddenly have the ability to cause a lot more harm.

It's the same with the Internet. If you own a PC, and you connect it to the Internet, you have a responsibility as a citizen of the Internet (and the world, pretty much) to be conscientious to others. An infected PC is not a laughing matter — you’re actively harming someone or something whether you’re aware of it or not. If you're not prepared to take due care, you should be treated like the cops would treat you if you were an unlicensed drive — you shouldn't be allowed on the Internet.

It's a social problem, not a technical one.

Yes, the data going through the USB may be digital, but as I have shown, the USB power, not data can cause interference.

For a vinyl ripper, the USB power has the ability to interfere with the audio while it's still analogue, before its conversion to digital prior to being sent over USB.

One would hope a vinyl ripper would use an external source of power and shield the USB well.

In theory, maybe, but in practice I get noticeable EM noise from USB.

I have a USB-powered speaker (uses a normal 3.5 mm jack for audio) for my computer which also has an earphone port on the side, which is handy. It used to be part of a HP LCD monitor (L1740 if you must know), which had a USB port for plugging the speaker into for power. Why you would design the speakers to get their power off a monitor they were specially designed to be an accessory for with USB I do not know -- surely a normal DC plug would have done the job. But I digress.

Anyway, I no longer use that monitor, but kept the USB speakers. To power them, I now plug them directly into my desktop PC's USB port for the power. Now when I plug my earphones into the side of the speaker bar, there is a noticeable hum that is directly correlated with the CPU usage. Normally it's like "bzzt zzt zzt". But if I drag a window around or compile something, it goes like "BZZT THH ZZT THH ZZT TTH ZZT".quite loudly.

It does that with two separate motherboards with two separate PSUs. However, it does not do that if I plug the USB power into my Eee PC (laptop) instead.

So there you have it. USB does suffer from EM noise. If you have a solution, I'd like to know -- it drives me batty some days.

The GP did use AD. Re-read this quote from the GP, my friend:

If that doesn't convince you, read this quote, then read up up on the description for the likewise-open package.

If the GP wasn't using AD, then what the heck were they doing using a tool that provides "authentication services for Active Directory domains"?