Friday, June 23, 2006

Norton File Manager: MIA but Missed

Background: More than thirteen years ago, long before Windows95, one of my favorite utilities was from Central Point Software. It was a When Symantec bought Central Point in, what, 1994?, the file manager was retained, and an updated, tweaked version was released for use with Windows95. Then it survived as one component for Symantec’s NT Tools for Windows 1.0 (also including antivirus warez). Occasionally I saw mention of version 2.0, but this never saw the light of day. Clearly Superior. What made (and makes) it superior? Two huge reasons. 1. Unparalleled Options. Thirteen years ago, Norton File Manager (NFM) had better resources for file management that Windows Explorer does today. For example, Windows Explorer offers six categories on its toolbar:
  • File
  • Edit
  • View
  • Favorites
  • Tools, and
  • Help.
By contrast, NFM has:
  • File
  • Disk
  • Edit
  • View
  • Tools
  • Options
  • Security
  • Window
  • Help
So there is a much higher level of granularity in options. Moreover, the menus give the kind of choices you need. For example, under Security you have Permissions, Auditing, and Take ownership. The File menu includes such useful choices as Encrypt and Associate in addition to the standard Windows Explorer offerings. Naturally, there are areas where Windows Explorer has it better (after thirteen years of uncontested, snailspace development), such as an “edit” item and “install”. However many of the differences are more wallpaper than substance, such as the option to set background wallpaper for folders, or the option to display files as thumbnails or in detailed form. Here's what NFM looks like. Just admire the elegant design, and the abundance of options. (Click to enlarge, of course.)

2. Unparalleled Customizeability. Besides a still unparalleled feature set, the other awesome quality of NFM is its extreme customizeability. This means that you can create a menu on either side of the screen (or the top and bottom) and populate it with text or icons. Thus, the style in the screenshot above can be changed to the one below. The content is the same, but the style of presentation has been customized:

(Click to enlarge, of course.)

Not only that, you can edit and rearrange the contents of these toolbars to include anything you want! And the pre-designed selection of icons is quite generous, including ones such as “Undo”, “MS DOS Prompt” and “Compare Files” which I have yet to see in Windows Explorer.

But wait, there’s more! Besides being able to extremely customize the contents and location and style of the toolbar, you can create your own toolbar items! There are generic commands and an interface for creating your own: This means you can create your own commands, and stack them in a toolbar for instant access! Here's what the easy interface for this looks like: And this was thirteen years ago! Will Windows Explorer ever be able to even approach this? This deep orientation for customizeability extends even to the style of the entire program: you have a standard view (used in these screenshots), a view resembling the ancient Windows 3.1 file manager window, an icon view, and XTreeGold mode, which looks like this: (Click to enlarge, of course.) And all this was done half a generation ago, most incredibly prior to Windows95. If there were more competition in the desktop OS market, it’s likely that we would have seen vastly more capable, supple file managers than Windows Explorer. But we don’t, and all we have as the benchmark of excellence is a product which was mature before Windows95 had ever hit the market. In fact, whenever I have reviewed the file management utilities on ZDnet, I have yet to find anything nearly as capable. Look hard for copies; of course it has been long since discontinued. Look at my screenshots, ye mighty, and despair.

Tuesday, June 20, 2006

Introduction: Well, with a copy of VMware GSX Server, I am looking forward to learning its depths, and comparing these with Virtual PC. The benefits are that it permits you to run applications in a rock-solid separate window with their own operating system. So your company might migrate to Server 2003/Windows XP, while some of your legacy applications are only validated for Windows 2000 or even Windows NT 4!. The pocket universe created by GSX and similar offerings is that you may run an application in the operating system of your choosing. The benefits of this are many and clear, both for developers and for infrastructure folks. In my tests, I will be using VMware GSX Server Version 3.0.0, Build 7592, and installing on Windows Server 2003, Web Edition (version 5.2.3790, Service Pack 1), with a generous gig of RAM. First Problem: Challenges with VMWare GSX Server are not long in coming! Even during installation, problems proliferated. Fortunately, this took a single form: over a dozen spurious error messages. These are all identical, and identically unilluminating: “Internal Error 2816. SetupIUnitialization, ActionText, ActionText” These can be safely ignored, according to the VMware support site. Even so, it would have been nice not to have encountered spurious error messages. Fortunately, other users have experienced this problem as well, and their bitter troubleshooting saves us immense headaches. Thus the initial install is eventful but painless. Second Problem: The second problem occurred after the installation was complete. In the Start>Programs VMware>VMware GSX Server folder, there are three items: 1. Manage Virtual Networks 2. VMware GSX Server Console 3. VMware Virtual Machine Console The first one (Manage Virtual Networks) worked perfectly. But when I started either of the other two, I received an error message: Application failure. hr = 0x80040154: (null) This was not transparent, to say the least. But some googling and link-jumping finally yielded a solution: running regsvr32 on two of the program’s DLLs. From the command prompt, I ran the following commands: regsvr32 c:\program files\vmware\vmware GSX server\vmappsdk.dll And regsvr32 c:\program files\vmware\vmware GSX server\vmdbcom.dll After this, everything was working smoothly. More as I work with the application. But running into problems as odd as these so early is scarcely a confidence builder.