home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.ibm.pc.misc
- Path: sparky!uunet!think.com!sdd.hp.com!news.cs.indiana.edu!noose.ecn.purdue.edu!gn.ecn.purdue.edu!mechalas
- From: mechalas@gn.ecn.purdue.edu (John P. Mechalas)
- Subject: Re: Stacker ate my hard disk again. :( help....
- Message-ID: <1992Dec14.163801.27783@gn.ecn.purdue.edu>
- Organization: Purdue University Engineering Computer Network
- References: <Bz6vHx.12z@news.cso.uiuc.edu> <1992Dec14.150447.4552@fcom.cc.utah.edu>
- Date: Mon, 14 Dec 92 16:38:01 GMT
- Lines: 22
-
- In article <1992Dec14.150447.4552@fcom.cc.utah.edu> dks8475@u.cc.utah.edu (David Kenneth Slack/Music) writes:
- >
- >I have been running Stacker 2.0, and I've had no problems at all with it.
- >When I ran the earlier version I would run into those kind of problems,
- >but 2.0 is (IMHO) 100% more stable than 1.x. I'm sure 3.0 wouldn't be
- >LESS stable. <smile>
- >
- >Good luck...
-
- Actually, I have been running 1.x because I have other things to spend my
- money on than the upgrades, and have neevr had *any* problems with it
- whatsoeevr. On the other hand, I keep seeing the horror stories about
- 2.0 write-protecting the volumes.
- I don't think Stacker itself is unstable...either the 1.x or 2.0 or 3.0
- versions, in so much as the comation of Stacker + some operating systems +
- some drivers + some motherboards is unstable. In other words, it no more
- unstable than any other program.
-
- --
- John Mechalas "I'm not an actor, but
- mechalas@gn.ecn.purdue.edu I play one on TV."
- Aero Engineering, Purdue University #include disclaimer.h
-