Has a new CDOS appeared? - Mikhail BigWolK PRESENTS: CDOS 1.10

╔══════════════════════════════ ═══════════════════════════════╗
║▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒░New CDOS appeared?░▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒║
╚══════════════════════════════ ═══════════════════════════════╝

(C) WLODEK BLACK

			Don't think down on seconds;
			You will understand for yourself, as I soon realized,
			When they chop you off like a puppy,
			Without letting me download even a quarter of the directory...


		Mikhail BigWolK PRESENTS:
			┌───────────┐
			│ CDOS 1.10 │
			└───────────┘

...On the last day of the passing golden autumn, on the eve of autumn
brainy and gray, in the family of communication programs under “our”
The modem started refilling. Count chickens in the fall!  We didn't have time
the last applause died down after the door closed quietly
the door of KOLOVRAT is like a relay race of merciless trampling on
fortunately everyone picked up the good old (and the same new!) CDOS
hitherto little known to the general public, but undoubtedly a brilliant hacker
by name... (see title of the note).
   So, CDOS version 1.10.
   At Misha’s request, I am commenting on it (see just above the title...).
The changes that Misha made are small in scope, but exceptional
extremely valuable in essence. Probably every sysop is familiar with the depressing
a picture of hopelessness: morning... Silence... Tight
"curtained" server... On the screen of the newly turned on monitor
The inscription begins to appear: “Disk error... Retry, Abort...”.
And it doesn’t matter why the disc is sealed from recording,whether he's on-
covered with a copper basin or a blue top... Sysop presses “Abort”, you-
loads "HISTORY", looks... Empty.  Milchik is sleeping, the night flies,
and the car hangs... Nothing further can be sung.
   So, in version 1.10, all disk errors are processed in
simple: "Disk error" -> "Wait ring...". Instead of waiting for an answer
that sleeping sysop, the server “rejects” the user’s current call
and then goes on to wait for the next call. Now it is impossible
but hang up the server with an attempt to write to a protected or absent-
disk, and reading errors will only lead to a loss of communication and nothing more.
Moreover. Thank you, Misha!
   It is better to unload HISTORY in 1.10 by BREAK->FILE->CAT->SAVE,
and not through EXTENDED MODE, since if the last communication session was
set the current “wrong” drive, then instead of unloading you again
you will see server mode.
   CDOS1.10 is less suitable for USER work, since possible
disk errors will put it into server mode, regardless
on SETUP. But this is nonsense; for user work you can have some
some other version.
   That's it. Download CDOS1.10 from "NICRON" BBS and from BBS
WOLF, use it and report any bugs. Good luck!

                                                 (c)WLODEK BLACK
                                               Tel. (095)462-8902
                                                   (Vladimir)