Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!psuvax1!vu-vlsi!cbmvax!higgin
From: higgin@cbmvax.UUCP (Paul Higginbottom SALES)
Newsgroups: comp.sys.amiga
Subject: Re: Some A2000/A500 answers
Message-ID: <2497@cbmvax.UUCP>
Date: Wed, 14-Oct-87 14:29:15 EDT
Article-I.D.: cbmvax.2497
Posted: Wed Oct 14 14:29:15 1987
Date-Received: Fri, 16-Oct-87 05:49:38 EDT
References: <4313@zen.berkeley.edu>
Organization: Commodore Technology, West Chester, PA
Lines: 35

in article <4313@zen.berkeley.edu>, bryce@hoser.berkeley.edu (Bryce Nesbitt) says:
> dave@csd4.milw.wisc.edu (David A Rasmussen) writes:
>> traded my 1000 for a 2000 yesterday (make that an A2000, not a B2000).

If you're in the U.S - we've only been selling B2000's, but again, that's
an internal designation and should be dropped, because as far as the U.S
is concerned - the internally designated A2000's have not been sold here.

>> ...is there any way to make it think my external 3" drive
>> is df1: instead of df2:?
> 
> Yes. From a CLI type "assign df2: df1:".  Poof, it is now both df1: and
> df2:!

First of all, I think your code is backward, it would be:
"assign df1: df2:" (assign NEWASSIGNMENTNAME: VOLUME/DIRECTORY).

Not "poof" however, because the assign command assigns to VOLUMES
or DIRECTORIES, but not the DEVICES, and therefore if you
"assign df1: df2:", you're assigning "df1:" to the DISKETTE in drive
and not the drive itself.  Thus, if you do not have a diskette in
the drive it won't work, or if it does, as soon as you change disks
and then request df1:, it will ask for the volume originally in that
drive again.

Apparently all is not lost though because on fish disk 70(I think) there's
a program called AssignDev which assigns to devices and not
volumes/directories.

> If you want a hardware solution, I'm sure there are some jumpers on the
> main board.

Not so.

	Paul.