On (27 Jan 95) [EMAIL PROTECTED] wrote... > From: Lord Blackadder <[EMAIL PROTECTED]> > Date: Fri, 27 Jan 1995 15:51:09 +0000 (GMT) > > > How about if we had a list of standard file extensions? > > This has got to be the best f*cking idea I've heard all week - let's get > to it! > Dan
First let's define what NOT to use! > .ARC - Rumsofts Archiver The .ARC extension is actually copyrighted! It belongs to System Enhancments Assosiations ie the people who wrote ARC/UNARC originally. examples of other .ext's that should not be used especially when placed on a ftp site are... .ARK CP/M variant of the .ARC archive .LBR Originally CP/M specific library file somtimes used in MS-DOS specific Apps to store a library of screen or printer drivers and are not compatable with the original format. .LZS .LSS .LZH .LHA all are produced by the LHxxxx series of archivers .PMA a CP/M specific variant of the LHarc archiver .ARJ probably copyrighted archive extension name .ZIP " " " " " .PAK " " " " " .ZOO possibly " " " " .?Q? .?Z? .?Y? are produced by the CP/M equivilent of unix compress/gzip and are single files compressed with a squeeze/crunch/freeze utility respectivly. .BAS is normally a non-tokenised BASIC source listing .COM .EXE .CMD are binary executables *normally* .BAT .SUB .JOB are normally ASCII command batch files .PIC .PCX .GIF .FIF .TIF .JPG .IMG etc are all pre-defined extensions that infer a definate file structure to transfer graphics that should not be used unless the file complies with the required structure. The use of any of those for Sam specific file-types on ftp sites and BBS's will at the least cause confusion and wasted ftp's and at worst some of them could cause machines to crash or even legal action for copyright or regestered trademark infringmant! > .CDE - Code files > .SCR or maybe .PIC Screen files > .PRG - Program files or we could adopt the MS-DOS *:-\ concept .EXE > .TXT or maybe .DOC - obvious > .DAT - Generally data file > These are all logical - can anyone come up with some more. .EXC for auto-executing CODE files maybe but never .EXE Why does the SAM *NEED* three character filename extensions on its own filesystem? The normal directory command shows exactly what type each file is as it already has the filetype in compressed form, why waste the name-length? I agree to Brian's suggestion that the *SAM specific* archival program should use a different extension .ARQ seems non-contentious with other file-ext's:-) Regards Johnathan ... Beware the Inertia of the Status Quo - Robin Clay -- |Fidonet: Johnathan Taylor 2:2501/307.9 |Internet: [EMAIL PROTECTED] | | Standard disclaimer: The views of this user are strictly his own.
