Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!mips!dimacs.rutgers.edu!seismo!uunet!ns-mx!umaxc.weeg.uiowa.edu
From: bheil@umaxc.weeg.uiowa.edu (Brian Heil)
Newsgroups: comp.sys.amiga
Subject: Re: MSH cry for help!
Message-ID: <3244@ns-mx.uiowa.edu>
Date: 17 Nov 90 19:25:21 GMT
References: <26992.27451cc3@kuhub.cc.ukans.edu>
Sender: news@ns-mx.uiowa.edu
Lines: 24

From article <26992.27451cc3@kuhub.cc.ukans.edu>, by 2flntopaz@kuhub.cc.ukans.edu:

[ My original post deleted ]
 
> 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

So this is (in the words of NASA) nominal behavior and I have to live with it?

I guess I didn't understand that part of the man page (or I read it too fast),
my fault.  Considering the price I think I can live with it!  Just out of 
curiosity does this also happen with Crossdos?

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!