Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!sol.ctr.columbia.edu!emory!hubcap!jmauric
From: jmauric@hubcap.clemson.edu (Phantom of Adexsi)
Newsgroups: comp.sys.amiga.applications
Subject: Re: MSH - Another Problem
Message-ID: <1991Apr12.141546.13393@hubcap.clemson.edu>
Date: 12 Apr 91 14:15:46 GMT
References: <1991Apr11.161520.11146@decuk.uvo.dec.com>
Organization: Clemson University
Lines: 25

From article <1991Apr11.161520.11146@decuk.uvo.dec.com>, by goldstein@arrods.enet.dec.com (Steve Goldstein):
> In article <5236@uniol.UUCP>, Hartwig.Schieck@arbi.informatik.uni-oldenburg.de (Hartwig Schieck) writes...
>>Hi !
>>I'm trying to run MSH on my AMIGA 500 (Kick 1.2,1MB) but it won't work
>>correctly.
>> 
> 
> I haven't been able to get MSH 130 to work with my A500 and two drive system..
> 

i have had no problems with MSH. make sure you do the following:

		mount msh:
		mount msh1:
		autodiskchange >nil: <nil: msh: msh1: df0: df1:
this way your amiga "knows" what disk you have and in what drive.
also use the PD program TRACKSALV with the above setup and your disks
run faster, smoother, and 99% of the time, error free.
				--john

-- 
===============================================================================
!X!   Music   Edit    Tools    Special  !        999999999 Bytes Free
=====!       !=================================================================
     !#Opera#!______