OK, me too, I can't resist. I feel I have to say something here. Nothing prepared in advance, even though I have to deal with MS shortcomings all the time. I just had to reload NT because Explorer "Gave Up" trying to display file names, it's most important function. The burns are there all the time, as are the constant upgrades to give you another poorly fleshed out feature. Some persistent shortcomings that come to mind are: Shortcuts, that when browsed erase the "Save As" filename with a useless lnk name. The "Universal Naming Convention" that doesn't work with most utilities, including Find, even though the documentation states proudly: "Supporting the UNC paths when dealing with file names is another way for an application to work seamlessly in a network environment. UNC paths allow logical connections to network devices without the need to specifically reference a network drive letter. The system will be able to locate the network server and path with the UNC name even over a modem connection. The UNC describes network servers and share points on those servers. UNC names start with two backslashes followed by the server name. All other fields in the name are separated by a single backslash." In Unix, NFS and symlinks have been around for (nearly) decades and work with everything. A big "Yeah Rite" on that seamlessness there, Redmondians. Then there's Help and Search utilities that can't find MS documents by their own titles, and on and on.... John A.