home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!rpi!uwm.edu!spool.mu.edu!news.nd.edu!bsu-cs!bsu-ucs.uucp!00clcoffing
- From: 00clcoffing@leo.bsuvc.bsu.edu
- Newsgroups: comp.os.msdos.programmer
- Subject: Re: ***4DOS vs DRDOS 6.0***
- Message-ID: <1992Nov22.140508.12220@bsu-ucs>
- Date: 22 Nov 92 19:05:08 GMT
- Organization: Ball State University, Muncie, In - Univ. Computing Svc's
- Lines: 22
-
- I figure I should put on my $.02 about DRDOS 6.0....
- I was drawn to DRDOS 6.0 because of the compress program, Super Stor.
- I have heard before that DRDOS is not totally compatible, now I believe it.
- While compressing my hard drive, DRDOS locked up tight. In the end I had
- to reset my computer, no other way out. My data was the electronic equiv-
- alent of scrambled eggs. Let my make a point that my system is a completely
- compatible 386, AMI BIOS, and DRDOS still locked up.
- My friend down the hall also used (note past tense) DRDOS and SSTOR.
- Somehow part of SSTOR's data file became corrupt. When SSTOR loaded, it
- displayed a message to the effect of "...file corrupt, mounting device as
- read only." The DRDOS manual advised us to run CHKDSK to correct the problem
- then reboot. How is it possible to correct the problem when SSTOR has the
- drive write protected? We backed up all data which wasn't corrupted, and
- removed DRDOS for good!
- DRDOS may have its good points, but I data integrity and compatibility
- problems outweigh the good in my opinion.
- AN ALTERNATIVE-- I would suggest using 4DOS instead of DRDOS. 4DOS adds
- new commands, enhances the rest, allows the user to define/redefine commands,
- adds pop up help, and more. --And I have not had a single compatibility
- problem with it.
- ---
- charles
-
