demoedf@iitmax.IIT.EDU (ed federmeyer) (06/15/88)
Here is a somewhat strange phenomenon I've seen- All the CP/M books I've ever seen seem to have a nice table of the file extentions listed somewhere. (You know, foo.BAS is a BASIC source, etc.) Well, I have not seen any such handy list for MS-DOS. (Maybe I just havn't been looking in the right places...) Does anyone have a list of these they might like to share with the other users on the net? (Or if this is too trivial for the net, you can of course E-Mail me...) Thanks in advance... Ed Federmeyer
ubiquity@cs.utexas.edu (Richard Hoffman) (06/16/88)
In article <1159@iitmax.IIT.EDU>, demoedf@iitmax.IIT.EDU (ed federmeyer) writes: > > Here is a somewhat strange phenomenon I've seen- All the CP/M books > I've ever seen seem to have a nice table of the file extentions listed > somewhere... Does anyone have a list of these they might like to share > with the other users on the net? I've seen such lists, but can't find one now. Of course, there's no rule that says files with .exe extensions *must* be executable, but conventions are always useful. Here's a starter list; perhaps someone would like to add to it. EXE Relocatable image COM Non-relocatable image BAT MS/DOS command script SYS Device drivers and configuration files BAS BASIC source FOR FORTRAN source C C source H C include files PAS Pascal source INC Pascal include files CBL COBOL source OBJ Object files ARC Archived files The first five of these are used by the MS/DOS files that come "out of the box"; the others are fairly standard in my observation. -- Richard Hoffman / 5751 Valkeith / Houston, TX 77096 / (713) 729-5716 +- / 12166 Metric Blvd., #122 / Austin, TX 78757 / (512) 823-1822 "Malt does more than Milton can / To justify God's ways to Man." -- ??
baird@cod.NOSC.MIL (John M. Baird) (06/16/88)
Standards...We got lots of standards. Pick your favorite.
Seriously, there are no standards, but here are some of the commonly used
extensions I have noticed in using various commercial software. Even this
list is not complete.
John Baird Naval Ocean Systems Center, San Diego (619)553-2197
-------
EXTENSION WHAT IT (USUALLY) MEANS
ARC Archive file output by some archive program
ASM Assembler input for MACRO Assembler
BAK Editor program backup copy of text file
BAS BASIC language source program
BAT A batch file for DOS
BIN Binary image version of an executable object file
C C language source program
CAL A spreadsheet file in SuperCALC format
CBL COBOL language source program
COB COBOL language source program
COM A program in binary image (non-relocatable) format
CSV A text file in comma separated variable format
DAT A data file
DIF A spreadsheet file in Data Interchange Format
DBF A database file in dBASE format
DOC A file containing documentation for some program
EXE A program in relocatable load module format
FOR FORTRAN language source program
H C language include file
INC PASCAL language include file
LIB Linker library file
MAC Macro input file
MAP Linker listing file
NDX An index file in dBASE format
OBJ Object code output by some complier
OVR File overlay to be used with a EXE or COM file
PAS PASCAL language source program
PIC A graphic file in LOTUS-1-2-3 format
RBS A database file in R:base format
SLK A spreadsheet file in SYLK format
SYL A spreadsheet file in SYLK format
SYS A system file, probably in binary image format
TXT A text file
TMP A temporary file
WKS A spreadsheet file in LOTUS-1-2-3 format
WK1 A spreadsheet file in LOTUS-1-2-3 format
XLC A spreadsheet file in Excel format (also XLM, XLS, XLW)Devin_E_Ben-Hur@cup.portal.com (06/17/88)
some more file extensions:
LIB -- object libraries
MAP -- link maps
00? -- overlays
OVL -- overlays
HLP -- help files
CFG -- configuration files
WK? -- Lotus (& workalikes) worksheets
DB? -- dBase (") data files.
RX? -- Reflex data files
$$$ -- temp files
DOC -- documentation.
TXT -- raw (not rich) text
PRN -- print files
PIC -- PIC format graphics
MAC -- keyboard macros (SuperKey & others)
BAK -- backup files
UUE -- UUEncoded files.
MAK -- make files.loci@csccat.UUCP (Chuck Brunow) (06/20/88)
In article <6575@cup.portal.com> Devin_E_Ben-Hur@cup.portal.com writes: >some more file extensions: > >LIB -- object libraries >MAP -- link maps ... >MAK -- make files. Also, to avoid collisions in porting to Unix: .y yacc script .l (ell) lex script .1 (one) nroff -man script .shar shell archive .z "packed" file .Z "compressed file" .o object file .s assembly lang .sh shell script +IN cpio install file (unix-pc) .a archof linkable routines (lib) .out output of various prog's and others. -- CLBrunow - KA5SOF Loci Products, POB 833846-131, Richardson, Texas 75083 clb@loci.uucp, loci@killer.uucp, loci@csccat.uucp
pozar@hoptoad.uucp (Tim Pozar) (06/23/88)
In article <1018@csccat.UUCP> clb@loci.uucp (CLBrunow) writes: > > Also, to avoid collisions in porting to Unix: > > .y yacc script > .l (ell) lex script > .1 (one) nroff -man script > .shar shell archive > .z "packed" file > .Z "compressed file" Uh, MS-DOS does not reconize the difference between upper and lower case. Oh, well... Tim -- --- ...sun!hoptoad!\ Tim Pozar >fidogate!pozar Fido: 1:125/406 ...lll-winken!/ PaBell: (415) 788-3904 USNail: KKSF / 77 Maiden Lane / San Francisco CA 94108
Ralf.Brown@B.GP.CS.CMU.EDU (06/23/88)
The July PC Magazine's Stephen Manes column "Extension Course: Filenames for
the Future" lists a bunch of extensions.
Excerpted without permission:
"I refer, of course, to the Strongly Typed International Filename Format 8.3
(STIFF 8.3), which was developed years ago but never implented."
"Earlier versions of the STIFF protocol were hampered by being out of touch
with DOS reality. The key to the widespread acceptance of the newly revised
STIFF 8.3 is that it recognizes and locks in forever such accepted DOS
filename extension conventions as these:
.ARC File compressed to avoid your wasting 40 days and 40 nights transmitting
or using it.
.BAK A protective file destined for deletion before you really need it.
.COM A "common" program file that can actually fit into 64K of memory and is
therefore offered at a bargain price.
.DEV File containing satanic cult messages that canhold your hard disk in
thrall.
.EXE A fancy "executive" program virtually unlimited in size and therefore
commanding hundreds of dollars more than the "common" one that does
the same thing.
.HLP A file begging to be put out of its misery.
.ME A file containing absolutely essential last-minute instructions no one
bothers to read.
.WK1 Spreadsheet template that works just once.
.WKS Spreadsheet template that works some of the time.
.$$$ File indicting a programmer's engagement in wishful thinking."
--
UUCP: {ucbvax,harvard}!cs.cmu.edu!ralf -=-=-=- Voice: (412) 268-3053 (school)
ARPA: ralf@cs.cmu.edu BIT: ralf%cs.cmu.edu@CMUCCVMA FIDO: Ralf Brown 1:129/31
Disclaimer? I |
claimed something?| Insert your favorite quote here