Path: utzoo!attcan!uunet!samsung!usc!wuarchive!psuvax1!psuvm!jkt100
From: JKT100@psuvm.psu.edu (JKT)
Newsgroups: comp.sys.amiga
Subject: Re: Mountlist help!!
Message-ID: <90281.001421JKT100@psuvm.psu.edu>
Date: 8 Oct 90 04:14:21 GMT
References: <90280.143404JKT100@psuvm.psu.edu>
Organization: Penn State University
Lines: 24

In article <90280.143404JKT100@psuvm.psu.edu>, I say:
>
>I have a 2091 controller with a Quantum 105S.  I just created 2 partitions
>and both partitions work PERFECTLY if I have the 2091 automount them.  BUT
>one of those partitions is for A-Max II and I do not want it to automount
>and clutter my WB when I am not running A-Max.  I've tried to create a
>mountlist for it, using the info I saw in HDToolbox, and I've ALMOST
>got it working, but A-Max II still won't recognize the partition when I
>use my mountlist entry below:
>
(my mountlist entry deleted - see previous posting if you want to
 look through it...)

I wanted to add some things I forgot to include in my previous post.
First, when I have the AMAX: partition automount, I do know it is unit
3.  I found this out by typing CD AMAX: in the CLI and I got back an
error requestor saying "Not a DOS disk in Unit 3."  Nevertheless, I have
tried units 0-9 in the mountlist just in case...   No luck.

So if I can rule out the unit=3 line, anyone know what else might be
wrong with my mountlist entry?  The command I use to mount it is simply
MOUNT AMAX:  After this command, it DOES show up in the device list when
I type INFO.  A-Max II just doesn't like it.  Thanks for any ideas,
                                                         Kurt