Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!decvax!ima!mirror!xanth!kent
From: kent@xanth.UUCP (Kent Paul Dolan)
Newsgroups: comp.sys.amiga
Subject: Re: Buglist for V1.2
Message-ID: <852@xanth.UUCP>
Date: Sun, 19-Apr-87 04:21:44 EST
Article-I.D.: xanth.852
Posted: Sun Apr 19 04:21:44 1987
Date-Received: Sun, 19-Apr-87 17:58:17 EST
References: <8704181043.AA14428@cogsci.berkeley.edu>
Reply-To: kent@xanth.UUCP (Kent Paul Dolan)
Distribution: world
Organization: Old Dominion University, Norfolk Va.
Lines: 64
Keywords: two disks mounted in df0:
Summary: Here's one I haven't seen reported yet.


Environment:	WorkBench 1.2, 2.5 Megabytes, 1 disk drive (df0:).

Problem:	Info function reported two disks plus ram: all mounted,
		copy from ram: copied to wrong disk.

Reproduce by:	I don't know.

Details:	I scratched the surface of disk Communications_1.2: right
		in the middle of the vt1002.4 executable.  I saw that the
		disk was scratched, so brought up workbench 1.2.  I wanted
		to clean the disk drive, so I ran v1.1 format, twice, since it
		writes all the tracks before verifying any, and thus gives
		a longer cleaning cycle than does the 1.2 format.  The first
		time, after the write cycle, I got impatient for the track
		zero verify to fail (didn't know if it would) and so popped
		the disk out of the drive, getting the expected error.  The
		second time I let format time itself out.
		
		I put workbench 1.2 back in and copied :c to ram:c, to have
		working code available for the rest of the process.  I never
		reassigned C:, just typed ram:c/function all the time.
		I made a directory called ram:communications_1.2.  I deleted
		c/vt1002.4 from the damaged disk, and then did a
			copy communications_1.2: ram:communications_1.2 all
		to recover most of the files from the damaged disk.
		
		Next, I copied vt1002.4 from a back-up disk into 
		ram:communications/c.  Next I formated a new communications_1.2
		disk.  Since format is in system under 1.2, that started with
		my workbench_1.2 disk in the drive, and I put it back when the
		format was done, to shut the drive up while I put a label on
		the new disk.
		
		I did an info, just for heck, to see how busy my ram: was
		getting, and noticed, but didn't think much about, ram:,
		workbench_1.2:, and communications_1.2: all being shown as
		mounted.  Now I issued
			copy ram:communications_1.2 communications_1.2:
		and the machine promptly began to write all over my working
		copy of workbench_1.2:.
		
		Grrrrr.  Another disk to rebuild.  (BTW, diskcopy takes 3
		passes on one drive systems even with add on memory.  Yuk.)

Sorry to make this so drawn out, but a lot went on here, and I have no idea
which of my bits of idiocy managed to elicit one from the system, but there
should be some reasonableness check built in to convince the workbench that I
probably didn't have two floppies in the same drive at once.

Isn't home computing fun!   Kent.

--
The Contradictor	Member HUP (Happily Unemployed Programmers)  // Yet
								    // Another
Back at ODU to learn how to program better (after 25 years!)    \\ // Happy
								 \// Amigan!
UUCP  :  kent@xanth.UUCP   or    ...{sun,cbosgd,harvard}!xanth!kent
CSNET :  kent@odu.csnet    ARPA  :  kent@xanth.cs.odu.edu
Voice :  (804) 587-7760    USnail:  P.O. Box 1559, Norfolk, Va 23501-1559

Copyright 1987 Kent Paul Dolan.			How about if we keep the human
All Rights Reserved.  Author grants free	race around long enough to see
retransmission rights, recursively only.	a bit more of the universe?