BEWARE DR DOS 6.0 USERS USING SUPERSTOR!!!!!
JWFENNER
If you are using DR DOS 6.0 and SuperSTOR, then beware. If the SuperSTOR drive
is completely filled, then your SuperSTOR drive may be CORRUPTED. According to
Novell (Digital Research), they know that the problem exists. They say that
whenever the drive is filled up, it automatically wraps around and starts
writting stuff at the BEGINNING OF THE DRIVE again, OVERWRITTING YOUR FAT and
directory areas. They also say that there is no fix for it, NOR ANY PLANNED
that they know of! The only recommendation they had was that you don't fill
your SuperSTOR drive more than 80% - 85% full (thus elimanting some of the
usefulness of this utility). It seems very strange they the do not intend to
fix such a major bug as this, since it is one of the major selling points
(in my opinion) of DR DOS. It also makes me wonder about the quality of the
other DR DOS utilties...
Scott Alfter
>*** WARNING *** WARNING *** WARNING ***
>They say that whenever the drive is filled up, it automatically wraps
>around and starts writting stuff at the BEGINNING OF THE DRIVE again,
>about the quality of the other DR DOS utilties...
I remember something funny happening while I had SuperStor installed.
I didn't lose anything, but I killed SuperStor before it had a chance
to do something really nasty. It wasn't doing much for me anyway...I
run a BBS, and most of the files are pre-compressed.
The rest of DR DOS, however, has been knock-on-wood.
_/_ Scott Alfter Internet: sknk...@cs.unlv.edu
/ v \ Call the Skunk Works BBS today!
(IIe ( (702) 894-9619 300-14400 V.32bis Apple II/IBM/Star Trek/Aerospace
\_^_/ Ask me about SoftDAC--digital audio for your IIe/IIc! Apple II Forever!
Daniel Chukurov 21324
SuperStor was not made by DRDOS people.
Also, do other disk compression utilities have the same problem?
Now for my "problem" with SSTOR:
If I have multiple partions A trough G and SSTOR all of them SSTOR
creates another drive H where it puts DCONFIG.SYS, which chains
to c:\config.sys, as swell some other files. Well, the question is
HOW DO I MAKE THE BOOTABLE DISK? WHICH FILES DO I NEED TO PLACE ON
THE FLLOPY?
Bill Neisius
: *** WARNING *** WARNING *** WARNING ***
..that's odd. It seems that I'm always running my SuperStor partitions at
90-100% of capacity, yet I've never had a FAT problem. Just luck? hmmm....
Dov Bai-MSI Visitor
>
>If you are using DR DOS 6.0 and SuperSTOR, then beware. If the SuperSTOR drive
>is completely filled, then your SuperSTOR drive may be CORRUPTED. According to
>Novell (Digital Research), they know that the problem exists. They say that
>whenever the drive is filled up, it automatically wraps around and starts
>writting stuff at the BEGINNING OF THE DRIVE again, OVERWRITTING YOUR FAT and
>directory areas.
Same thing happened to me. The disk became full while downloading with
MS-KERMIT. After the download completed my KERMIT and DRDOS directories
were gone. When I tried to reboot, SuperStore sensed a problem with
file structure and mounted the drive write-protected. The only thing I
could do is backup the disk and reformat.
Dov
Jim Graham
[hmmm, don't see a ``microsoft'' anywhere in that username, but perhaps
it's hiding somewhere.....]
>> *** WARNING *** WARNING *** WARNING ***
>>
>> If you are using DR DOS 6.0 and SuperSTOR, then beware. If the SuperSTOR
>> drive is completely filled, then your SuperSTOR drive may be CORRUPTED.
[remainder nuked]
In article <23...@hacgate.SCG.HAC.COM> bi...@solaria.hac.com responds:
> ..that's odd. It seems that I'm always running my SuperStor partitions at
> 90-100% of capacity, yet I've never had a FAT problem. Just luck? hmmm....
same here --- my SuperStor partition was, for rather a long time,
floating at around 95% full, and ran out completely several times.
the drive did *NOT* ``wrap around'', as the first poster suggests,
but instead, returned the standard old message about insufficient
disk space.
oh, before anyone suggests that he's running an older version than
me, I bought DR Dos 6.0 the day it was released (didn't want to wait
for the upgrade from 5.0...I wanted SSTOR ``yesterday'') and I have
yet to install the updates (just found the disk again yesterday...had
forgotten all about it).
later....
--jim
--
#include <std_disclaimer.h> 73 DE N5IAL (/9)
------------------------------------------------------------------------------
INTERNET: j...@n5ial.chi.il.us | gr...@gagme.chi.il.us | j.gr...@ieee.org
ICBM: 41.70N 87.63W UUCP: gagme!n5ial!j...@clout.chi.il.us
AMATEUR RADIO: n5ial@n9hsi (Chicago.IL.US.Earth) AMTOR SELCAL: NIAL
------------------------------------------------------------------------------
Mark Flynn
>In article <10...@engcon.marshall.ltv.com> fen...@engcon.UUCP (JWFENNER) writes:
>>*** WARNING *** WARNING *** WARNING ***
>>[...]
>>They say that whenever the drive is filled up, it automatically wraps
>>around and starts writting stuff at the BEGINNING OF THE DRIVE again,
>>OVERWRITTING YOUR FAT and directory areas...It also makes me wonder
>>about the quality of the other DR DOS utilties...
>
>I remember something funny happening while I had SuperStor installed.
>I didn't lose anything, but I killed SuperStor before it had a chance
>to do something really nasty. It wasn't doing much for me anyway...I
>run a BBS, and most of the files are pre-compressed.
>
>The rest of DR DOS, however, has been knock-on-wood.
>
I must have missed the beginning of this thread. Could some kind soul please
send me more details? I've never had problems with this utility (I've got
about 75Meg on a 40Meg drive), and at times get close to the limit, but
havn't yet reached it. Thanks.
Mark Flynn
David Paper
Well, i dunno about superstor on Dr Dos 6.0, but i've heard HURRENDOUS
things about Stacker 2.0 on MS dos 6.0Beta....it will boot up, run, then
after you load all your files, boom, it crashes big time, and you loose
everything.. and getting stacker off under normal conditions is a pain in
the but.. let alone if it crashes..
just a little info..
and for some reason, stacker doesn't like REALLY REALLY big HD.. i tried
to stack a 330, and it TOOK 4 EVER!!!! totally slowed the 386/33 down..
oh well
-dave
Tom Williams
> *** WARNING *** WARNING *** WARNING ***
>
> If you are using DR DOS 6.0 and SuperSTOR, then beware. If the SuperSTOR dri
> is completely filled, then your SuperSTOR drive may be CORRUPTED. According
> Novell (Digital Research), they know that the problem exists. They say that
> whenever the drive is filled up, it automatically wraps around and starts
> writting stuff at the BEGINNING OF THE DRIVE again, OVERWRITTING YOUR FAT and
> ... It also makes me wonder about the quality of the
> other DR DOS utilties...
>
IMHO, DR DOS 6.0 has but the one failing. Who wrote SuperStor? I
understand that the Stacker folks did, and the two utilities are
extremely similar. Maybe THEY are the ones who need to make the
correction.
I won't let you assume I have had no problems (though it is the case),
because I don't have a hard drive on my laptop (where the good DR is
loaded). What it DOES provide me is a direct interface to GEM and the
DRIVPARM function for my floppies (Tandy 1400LT respondes with 360k as
drive size to any system other than their own for formatting, etc.).
HALE TELECOMMUNICATIONS - Public Access Node, San Diego CA 619/660-6734 HST
wi...@hale.cts.com (Tom Williams) 26-Sep-92 at 6:32a
YONG KUEN FATT ALAN
Just a couple of days ago, I install Monkey2 to D:. During the
intallation, the SuperStor drive ran out of disk space. I notice
that the harddisk LED wastnt lighted up halfway during the
installaion. Anyway, when I "dir d:", I saw all the files being
"installed". However half of them were 0 size. Hence in my case,
it only create 0 size files when it is full. I dont have any
problem of corrupted FAT etc.
Oh, I reinstalled Monkey2. I deleted more files for it. BTW,
Monkey2 installation program gave "Installation completed" even
though the files are 0 size.
Alan
----- Beam me up Scotty, there's no intelligent life here -Kirk
**********************************************************************
* engp...@nusunix2.nus.sg ay...@nuseev.bitnet *
* VLSI CAD and Design Laboratory, Dept of Electrical Engineering *
* National University of Singapore, 10 Kent Ridge Crescent *
* Singapore 0511. Telephone: 7726319 Fax: 7773117 *
**********************************************************************
----- Lets get dangerous ---DW
Scott Alfter
>IMHO, DR DOS 6.0 has but the one failing. Who wrote SuperStor? I
>understand that the Stacker folks did, and the two utilities are
>extremely similar. Maybe THEY are the ones who need to make the
>correction.
Addstor wrote SuperStor; Stac wrote Stacker. Maybe the current
version of SuperStor has been fixed; you'd have to buy it separately.
I didn't bother with it, though, since I run a BBS on my system and
95%+ of the files are ZIPs, ARJs, GIFs, JPGs...they're already
compressed and SuperStor can't do much more with 'em.
Frank Slootweg CRC
No flames intended and I would very much like a response from the
Novell/DRI people to this, but I find the above highly unlikely. I have
intentionally (see below) completely (0 bytes free) filled up my SSTORed
D partition many times without any problems. Like another poster, I have
the original DR DOS 6.0 version (i.e. no (Dec'91 or MS-Windows 3.1 or
Apr'92) updates).
[Why did I intentionally fill up my SSTORed partition? I did it to
reproduce the "CHKDSK reports '... bytes in SuperSTOR reserved units'
(or similar)" "problem". Problem between quotes, because this is, I
think, normal CHKDSK behaviour when the SSTORed partition becomes full
and (for a compression factor of less than 2:1) the CHKDSK numbers *can
not* "add-up" anymore, so the difference becomes "SuperSTOR reserved
units" (other utilities (like PC Tools' DISKFIX) will see these as "bad
blocks").]
Frank "Do I need to worry?" Slootweg
JAMES DORCEY
writes...
>IMHO, DR DOS 6.0 has but the one failing. Who wrote SuperStor? I
>understand that the Stacker folks did, and the two utilities are
>extremely similar. Maybe THEY are the ones who need to make the
>correction.
Actually, Addstor (sp?) wrote SuperStor, which is the primary competitor of
Stacker in the disk compression market. I get the impression that the
version of SuperStor included with DR DOS 6.0 is akin to a functional demo
- if you try this version of SuperStor, you can buy the "full package" (
strangely enough, there is a discount mail-in coupon in the DR DOS 6.0 box
for the full version of SuperStor - or at least there was in mine).
JD
hc...@csie.nctu.edu.tw
Charles Rutledge
>
>Actually, Addstor (sp?) wrote SuperStor, which is the primary competitor of
>Stacker in the disk compression market. I get the impression that the
>version of SuperStor included with DR DOS 6.0 is akin to a functional demo
>- if you try this version of SuperStor, you can buy the "full package" (
>strangely enough, there is a discount mail-in coupon in the DR DOS 6.0 box
>for the full version of SuperStor - or at least there was in mine).
>
A word of caution when getting the full SuperStor package. The Version 2
package may not be fully compatable with the one in DR DOS (at least it
wasn't for me). After installing, I decided to try out a few of the
utilities -- such as Recompress, which is suppost to yield a better
compression ratio. During the process, something bad happened and I
got an error not described in the book. My drive lost three directories
and the SuperStor fix-disk utils were never really able to clear up the
problem.
To make matters worse, DR DOS's CHKDSK would not work at all with SuperStor
Version 2. (Yes, I have the April update for DR DOS installed.) CHKDSK
would go start and say it was checking the SuperStor drive and then lock up
solid. Ended up saving what I could and reformating the drive.
Maybe someone with Novell/DRI or Addstor could comment on this.
--
Charles Rutledge / NCR Test Program Development | NCR Corporation
Internet: Charles....@PeachtreeCityGA.NCR.COM | The Networked Computing
ATT: (404) 487-7000 Ext 7523 / Fax: (404) 487-7089 | Resource Of AT&T
Ranseus (Jim Knepley)
>
>A word of caution when getting the full SuperStor package. The Version 2
>package may not be fully compatable with the one in DR DOS (at least it
>wasn't for me). After installing, I decided to try out a few of the
>utilities -- such as Recompress, which is suppost to yield a better
>compression ratio. During the process, something bad happened and I
>got an error not described in the book. My drive lost three directories
>and the SuperStor fix-disk utils were never really able to clear up the
>problem.
I also had this problem, but I only lost 1 directory and I got it back
using Norton and the SSTOR utilities.
>To make matters worse, DR DOS's CHKDSK would not work at all with SuperStor
>Version 2. (Yes, I have the April update for DR DOS installed.) CHKDSK
>would go start and say it was checking the SuperStor drive and then lock up
>solid. Ended up saving what I could and reformating the drive.
CHKDSK worked fine for me with v2 of SSTOR. No problems at all, XDIR
acted as it always did, too.
Really, all this talk about the quality of DR DOS is pretty silly. I've
been running it for a while now and have had no problems with DR DOS at
all. There have been some other programs (such as SSTOR) that had the
odd problem, but nothing I wasn't able to fix in 10-15 minutes.
Jim
--
**** kne...@cs.colostate.edu ****************** Boycott Microsoft ****
Jim Knepley Magician, programmer, computer geek.
(Ranseus) Proud user of Clinton condoms. Scented like Flowers.
*********** CTHULHU IN '92! -- Why vote for the LESSER evil? **********
Charles H. Reichert
The store bought Version of SSTOR IS NOT compatible with DR-DOS 6.0 1This was mentioned
in the Manual or a README file. The SSTOR supplied by AddStor for DR-DOS 6.0
is "tweaked" for DR-DOS! I've been using SSSTOR drive D, E without problems.
I use a small uncompressed Drive C to be sure there's no problems when I modify the
size of my autoexec.bat or config.sys files.
--
====================================================================
| Charles H. Reichert 708-632-6669 Work - MOTOROLA, INC Cellular |
| KD9JQ 708-358-3827 HOME - after 8PM CST weekdays |
| 955 Concord Ln. Hoffman Ests., IL. 60195 |
====================================================================
Frotz
]If I have multiple partions A trough G and SSTOR all of them SSTOR
]creates another drive H where it puts DCONFIG.SYS, which chains
]to c:\config.sys, as swell some other files. Well, the question is
]HOW DO I MAKE THE BOOTABLE DISK? WHICH FILES DO I NEED TO PLACE ON
]THE FLLOPY?
I take it that FORMAT A: /S doesn't work for you?
--
John "Frotz" Fa'atuai fr...@novell.com (email@domain)
Desktop Systems uunet!novell.com!frotz (bang address)
Group/Novell NOVELL:FROTZ or FROTZ@NOVELL (MHS address)
c/o TS Dept. 408/645-2067 (vmail)
80 Garden Court 408/649-8209 (fax)
Monterey, CA 93940
G. Wayne Nichols
feature with compressed volumes created by DRDOS's version of SSTOR.
They also warn about using their DISKOPT with SuperStor 2.0.
CHKDSK may not work, either, if I recall.
(Their recommendation is to back up the compressed volume,
delete the compressed volume, recreate under SuperStor 2.0,
and restore the compressed volume's data).
So I backed up my 240 MB compressed volume to floppies,
and used Recompress anyway. No problems occurred.
In fact, CHKDSK had been hanging checking the internal SSTOR info,
and now it works again.
I haven't tried DISKOPT, but PC Tool's Compress continues to work fine.
So I gues in SOME situations you MAY have problems with CERTAIN combinations.
Charles Rutledge
>
>Really, all this talk about the quality of DR DOS is pretty silly. I've
>been running it for a while now and have had no problems with DR DOS at
>all. There have been some other programs (such as SSTOR) that had the
>odd problem, but nothing I wasn't able to fix in 10-15 minutes.
I have no complaints at about the quality of DR DOS and feel it is much
better than any favor of MS-DOS. My problem was adding in what I thought
would be an upgrade (SuperStor 2.0) to get all its features. As it turns
out, SuperStor 2.0 is probably not an upgrade for the version packaged with
DR DOS. Adstor probably could have mentioned this somewhere (or maybe they
did and I missed it -- live and learn). But problems about getting programs
that should work together and don't are not silly to those of us that do
have problems. I'm glad things worked out for you. I had a bit more trouble,
and though all in all, I like DR DOS, I would like to think I come to Net
for help and to help pervent troubles for others.
JWFENNER
drive fills up. Sometimes, according to Novell/DR, when the drive fills up it
will WRAP AROUND to the beginning of the SSTOR drive and OVERWRITE THE FAT.
They know the problem exists, but at the time I talked with them, they had no
intentions of fixing it (or requesting that ADDSTOR do so). Their only
recommendation was not to fill the SSTOR drive more than 85% full. Seems like
a waste if you can't use your full drive...
--
==================================================================
= Jon Fenner (engcon!fen...@uunet.uu.net) =
= LORAL Vought Systems - Neural Network / AI Research Group =
==================================================================
Frank Slootweg CRC
>I also have had problems with SSTOR that comes with DRDOS. When the SSTOR
>drive fills up. Sometimes, according to Novell/DR, when the drive fills up it
>will WRAP AROUND to the beginning of the SSTOR drive and OVERWRITE THE FAT.
>They know the problem exists, but at the time I talked with them, they had no
>intentions of fixing it (or requesting that ADDSTOR do so). Their only
>recommendation was not to fill the SSTOR drive more than 85% full. Seems like
>a waste if you can't use your full drive...
This urban legend seems to continue (by the same poster?). As I posted
before: I have *many*, *many* times completely filled my (DR DOS 6.0)
SSTORed partition without any ill effects.
Novell/DRI (Frotz?) can you please comment on this?
Frank Slootweg
Massimo Cotrozzi
>fen...@engcon.marshall.ltv.com (JWFENNER) writes:
>Frank Slootweg
So did I . Never had problems with it ...
Massimo
--
--------------------------------------------------------------------------
! /|/| /| \ / ! Massimo Cotrozzi Computer Science Dept. Milan Italy !
! / | /-| \ ! cotr...@ghost.dsi.unimi.it !
!/ |/ | / \ ! mas...@cdc835.cdc.polimi.it !
phy...@csc.canterbury.ac.nz
> fen...@engcon.marshall.ltv.com (JWFENNER) writes:
>
>>I also have had problems with SSTOR that comes with DRDOS. When the SSTOR
>>drive fills up. Sometimes, according to Novell/DR, when the drive fills up it
>>will WRAP AROUND to the beginning of the SSTOR drive and OVERWRITE THE FAT.
>
> before: I have *many*, *many* times completely filled my (DR DOS 6.0)
> SSTORed partition without any ill effects.
Ditto. I'd like to hear some confirmed report that there is a problem there, if
there is one. The only problems I've had have been traced back to faulty
hardware (sometimes this is darned hard to find - things like Norton's DT
aren't good enough, but Jim Braking's HDDIAG spotted the intermittent problem).
I think the problem might be that the disk has more than 1024 cylinders, in
which case you can get a wrap-around with any software if you fill up the disk,
unless you have the proper software loaded first. And of course that isn't
SuperStore's fault. The only problem might be in realising the special driver,
if it needs to be loaded every time, would go at the start of DCONFIG.SYS, not
CONFIG.SYS, just as DMDRVR.BIN has to go first.
Mark Aitchison, University of Canterbury, New Zealand.
USENET News System
>there is one. The only problems I've had have been traced back to faulty
>hardware (sometimes this is darned hard to find - things like Norton's DT
>aren't good enough, but Jim Braking's HDDIAG spotted the intermittent problem).
>
>I think the problem might be that the disk has more than 1024 cylinders, in
>which case you can get a wrap-around with any software if you fill up the disk
>unless you have the proper software loaded first. And of course that isn't
>SuperStore's fault. The only problem might be in realising the special driver,
>if it needs to be loaded every time, would go at the start of DCONFIG.SYS, not
>CONFIG.SYS, just as DMDRVR.BIN has to go first.
>
>Mark Aitchison, University of Canterbury, New Zealand.
Mark
I've been using Superstor for the last year without any problems (at
all) and was beginning to believe that the disk filling up was, as a
previous poster said, an urban legend. However recently, a repeatable
failure has occurred with my system. Here's the scenario:
HARDWARE:
HP Vectra 8MHz AT (real old), DRDOS 6 with latest revisions installed
30MB 5ms HDD, partitioned as
D: is 3MB uncompressed,
C: is remaining 28MB superstored (gives about 46MB)
(this is an old MFM drive that came the the PC. ie. <1024cyl)
It's been running fine for a year without ANY NOTICABLE DIFFERENCE between
C: and D:.
THE PROBLEM
===========
To install (on C:) the children's game "The Treehouse" which has it's
own INSTALL program. It needs (supposedly) about 3MB.
--------------------------------------------------------------------------
ATTEMPT #1
I have about 3MB left on C: so I started INSTALL - it failed at the end.
RESULT #1
A "DIR" shows "0 bytes left" as expected - I thought there might be
insufficient room, so I deleted some files, one of which was 97K long.
AFTER DELETING THE FILES, the files were gone but there was STILL "0
BYTES LEFT". DRDOS's chkdsk did not detect any errors and neither did
PCTools #7 of DISKFIX. Where did the 97K file (and it's space go?)
* THIS SYMPTOM (files gone & still "0 bytes left") IS CONSISTENT & REPEATABLE
At this stage:
ALL THE REMAINING FILES WERE INTACT & COULD BE READ OK,
I JUST COULDN'T WRITE ANY :-(
ACTION #1
I think it was about this time that CHKDSK reported about 9MB of
SUPERSTOR RESERVED DRIVE UNITS (or something similar that doesn't
usually appear). Reread some old news from Frank Slootweg (sp?) about
a similar problem and found that the space might be in the BAD BITS of
DISK list, so I ran DISKOPT and found that most of the disk came back
(and I could write again.
** There was the usual disagreement between CHKDSK, DIR and SSTOR about
how much disk was available.
--------------------------------------------------------------------------
ATTEMPT #2
Delete lots of files to leave lots more than 3MB free on the
compressed partition, and try INSTALLing Treehouse again (brilliant
program by the way), same result as above. Rerun DISKOPT to clean up
and DELETE LOTS MORE FILES.
--------------------------------------------------------------------------
ATTEMPT #3
With about 9MB free (real space as I remember), the TREEHOUSE
installed perfectly.
WHY?
Don't know, maybe Treehouse's INSTALL keeps sending data to be written
after and earlier WRITE has failed ???
I'M STILL HAPPY TO USE IT ...
I have no qualms about using DRDOS including SUPERSTOR, in fact I
prefer DRDOS to MSDOS which I use at work, but it would be nice if
there were better diagnostic and repair utilities for SUPERSTOR.
Cheers (from a previously skeptic :-)
Giovanni
--
-----------------------------------------------------------------------------
Giovanni Moretti ZL2BOI
Computer Science Department, Massey University, Palmerston North, New Zealand
G.Mo...@massey.ac.nz Phone +64-6-356-9099 Fax 64-6-350-5611
Frank Slootweg CRC
described is that SuperSTOR apparently has less available space than you
think and/or the utilitiies (CHKDSK, XDIR, SSTOR) seem to tell you.
However the, IMO, urban legend is something totally different and much
worse:
fen...@engcon.marshall.ltv.com (JWFENNER) wrote:
>I also have had problems with SSTOR that comes with DRDOS. When the SSTOR
>drive fills up. Sometimes, according to Novell/DR, when the drive fills up it
>will WRAP AROUND to the beginning of the SSTOR drive and OVERWRITE THE FAT.
The "OVERWRITE THE FAT" implies total disk corruption. You just have
less space than you think. Two totally different problems!
GM> ATTEMPT #1
GM> I have about 3MB left on C: so I started INSTALL - it failed at the end.
This is probably the essential part. If the "I have about 3MB left on
C:" came from the DIR command, then that is your problem. You should not
believe the DIR command for a SSTORed drive (and the CHKDSK command even
less (I think this was, rightfully, mentioned in the README for the
Apr'92 update)). As I said several times before: This is *no* critcism
on SuperSTOR. DIR and CHKDSK work as good as possible. If you want The
Real Numbers (tm) then use SSTOR and XDIR.
A simple method to determine how much you can still store on a SSTORed
drive: Do a "DIR" for the drive and look at the last reported number
("available"? (My PC is at home)) and divide it by two. That is the
number that you *always* *can* store, even if the data can not be
compressed. You *might* be able to store more if the data can be
compressed. Of course you can get this number from SSTOR too, but DIR is
probably more convenient.
Frank Slootweg
P.S. Also the "Disk is full. Remove some files. Disk is still full and
CHKDSK reports reserved units. Run DISKOPT. Disk is no longer
full." behaviour is normal and can not be prevented. See y old
postings for details (Time for a DR DOS / SuperSTOR Frequently
Asked Questions list?).
Thilo Wunderlich
>P.S. Also the "Disk is full. Remove some files. Disk is still full and
> CHKDSK reports reserved units. Run DISKOPT. Disk is no longer
> full." behaviour is normal and can not be prevented. See y old
> postings for details (Time for a DR DOS / SuperSTOR Frequently
> Asked Questions list?).
How about an own newsgroup for DrDos ? But don't ask me to create it. I've
no idea how to do that . And with an own newsgroup we could create a FAQ
for DrDos.
Thilo
--
Thilo Wunderlich c1...@alf.zfn.uni-bremen.de