For anyone curious about real world practical usage:

H:\>mountvol
Creates, deletes, or lists a volume mount point.

MOUNTVOL [drive:]path VolumeName
MOUNTVOL [drive:]path /D
MOUNTVOL [drive:]path /L
MOUNTVOL [drive:]path /P
MOUNTVOL /R
MOUNTVOL /N
MOUNTVOL /E

In practice, there's really no testing to be done. Either it works or it doesn't. I use UMA any time I'm in a rural area with WiFi available and it's been very useful to me. Unfortunately, calls on UMA still debit your monthly wireless minutes, which I find to be appalling. I can understand some charge, but the standard rate is way too high considering I'm not using their wireless network for transit.

A PIX or an ASA would really be more appropriate. I picked up a 50-user ASA 5505 a while back, but it cost me $300.00

Your analogy does not follow. When you watch the cursor, you're watching the "object" that's directly controlling the input, just like when you watch your fingers on an iphone or the blue highlight on a Blackberry Storm.

The tactile response is mouse clicks and the fact that you're moving a physical object around. Is that so hard to grasp?

For one thing, there's tactile feedback with a mouse. It's pretty substantial. Secondly, yes. I'd argue that you look at your mouse pretty constantly, because most people tend to watch the mouse cursor when they're using the mouse.

Ahh, I see what he was getting at. I remember learning that during a NetBackup training course (I believe Netbackup used a modified version of Sybase as a back end for a while?). Thanks for reminding me.

Sybase? I think you mean MSSQL. Also, the Eclipse IDE actually has some capability for .NET development now. This can easily be used with open version control solutions. It may not be good for developers who are doing large projects, but for anyone developing plug-ins for office apps or something similar it's not too bad.

There are a lot of reasons, beyond performance, why this is a bad idea. I'm well aware that it's done, but I would expect it won't be common for too much longer. How do you handle an e-discovery request when you have PSTs in unknown locations? What happens when a lawyer knows you have something and then it gets lost? It's nasty territory to be in.

I'd wager that Microsoft is willing to do this because the .pst format is becoming irrelevant. Medium and large businesses already want nothing to do with them due to issues with performance and management. That leaves small businesses and a small number of home users. With hosted exchange options becoming more common among small businesses, the need for .pst files is going away very quickly.

Actually, getting Windows to 640x480 is no easy task now.

So true. I don't want to think of how many hours I've spent searching "windows expose" on google. There are a couple of crappy implementations, but none of them are really usable. I used switcher for a while, but it only works if you set the process priority to maximum and it's difficult to make that preference persistent.

The biggest thing that I want is the ability to switch to the desktop, do work, then switch back to my active windows. In Vista and prior it can't be done. I'm not sure about 7, because I haven't been using it for very long.

That cleared it up for me. Thanks.

For those of us who don't have experience with how the big ISPs connect to each other, could someone shed some light on the situation? Does peering involve a physical connection or is it just down to advertising routes? I thought having your routes advertised was a good thing.

Or you could get a marketing person with a brain that would serve them ads for new software, a wireless N router or anything else that might be useful after one upgrades their computer.