NetNews Usenet Archive 1992 #27/NN_1992_27.iso/spool/comp/sys/mac/apps/17476

Internet Message Format | 1992-11-20 | 3.6 KB

Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!src.honeywell.com!The-Star.honeywell.com!umn.edu!csus.edu!netcom.com!netcomsv!salient.com!HarriRehnberg
From: [e-mail] (Salient Software)
Newsgroups: comp.sys.mac.apps
Subject: Re: MacTCP/DiskDoubler/MacLink
Date: Fri, 20 Nov 92 17:56:28 PST
Organization: Fifth Generation Systems
Message-ID: <[e-mail]>
Reply-To: [e-mail] (Salient Software)
X-Mailer: uAccess - Macintosh Release: 1.5v3
Lines: 62

In article <[e-mail]> (comp.sys.mac.apps), [e-mail] ("Sod the proles!") writes:
...
|2. (This one is more important to me) I am using DiskDoubler on my ClassicII
|running 7.0.1+1.1.1 and I LOVE it, but I occasionally find that when I open a
|compressed document, it uncompresses (apparently fine,) but then it _doesn't_
|open it -- it just recompresses it!

The application can't be found or is busy (open).  When you dblclick
on a compressed file the DiskDoubler application is launched by the
Finder to expand the file.  After the file is expanded the DD
application tries to launch the application that the file belongs
to.  If the application is already running then it can't be launched
by DD and have the file name passed.  When the DD application quits
the DDInit (if set to compress immediately) compresses the file.

|I'm doing it _right_ -- i.e. I start the
|application _first_, or I make sure the application isn't compressed (btw I
|wish someone would work on that for future versions -- why can't I open a
|compressed document that can send its launch command to a compressed app which
|will then uncompress and launch and open that document?? it does make DD a
|little more cumbersome for me.) It only happens occasionally, and I've always
|assumed that there was something else wrong (not enough memory, or whatever)
|but I've noticed that it keeps happening, even when nothing else is running. I
|don't notice any rhyme or reason to the things it refuses to open -- i.e. this
|happens with docs, with apps, etc.
|It's a pain because I have to select the item and go to "Expand" under the DD
|menu -- and if I don't remember to select it and compress it again when I'm
|done, DD won't automatically recompress it.
...

Sequence of events for DiskDoubler.

Dblclick on a compressed data file and the DDApp launches expanding
the file.  DDApp then looks for the application the file belongs
to.  If the application is compressed then DDApp expands the application
according to the settings in the DD settings dialog (exp: expand all
related files (same folder as app) or application only).  After the
application is expanded DDApp launches it and passes the file name
to it.

If the appl is already running you MUST use the open file dialog to
open compressed files.

When you dblclick on a compressed file you are using the DDApp.
When you use the open file dialog you are using the DDInit.

Memory can be a factor.  If the files that are causing the problem
are compressed with method A then approx. 450K of memory is required
to expand the file.  If method B is used then approx. 250K of memory
is needed.

I would recommend that you update to the latest version (3.7.7) which
is available at most of the common ftp sites on InterNet.  You can
also call Fifth Generation Systems at 1-800-766-7283 and order an update
which is free if your running version of 3.7 or later.  Which I
hope you are because 3.7 is the minimum version required for system
7.0

If you want transparent operation then I recommend that you consider
AutoDoubler.

for all FGS products [e-mail]
for AutoDoubler & DiskDoubler [e-mail]