home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!HUJIVMS!SHALEV
- Message-ID: <NOTABENE%92101113311481@TAUNIVM>
- Date: Sun, 11 Oct 92 13:27:00 +0200
- Sender: Nota Bene List <NOTABENE@TAUNIVM>
- From: Michael Shalev <SHALEV@HUJIVMS>
- Subject: Superstor etc.
- Newsgroups: bit.listserv.notabene
- Lines: 29
-
- Peter MacDonald has asked what effect Superstor might have
- on NB4 installation, and a similar question has been raised
- viz Stacker. Without having atttempted nb4 installation yet
- (needless today, am still waiting for it!), I doubt that
- this is the problem. What these programs do is turn the
- contents of your hard disk into one huge compressed file.
- So far as you, __and your software__ are concerned, however,
- nothing has happened. That is, Superstor maintains the
- appearance of normal filenames, and manages conversions to
- and from the compressed super-file, _transparently_.
-
- Peter, if you want to test whether the problem is with
- Superstor or DRDOS, take into account that:
-
- 1. Part of Sperstor's alchemy occurs at bootup, when
- DRDOS typically looks for a file called dconfig.sys on
- your "real" hard drive, which is where it learns that
- you are using a compressed, drive, and "swaps" the
- desgnations of the two drives (e.g. C:, the "real" drive,
- become D: so that you and your programs can still believe
- you're working on C:). Note: the offensive lines of
- config.sys--if any--might be lurking in your dconfig.sys.
-
- 2. You cannot tell DRDOS to forego working with Superstor on
- a compressed drive--unless you take the radical step of
- decompressing it, which DESTROYS ALL YOUR COMPRESSED FILES.
-
- Please let us know the outcome.
- ..Michael
-