Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uunet!mcsun!cernvax!chx400!bernina!neptune!iiic.ethz.ch!umueller
From: umueller@iiic.ethz.ch (Urban Dominik Mueller)
Newsgroups: comp.sys.amiga.datacomm
Subject: Re: Error in DMS !
Keywords: shell, csh, dms
Message-ID: <29300@neptune.inf.ethz.ch>
Date: 10 Jun 91 07:16:39 GMT
Article-I.D.: neptune.29300
References: <91155.143734OEYO8729@TREARN.BITNET> <1991Jun6.083154.18043@rhrk.uni-kl.de>
Sender: news@neptune.inf.ethz.ch
Reply-To: umueller@iiic.ethz.ch (Urban Dominik Mueller)
Organization: Departement Informatik, ETH, Zurich
Lines: 19

In article <1991Jun6.083154.18043@rhrk.uni-kl.de> beckhaus@joan.informatik.uni-dortmund.de (frank bechhaus) writes:
>In article <91155.143734OEYO8729@TREARN.BITNET> OEYO8729@TREARN.BITNET 
>(Cem TURGAY) writes:
>
>>[unable to unpack a .dms file]
>
>Do you use a shell ?  I've seen a similar problem recently with unmashing
>an archive while running CShell 5.xx. In most cases this works without
>problems, but some archives appeared to be corrupted.
>After quitting the shell the same archives could be unmashed without any
>difficulties.

Probably this is only a question of free memory. DMS reports unlogical
errors if it runs out of memory, and freeing the 100K used by csh
might just be enough to make DMS happy. There is a small chance that
csh does something wrong with the call of external commands, but in
that case, the unpacking should go wrong every time.

   -Dominik