🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.ibm.pc.misc
Article #10315

Re: Stacker ate my hard disk again. NOT!

#10315
From: Steven Lemons
Date: Tue, 15 Dec 1992 05:06
41 lines
2486 bytes
Like several other users, I had been using version 1.x of Stacker since
it came out, with no problems that could be attributed to the program.
"Unstable" is not a fair characterization of this software.

	.	.	.

I put off upgrading, since $49+ seemed out of line for an upgrade to
software in this price range. (And with several products now competing
in this market, this is probably the last time Stacker will be able to
soak its users for this amount.)

Regardless, I've just upgraded to version 3. This version is definately
quicker on my pc, though I'm not sure that they have managed to
increase the level of compression much.

One potential problem is the setup program. It works fine for the most
part, but it expects to be able to install the entire upgrade into the
directory in which the current Stacker program resides. Now, I don't
know about version 2, but version 1 only required you to leave a very
small (100k?) portion of the disk uncompressed.

So let's say that you left only the minimum amount of space
uncompressed, putting stacker.com there, and the remainder of the
Stacker programs onto the compressed volume. When you go to install
version 3, it of course wants to put everything into the same directory
with stacker.com.  Unfortunately, there isn't room, and the setup
program doesn't give you the option of changing the install directory -
it simply says to make more room, and run setup again. Well, there is
no way of making more room, if the Stacker volume is occupying all but
100k of the disk. We're talking "major problem with the setup program"
here.

It is possible to get around this "little" problem with the setup
program, but one would expect more from version 3 of a product that is
the leader in its field. This setup program puts (some) users into precisely 
the position in which they are likely to make a mistake, and perhaps
damage their existing stacked volume.


Steve Lemons
Technical Details
Message-ID: <1gjp3sINNmph@male.EBay.Sun.COM>
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!ames!sun-barr!male.EBay.Sun.COM!lime!slemons
References: <92349.214819RFM@psuvm.psu.edu>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!ames!sun-barr!male.EBay.Sun.COM!lime!slemons
From: slemons@lime.EBay.Sun.COM (Steven Lemons)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Stacker ate my hard disk again. NOT!
Date: 15 Dec 1992 05:06:04 GMT
Organization: Sun Microsystems, Inc.
Lines: 43
Distribution: world
Message-ID: <1gjp3sINNmph@male.EBay.Sun.COM>
References: <92349.214819RFM@psuvm.psu.edu>
Reply-To: slemons@lime.EBay.Sun.COM
NNTP-Posting-Host: lime.ebay.sun.com