david1@aluxe.UUCP (12/15/83)
What type(s) of applications would require 2 disk-drives?
ABN.ISCAMS%usc-isid@sri-unix.UUCP (12/17/83)
How do I use 2 disk drives? 1. Software development (and I mean simple stuff): I keep all my tools -- my utilities, text editor, assembler/disassembler, debugger, backup copies (so I can keep using the same name) on the other disk drive. That leaves me all the one disk for files, and no duplication of utility files. (Even better since I implemented CPMUSER in my CP/M, and my system now automatically looks to Drive A and then User Area 0 for files. (I do the same for complicated stuff too, but complication alone doesn't drive the idea of using 2 drives. 2. Assembling a special disk full of goodies from a collection of many (I habitually keep different type files (.ASM, .COM, .DOC, .PAS, .C, .TXT) on different backup disks. Sorting through them to assemble a set of applications for a friend (all Public Domain) is very simple when I can leave the donation disk in one drive, and stuff the others in and out of the second drive, searching (with MDIR) all user areas as I will. 3. Working with a MONSTER file (e.g., MDM715.PRN!!) -- now, I have 8" DSDD drive and a nice little 5 Megger HD, but... IF I only had a couple of 250K or 350K 5 1/4's -- well, a monster file couldn't even be ASSEMBLED on one of those wee little rascals without distributing .ASM and maybe .HEX and .COM on one, and that bug sucker .PRN on the second. 4. You don't believe in backups? Sure is a pain with only 64K (well, darn sight less TPA) and 250K and up of disk! 5. When one starts eating disks, you always got another right there! Regards, David Kirschbaum Toad Hall
delong@uiucuxc.UUCP (12/17/83)
#R:aluxe:-124900:uiucuxc:3700077:000:513
uiucuxc!delong Dec 16 09:12:00 1983
/***** uiucuxc:net.micro / aluxe!david1 / 8:34 pm Dec 15, 1983 */
What type(s) of applications would require 2 disk-drives?
-----------
A typical example would be a project management package using
the critical path method. The programs would be on drive A, while the
data would be on drive B. Often the program is too large for a 64K
machine. So the program is broken into smaller chunks(overlaying).
Carl DeLong {decvax,ucbvax}!pur-ee!uiucdcs!uiucuxc!delong
{ihnp4,pur-ee}!uiucdcs!uiucuxc!delongandree@uokvax.UUCP (12/20/83)
#R:aluxe:-124900:uokvax:3400027:000:594 uokvax!andree Dec 18 16:06:00 1983 /***** uokvax:net.micro / aluxe!david1 / 8:34 pm Dec 15, 1983 */ What type(s) of applications would require 2 disk-drives? /* ---------- */ Except for things that just won't fit on one drive, none. Anything you can do on two drives you can do on one. On the other hand, many of those things will be MUCH slower. The best example is backing a disk up (a must for all applications). Try backing up a 200K disk on a 16K machine with one drive. Similar comments apply to coping files from one disk to another without doing a complete copy. This may not be possible under some systems. <mike
Seiler@MIT-XX.ARPA (01/06/84)
From: Larry Seiler <Seiler@MIT-XX.ARPA> Copying files between disks is moby hard without two drives. Two drives also makes it possible to keep your application software on one disk and your data files on multiple other disks, instead of having to keep your application program on each and every disk that has a data file (or else swapping disks around after loading the program, which is impossible if the program itself swaps to and from disk, as most do). I have 20 or 30 disks of text files; if I had to keep a text editor on each that number would nearly double. Enjoy, Larry -------