Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!caen!kuhub.cc.ukans.edu!2flntopaz
From: 2flntopaz@kuhub.cc.ukans.edu
Newsgroups: comp.sys.amiga
Subject: Re: MSH cry for help!
Message-ID: <26992.27451cc3@kuhub.cc.ukans.edu>
Date: 17 Nov 90 16:19:31 GMT
References: <3240@ns-mx.uiowa.edu>
Organization: University of Kansas Academic Computing Services
Lines: 37

In article <3240@ns-mx.uiowa.edu>, bheil@umaxc.weeg.uiowa.edu (Brian Heil) writes:
> Well, I'm stumped!
> I got the messydisk (msh) file-system from the fish disks and installed it
> and mounted MSH:  No problems so far.  When I cd to the disk using SKsh
> builtin cd I get an error [msh:: can't change to directory (8)] so I used
> the cd command from a standard WB disk.  This works and I can read/write stuff
> to this disk without problems.  The problem comes when I remove the msdos disk
> from the drive (unit 1) and stick in an amigados disk.  The drive whirrs and
> gronks (that's right I have a 1000 and I'm very attached to that gronking!) 
> and I get a system requestor that says...
>                       
>                       Messydos volume
>                       
>                       has a Read or Write error
>                       retry               cancel
> 
> hmph! something is not working right here!  If I select retry I get the
> requestor back.  If I select cancel it goes away and the disk (an amiga disk
> in df1:) is normal.  
> 
> Any body have a clue as to what's going on here (any body have the same thing
> happpen to them)? 
> 
> Brian Heil                           )              University of Iowa
> bheil@scout-po.biz.uiowa.edu         (      College of Business Administration
> bheil@umaxc.weeg.uiowa.edu           )        Computing Services Organization
>                       AMIGA   There is no substitute!

In the (ahem) manual it says that when you have inserted an MSH: disk and then
remove it and insert an Amigados disk directly after it that MSH: and 
Amigados both try to identify it at the same time.  MSH: can't make
heads or tails of it and gives up (ie. the read/write error) then when
you click the cancel requester it goes away and gives control back
to Amigados.

David Poland
2flntopaz@kuhub.cc.ukans.edu