home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.misc
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!cbnewse!cbnewsd!att-out!walter!qualcom.qualcomm.com!cancun!rdippold
- From: rdippold@cancun.qualcomm.com (Ron Dippold)
- Subject: Re: Stacker and Hyperdisk, but how?
- Message-ID: <rdippold.724553425@cancun>
- Sender: news@qualcomm.com
- Nntp-Posting-Host: cancun.qualcomm.com
- Organization: Qualcomm, Inc., San Diego, CA
- References: <1992Dec16.120156.7753@ericsson.se> <1992Dec16.223918.10968@rei.com>
- Date: Thu, 17 Dec 1992 00:50:25 GMT
- Lines: 23
-
- fox@rei.com (Fuzzy Fox) writes:
- >etxstfr@helix.ericsson.se (Stefan Frick) writes:
- >>The 'README.DOC' that came with stacker claims that Stacker and Hyperdisk can
- >>co-exist but they don't give any details, just that caching should be done
- >>towards the uncompressed part of the disk.
-
- >Um...Does Stacker perform an SSWAP function, thus swapping the
- >compressed and uncompressed drives? This might confuse Hyperdisk.
- >Perhaps you should load it after Stacker has done it's SSWAP magic, or
- >maybe stop using SSWAP if it's not too much trouble.
-
- Stacker/Hyperdisk worked great for me for a long time. The trick is
- to stack the drive that the compressed "drive's" files is on, and not
- the compressed "drive". Thus, on hard disk C: I had a file,
- C:\STACKVOL.000 that appeared as drive D: once stacker was loaded.
- You should NOT tell Hyperdisk to cache "D:", just C:. Never did it
- with SSWAP...
-
-
-
- --
- Custom will often blind one to the good as well as to the evil effects of any
- long established system. -- Bishop Richard Whately
-