Path: utzoo!utgpu!water!watmath!garfield!john13
From: john13@garfield.UUCP (John Russell)
Newsgroups: comp.sys.amiga
Subject: Re: Sys:System vs. System:
Message-ID: <4501@garfield.UUCP>
Date: 20 Feb 88 17:47:58 GMT
References: <7025@agate.BERKELEY.EDU>
Reply-To: john13@garfield.UUCP (John Russell)
Distribution: na
Organization: Memorial University of Newfoundland, St. John's
Lines: 25

In article <7025@agate.BERKELEY.EDU> spencer@eris.berkeley.edu (Randal m. Spencer [RmS]) writes:
>
>why do I have to create a directory in ram called system when I want to
>run diskcopy and format out of ram?  I want to just copy the files and
>then assign System: to Ram:, or is that just me that feels this way?

This used to bug me a little too. It's only with the Workbench (so you can
path ram: from the CLI) but these are about the only things I use the Workbench
for now.

It should be possible to change, eg patch the sys:system/diskcopy that must be
in "format" somewhere (so it can stick it in disk.info), and write a little
program to 'convert' the default tool entries of old disks.

This would of course have the possibility of confusing novice users. However
the way it is now is confusing, especially when you are trying to explain it
to said novice using his WB disk, which is invariably a commercial program
with commands like 'makedir', 'assign' etc left out.

John
-- 
"Fanaticism is all right... as long as you're ALONE! HAHAHAHA!"
		-- Pat Robertson shares a gem of wisdom told to him by Richard 
		   Nixon, and thus becomes the first politician to whom I can
		   honestly apply the term "scares the willies out of me"