TCS - Put File Extensions To Work For You

Put File Extensions To Work For You

by Carol Daniels, Melbourne PC Users Group
From the August 1999 issue of the I/O Port Newsletter

Since Windows 95 was released many computer users have tidied up their computing lives by hiding away those messy little bits that 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.

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.

386Windows Virtual Device Drivers
AAMMacromedia Shockwave
AIAdobe Illustrator file
ARCArchive file
AVIVideo Clip
BAKBackup File
BASVisual Basic Code Module
BATBatch File
BCFBriefcase File
BMPWindows bitmap
CABCabinet file
CDBClipboard file
CDRCorel Draw 3 - 7
CFGConfiguration file
CHKScanDisk file
CLSVisual Basic class module
COMMS-DOS executable file
CPIInternational code Page information
CPLControl Panel applet
CPPC++ compiler source file
CURWindows Cursor file
DATData file (used by several applications and system functions)
DCXFaxView document
DFBDbase/FoxPro database file
DLLDynamic Link Library
DOCMS Word document
DOTMS Word template file
DRVDevice driver
DWGAutoCad file
EPSEncapsulated PostScript
EXEExecutable file
FH3/FH4/FH5/FH6/FH7Freehand 2.0 - 7.0
FONBitmapped font file
FOTFont metric for TrueType fonts
FRMVisual Basic form file
FXDWinfax file
GEMGraphics Environment Manager
GIFGraphics Interchange Format
GZGzip file
HLPHelp data file
HQXBinHex archive format
HTM/HTMLHypertext Markup Language file
ICOWindows icon
INFSetup Information file
INIConfiguration settings file
JPG/JPEGJoint Photographics Expert Group Format
KBDKeyboard layout data
LGOWindows logo driver
LIBStatic-link library file
LNKA Desktop shortcut
LOGA log file
LZH LHArc compressed file
MAKC/C++ make file
MDBMicrosoft Access database
MIDMIDI sequence
MIFMIDI instrument file
MOVQuickTime movie
MPG/MPEGMotion Picture Experts Group video format
NLSNatural Language Services driver
OCXActiveX control
PCXPC Paintbrush file
PDFPortable Document Format
PDXParadox database
PIFShortcut to MS-DOS program
PJHP PaintJet file
POTPowerPoint template
PPDPostscript Printer Description file
PPTPowerPoint Presentation file
PRVExtensis PagePreview
PSPostScript output file
PSDAdobe Photoshop file 3.0/4.0
PWLPassword list
QTQuicktime movie
RAReal Audio data fie
RAMReal Audio file
REGExported Registry patch file
RTFRich Text Format file
SCRScreen Saver file
SHSScrap object
SIGSignature file
SITStuffit archive
SPLShockwave Splash file (also Windows 95 extension for temporary printer spool files)
SWPSwap file
TARUnix archive format
TIF/TIFFTagged Image File Format
TMPTemporary file
TTFTrueType Font
TXTText file
UUUUencoded file
VBXVisual Basic Custom Control File
VXDVirtual device driver
WAVWaveform file
WCMWordPerfect macro file
WKSLotus 1-2-3 worksheet
WMFWindows Metafile
WP/WPDWordPerfect Files
WPGWordPerfect Bitmap
WPTWordPerfect Template file
WRIWordPad file
XBMX Window System bitmap
XLMExcel macro file
XLSExcel worksheet
XLTExcel template
XLWExcel Workspace
XWDX Windows System dump
ZCompressed Unix file
ZIPCompressed 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



This page has been accessed times.
Tulsa Computer Society 7/10/99
Don Singleton, President
djs@ionet.net