Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!mordor!sri-spam!ames!husc6!uwvax!uwslh!lishka
From: lishka@uwslh.UUCP (Christopher Lishka)
Newsgroups: comp.sys.amiga
Subject: Re: Path problem ???
Message-ID: <302@uwslh.UUCP>
Date: 5 Feb 88 01:44:09 GMT
References: <2789@omepd>
Reply-To: lishka@uwslh.UUCP (Christopher Lishka)
Organization: U of Wisconsin-Madison, State Hygiene Lab
Lines: 44

In article <2789@omepd> hah@inteloa.UUCP (Hans Hansen) writes:
>
>	I have a real puzzler !  I have a diskette that WHILE inserted into
>either df0: or df1: or df2: (I have 3 3.5" drives) causes my A1000, running
>1.2 released S/W to forget all known paths.  As soon as I remove the diskette
>from whichever drive I have it in my Amy remembers?? what paths ARE!!! 
>
>Hans  (The guy with a kinky diskette)	hah@inteloa.UUCP
>					hah%inteloa.intel.com

	Being a new Amiga user, I recently had a problem similar to
this that stumped me for a bit.  I was setting up some disks to work
with C, and one of them was bootable.  So I went through the
prerequisite copying of all my workbench disk parameters and such to
the main C disk, created my workdisk, renamed them, did an install,
and hit a Ctrl-Amiga-Amiga.  Fine...everything is going smoothly...until
it starts reading in the startup-sequence, and then proudly exclaims
something like "ConMan: unknown command."  Hmmmm...I rebooted with my
regular workbench, checked the C directory on my C-bootdisk, and
ConMan was there.  SH*T!  What the hell was going on?  Tried it a few
more times, recopied ConMan, tried it with different commands, etc.
and the only response I got from the bootable C disk was "...command
not found" (not the words the Amiga used, but you get the picture).

	And then it hit me: being a bit naive I had called my C
workdisk the name "C", so when the machine booted up it had two
volumes in df0: and df1:, and one of the volumes was called "C:".  So
when it came time to look for a command, it checked C: (now also known
as df1:) and didn't find everything.  A bit confusing and rather
subtle.  Also pretty funny when you think about it.

	The moral: make sure that none of your disks have the same
name as a volume (I believe that is the terminology); i.e. don't call
your disks "L", "C", "S", or "RAM" because they probably will mess
things up.  I don't know if this is your problem, but it is worth checking.

	Between the little nuances of UNIX, AmigaDos, MSDos, and
whatever other OS's you use, it is more that enough to drive a
programmer batty.

						-Chris
-- 
Chris Lishka                    /lishka@uwslh.uucp
Wisconsin State Lab of Hygiene <-lishka%uwslh.uucp@rsch.wisc.edu
"What, me, serious? Get real!"  \{seismo, harvard,topaz,...}!uwvax!uwslh!lishka