Since Windows 95 was released many computer users have tidied up their computing lives by hiding away those messy little bits than hang off the end of a file name. They haven't done away with file extensions, they've just put them out of site, and out of mind. My life isn't tidy. So not surprisingly my files are displayed, extensions
and all. Let's face it, I use my Windows desktop just like I use my actual desktop, to store bits and pieces,
works in progress, notes, reminders, things I want to read, stuff I want to check, all there right up front,
where I can't miss it. And just like my actual desktop, things accumulate on my Windows desktop, until I've
used up all the space. Then I start chucking things into the recycle bin, or putting them away into folders.
So it is equally predictable that I choose to display file names with those messy little bits right out in
the open. Because it's extra information for me to use. And I do use it, all the time. This isn't the most earth shattering tip, but it does make my computing life easier. How? That depends on whether we are talking about standard extensions, or my own, "custom" extensions. I use custom extensions as a simple, at-a-glance version control system. By glancing at the extension I can tell exactly how far I have gone in the writing or editing process for any submission on my computer. I use a different code for different types of projects too. So by using the standard sorting options, I can group files by type, project and status, along with the standard name, date and size choices. I use standard extensions as a safety net to prevent me from deleting needed files. Also, because I don't allow any programs to launch attachments automatically, keeping file extensions visible is a secondary safeguard against me accidentally executing an infected file. I also use file extensions for the purpose for which they were intended, to tell me what sort of file I'm about to open, view or use in some way. Yes, I know Windows can do that for me. But not with the kind of flexibility I need. I often have several programs that "can" be used to open a particular file type. Which program I want to use--for example, on *.GIF or *.HTM files, depends on what I want to do with the files. Visible extensions make it easier and quicker for me to choose the right file, and then the right program. Finally because I try to use a common name for all elements of a project, extensions, nestled right up there, next to the file name, make it much easier for me to see which compost files are notes, documents, tables, definitions, archives, or library items. If you want to put this sort of information to work for you, you'll need to do two things. First you'll need to adjust your file display settings to show extensions (file types). Here's how you do that:
Table 1 will help you with that--it's not exhaustive, just a selection of the more common file types I've come across. No need to memorise them either, just keep the table or this article where you can find it. Now, if you are really keen, and want to study file types
The recent spate of Trojans/viruses spotlighted a deficiency in the general
computer users's understanding of the term "executable file". Many messages that were accurate on all other
counts, identified executable files as ".EXE" files only. While *.EXE files are, most definitely executable,
they are not the only executable files. Word documents can contain executable macros, and although they may
seem like a blast from the past to some, *.BAT and *.COM files are also executable. As are *.SHS and *.VBS
files, and of course, MS Office documents containing macros.
Reprinted from the May 1999 issue of PC Update, the magazine of Melbourne PC User Group, Australia |