Category : Assembly Language Source Code
Archive   : DOCFILES.ZIP
Filename : BAC.DOC

Output of file : BAC.DOC contained in archive : DOCFILES.ZIP

BAC (Backup Directory) John Dickinson
Command Magazine, Vol 4, No 17
Copyright 1985 Ziff-Davis Publishing Company

Purpose: Backs up all (or selected) files in a
directory to hard or floppy disks, permitting
disk changes when target disks become full.

Format: BAC [d:][path]filename[.ext] [d:][path]

Remarks: Unlike the DOS COPY command, BAC.COM permits
you to change (formatted) target disks when
backing up files to disk. Furthermore, it
only backs up files whose date stamp is later
than those of identically named files on the
target disk. Unlike BACKUP, BAC does not
change the setting of the archive bit. Also,
files copied with BAC.COM are fully usable at
all times; they do not need first to go
through a RESTORE process.

BAC.COM supports the use of global (* and ?)
characters in filenames and extensions. It
does not, however, permit you to REName files
during copying.

Example: You are working at a PC AT with a hard disk
drive (C:) on which you keep your copy of
BAC.COM, and you want to back up all the .DOC
files stored on a 1.2-Mb floppy disk (drive
A:) onto regular 360K disks (drive B:).
Since these .DOC files will require
approximately 600K, you must have two
formatted blank floppy disks ready to use in
drive B:. From the C> prompt you enter


When the first target disk in drive B: is
full, you will be prompted to change disks.


1. BAC.COM compares the date stamps of
identically named files and will not
overwrite a newer version with an older
one. This may cause files to be skipped
if you omit to keep your date/time

2. Requires DOS 2.0 or later.

  3 Responses to “Category : Assembly Language Source Code
Archive   : DOCFILES.ZIP
Filename : BAC.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: