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.
Why?
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 project 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:
* double click on My Computer
* select View, Options
* then click on the View Tab
* remove the check from the box next to "Hide MS-DOS file extensions for file types that are registered.
* click Apply, then close.
The second thing you need to do, is learn something about the standard/registered file extensions.
The accompanying chart 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...
* this page has an extensive list of Windows 95 file names and functions http://web2.airmail.net/darylc1/windows.htm
* and this one has a search engine on which you can query 1,353 file extensions. http://kresch.com/exts/ext.htm
One final note on the subject of file extensions
The recent spate of Trojans/viruses spotlighted a deficiency in the general computer user'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 Word Macros.
| 386 | Windows Virtual Device Drivers |
| AAM | Macromedia Shockwave |
| AI | Adobe Illustrator file |
| ARC | Archive file |
| AVI | Video Clip |
| BAK | Backup File |
| BAS | Visual Basic Code Module |
| BAT | Batch File |
| BCF | Briefcase File |
| BMP | Windows bitmap |
| CAB | Cabinet file |
| CDB | Clipboard file |
| CDR | Corel Draw 3 - 7 |
| CFG | Configuration file |
| CHK | ScanDisk file |
| CLS | Visual Basic class module |
| COM | MS-DOS executable file |
| CPI | International code Page information |
| CPL | Control Panel applet |
| CPP | C++ compiler source file |
| CUR | Windows Cursor file |
| DAT | Data file (used by several applications and system functions) |
| DCX | FaxView document |
| DFB | Dbase/FoxPro database file |
| DLL | Dynamic Link Library |
| DOC | MS Word document |
| DOT | MS Word template file |
| DRV | Device driver |
| DWG | AutoCad file |
| EPS | Encapsulated PostScript |
| EXE | Executable file |
| FH3/FH4/FH5/FH6/FH7 | Freehand 2.0 - 7.0 |
| FON | Bitmapped font file |
| FOT | Font metric for TrueType fonts |
| FRM | Visual Basic form file |
| FXD | Winfax file |
| GEM | Graphics Environment Manager |
| GIF | Graphics Interchange Format |
| GZ | Gzip file |
| HLP | Help data file |
| HQX | BinHex archive format |
| HTM/HTML | Hypertext Markup Language file |
| ICO | Windows icon |
| INF | Setup Information file |
| INI | Configuration settings file |
| JPG/JPEG | Joint Photographics Expert Group Format |
| KBD | Keyboard layout data |
| LGO | Windows logo driver |
| LIB | Static-link library file |
| LNK | A Desktop shortcut |
| LOG | A log file |
| LZH LH | Arc compressed file |
| MAK | C/C++ make file |
| MDB | Microsoft Access database |
| MID | MIDI sequence |
| MIF | MIDI instrument file |
| MOV | QuickTime movie |
| MPG/MPEG | Motion Picture Experts Group video format |
| NLS | Natural Language Services driver |
| OCX | ActiveX control |
| PCX | PC Paintbrush file |
| Portable Document Format | |
| PDX | Paradox database |
| PIF | Shortcut to MS-DOS program |
| PJ | HP PaintJet file |
| POT | PowerPoint template |
| PPD | Postscript Printer Description file |
| PPT | PowerPoint Presentation file |
| PRV | Extensis PagePreview |
| PS | PostScript output file |
| PSD | Adobe Photoshop file 3.0/4.0 |
| PWL | Password list |
| QT | Quicktime movie |
| RA | Real Audio data fie |
| RAM | Real Audio file |
| REG | Exported Registry patch file |
| RTF | Rich Text Format file |
| SCR | Screen Saver file |
| SHS | Scrap object |
| SIG | Signature file |
| SIT | Stuffit archive |
| SPL | Shockwave Splash file (also Windows 95 extension for temporary printer spool files) |
| SWP | Swap file |
| TAR | Unix archive format |
| TIF/TIFF | Tagged Image File Format |
| TMP | Temporary file |
| TTF | TrueType Font |
| TXT | Text file |
| UU | UUencoded file |
| VBX | Visual Basic Custom Control File |
| VXD | Virtual device driver |
| WAV | Waveform file |
| WCM | WordPerfect macro file |
| WKS | Lotus 1-2-3 worksheet |
| WMF | Windows Metafile |
| WP/WPD | WordPerfect Files |
| WPG | WordPerfect Bitmap |
| WPT | WordPerfect Template file |
| WRI | WordPad file |
| XBM | X Window System bitmap |
| XLM | Excel macro file |
| XLS | Excel worksheet |
| XLT | Excel template |
| XLW | Excel Workspace |
| XWD | X Windows System dump |
| Z | Compressed Unix file |
| ZIP | Compressed archive file |
This article is furnished as a benefit of our membership in the Association of Personal Computer User Groups (APCUG), an international organization to which this user group belongs. The author, Carol Daniels is a freelance writer and editor specializing in science, technology computers, computing, business, health, medicine, food and agriculture. She is on the Management Committee of the Melbourne PC User Group and a member of APCUG's Board of User Group Advisors.
For more information on the Tulsa Computer Society click here