Extracting CDOS and CP/M) files
cisin at xenosoft.com
Thu Oct 11 17:10:12 CDT 2007
On Thu, 11 Oct 2007, Chuck Guzis wrote:
> The one we never could figure a way around was the customer turning
> the power off before an application could terminate and close any
> open files, update indices, etc.
> The problem is still with us today. Nihil sub sole novum.
Current method is to treat "shutdown" as a "request", not a command.
For the youngsters who weren't around in those days:
In MS-DOS 6.00 (and some earlier incidents back to Windoze 3.10) MICROS~1
exacerbated that problem horribly with SMARTDRV.
People would turn off their computers as soon as the DOS prompt reappeared
after word processing, spreadsheets, etc., and some or all of the new data
and DIR would not have been written yet!
The blame was always hung on the disk compression, since that was what
people NOTICED being different; but the compression was NOT the problem.
Eventually, MICROS~1 had to do a free update (6.2x) to fix it.
The repairs that were made to fix the compression related problems
SMARTDRV would default to not doing WRITE caching.
If write caching had been enabled, SMARTDRV would no longer change the
sequence that cached sectors were written (which had provided some
If write caching were enabled, then when an application ended, SMARTDRV
would not relinquish control back to DOS to display tyhe prompt until the
write buffers had been written.
Those were the patches that "fixed the bugs in the compression system".
Infoworld had "proven" that the compression was bad by setting up a script
to WP, Lotus, etc. and a COLD restart in a loop. Bill Gates contacted the
editor, and because billg would not admit to flaws in SMARTDRV (or
anything else), he just told the editor that their testing methodology was
flawed. That resulted in an editorial denouncing MICROS~1 for the call.
Ah, the good old days.
More information about the cctalk