NeOS

=============================================================================
* Forwarded by Tim Kelly (2:465/240)
* Area : ZX.SPECTRUM (ZX.SPECTRUM)
* From : Kamil Karimov, 2:5080/500.12 (Sat Jun 19 1999 22:30)
* To : Roman Petrov
* Subj : NeOS
===========================================================================================
┐ ┌
├─┤ello, Roman!
┘ └
They asked me to send a letter about NeOS:
----------------- cut -------------------------

Some time ago I implemented it on my machine (Quorum)
IDE controller. And since the existing tools for working with a hard drive were not satisfactory, to put it mildly, I decided to make an add-on for the CP/M OS, since CP/M has been working on Quorums almost since the creation of this computer. There wouldn't be much need to modify it, because... All CP/M programs access the
system through standard points. There is already an IDE driver that allows you to communicate with the hard drive at the level of logical
sector numbers, as well as part of the MS-DOS kernel - support for partitions, FAT16,
subdirectories, opening files and sequential reading, as well as
a simple console.

ABOUT MY WORK HAS BEEN SUSPENDED BY INFORMATION ABOUT NeOS. Cool idea! After working with NeOS on an emulator and on a real machine, I
decided thatThis is exactly what mine, as well as many
other SPECTRUMS, lack.

In Yekaterinburg there is a large fleet of computers
locally produced Quorum. And today there are models with
RAM 64,128,256,512,1024 kb. The idea of ​​a new operating system, NeOS
attracted a certain circle of people.

I would be glad to offer cooperation in order to speed up the release
of the full version, as well as expand the set of drivers specifically for
Quorum 128-1024. And at the moment there are several
proposals:

1.
?: It’s clear, does each device need its own
driver? (for example, with several drives it is quite possible
to get by with one driver)

?: How is it planned to add names of logical
devices when a partition is detected, and in general, should the device driver
do this?

- suggestion: The device driver (or FS) should
determine the presence and number of devices of its type, in
according to which add logical devices to the list
(necessary for the possibility changing hard drives). The corresponding driver function (initialization) is required. The driver
must be passed a pointer to the device description table.

! There is a glitch in system 1.0: if at the time of initialization there was no disk in the drive, then the system thinks thatthe device does not
exist. The device will not appear even if the disk is
inserted.

FCB:
?: In the directory, judging by the fact that the file number in the directory
is one-byte (35), there is a limit on 256 files in
the directory - give this byte a meaning: the file number in the block
directory, and the number of the first block of the directory (33) - the number
of the block containing the descriptor file.

2.
The ide screw is connected according to its own circuit. Structure - msdos
divided into 2 sections. There is a desire to write a
driver for this scheme.

3.
There is a desire to write a driver for the CP/M file system. In
the future there will be a CP/M BDOS and CCP emulator (the emulator requires a
"CACH").

4.
In the Quorum computer (today there are models with RAM
64,128,256, 512,1024) there is access to the FDD controller without
recourse to TR-DOS. The idea came up to write an FDD driver that
works bypassing TR-DOS.

I would like to receive more detailed information about the structure
of disk device drivers, as well as information about the order
initialization of devices.

Sincerely, Evgeniy Stakhov
06/19/99 19:38:26 === Cut ===
RP> + Origin: Speccy rulezzz forever! (2:5052/7.37)

All the best,Roman!
... -= Once again! =-
-+- ∙ Sherwood Station ∙
+ Origin: ...... (Fido 2:5080/500.12)
=======================================================================================================================================================

... Email: tim_...@mail.ru 500:622/1@zxnet ICQ UIN: 34684028