I'm still perplexed that TC has to wait for all drives in the system to respond before it starts. Is there a specific reason for this or is it the result of some library you're using that you have no control over?
If it was displaying free space for every drive in the task bar, I'd understand.
There's so much in TC. Maybe there are some internal variables that get initialized that require all drives to be queried.
You think mapped drives are a problem! Try entering a UNC path to a share on another computer (like \\lucky\d$) in the location box. I get a 150-second hourglass after which nothing has changed. TCMD is the only piece of software on my system which can deal (somewhat) with networking but can't go to a UNC-specified share. Even Explorer, with its tree and list views showing does it almost instantly, updating the tree view in a reasonable fashion (MSWindowsNetwork\WORKGROUP\lucky\d$). Rex, are there no shell or cabinet class windows that will handle all this for you?