Doors'2ooo: D2K_LAST.$z
ZXNet echo conference «real.speccy»
Once, namely 24 Jul 00 Oleg Golenkoff wrote All:
OG> People! Have you seen the sub? Why is everyone silent again?
OG> opinions / suggestions to the studio!?
And I thought the subject was already dead. It's time to approach a more or less complete version
IMHO. I’m waiting, you know, I can’t wait :)
p.s. what did you decide with FS? Transparent support will be ?
WBR, Denis Ognewsky
EmP^A1C // ALLiANCE [AMiGA]
... */MousoMeter/* : 5.680212 /km/ / *Activity*: 128 /days/ 0:22 /hours/
Somehow Denis Ognewsky tapped Oleg Golenkoff on the keyboard:
DO> And I thought the subject was already dead.
With such a general approach.... it will definitely be dead :(
since no one else is interested in this project except over the hill :(
DO> It’s time to approach a more or less complete version
DO> IMHO.
We’re approaching :) If everything goes ok, we'll make a pre-release presentation at CC'000...
DO> I can't wait, you know, I can't wait :)
Thank you for your support! :)
DO> p.s. what did you decide with FS? Will there be transparent support?
We decided to stop at transparency! whatever you want, install it aka
mount.... but as a FAT32 base (slightly modified)
C ya in nE>
So your site hasn’t been updated for three years and not a word about subzh anywhere,
that’s what I thought too - it’s gone. But look, it’s not! ;)
--
Cya, Mind Surgeon aka Anodyne.
there isn’t even a system as such... just move the mouse...
For this Au Revoire, CompoWellcome. [Team GS]
When I saw a letter from you on July 24, 00 12:37, I went and drank some beer and sat down to cook
an answer for you. And it happened on July 26, 00 at 22:40:
OG> People! Have you seen the subject? why is everyone silent again?
OG> opinions / suggestions to the studio!?
The idea is good (in my opinion), but it’s very similar to offtopic :( And this is not
good.
*Cya!* Sincerely Midi^Energy Minds
[I ZX]
[/Energy Minds Team/] [/Freedom Team/] [/X-Project Team/] [/Rulez Beer/]
... e-mail: [_mid...@usa.com_]^[_mid...@mail.ru_]
RT> The idea is good (in my opinion), but it is very similar to
RT> offtopic :( And this is not good.
Don’t stop people from doing things. What difference does it make? What’s the difference, the main thing is that it works
not like the offtopic. :)
Priest^Energy Minds
[TEAM Marinka][TEAM Spectrum][TEAM FREEDOM][prie...@mail.ru]
... Energy Minds from Freedom. We are Sinclair's generation.
C ya in nE>
C ya in nE>
Once upon a time Tue 25 Jul 2000, Oleg Golenkoff and Denis Ognewsky thought on the topic:
Doors'2ooo: D2K_LAST.$z
DO>> And I thought the subject was already dead.
OG> With such a general approach... it will definitely be dead :(
and how about you? are you coming? you can't be seen in the echoes...
OG> because no one else is interested in this project except over the hill :(
here I am interested :-)
DO>> It's time to approach a more or less complete version IMHO.
OG> We are approaching :) If everything is ok, then at CC'000 we will make a presentation
OG> pre-release...
I hope it will be online later. will it spread?
SS> I already wrote somewhere that writing “operating systems” on the Spectrum
SS> and a parody on win is not
SS> welcomed by me. I advise you to abandon the project and do
SS> something else, otherwise you’ve gotten all kinds of
SS> doors, firestarters, zx-windows and others.
Look, how smart!.. IMHO you yourself with your vehicle have not gone far from such ideas. So
people are at least trying to build some kind of interface, but in your shopping center only you yourself
know how to steer through this hole. Don't be offended by the harsh words, but that's the way it is.
See you later, Anton.
... drink some beer and drink for us. (C) Scriabin
OG> well, yes... but is the interface a by-product? :(
what is not? Everything is actually the same as in Windows... what can we say about nothing? Nothing! :-).
if only, what you threw could have done something, then... S?
C ya in nE>
OG> :(
In general, when you press past an icon, all icons should
be deselected. Secondly, when you press past the "Start" window, it should
close (and not only when you press this button). Thirdly,
why, when you close the "Start" window, all the icons Are they redrawn?
If you don’t redraw them, then it will be faster. Fourthly, the icons are dragged around with a glitch. The latter applies to the mouse, it was not tested on the keyboard. The glitch
is that the cursor “moves” from the icon, sometimes by 5-8 characters,
which is why the problem arises when dragging an icon to the edge of the screen
(the cursor has already reached the edge, but the icon has not).
And one more thing - I would like when dragging an object (left mouse button),
if I hold it down and press the right mouse button, then the object returns to
from where I started dragging it - that is, as if I didn’t move it. Why is this necessary? For example, I want to drag the icon, but I accidentally grab the window and drag it to another corner of the screen before I realize that I grabbed the wrong object. And, in order not to drag the window back, I just press the second button. mouse without releasing the first one, as a result of which the window will move
to its initial position.
P.S. And something is not clear about the purpose of the program ;)
__
__/ / Powered by Amiga
\_\/ WBR, Mystery
C ya in nE>
OG>> well, yes... but is the interface a by-product? :(
ND> and what not?
what yes? Are you satisfied with the is-dos interface?
ND> everything is actually the same as in 3-Windows...
8[ ] well, thank you... you could also compare it with domen os...
ND> what can you say about nothing? nothing! :-).
in any case, you can always express it in two terms: steering wheel / not steering wheel !
ND> Now, if only, what you threw could do something, then... Y?
it will :)
PS: and I threw this to remind you that the project is not in down!
Once Dmitry Naboka tapped on the keyboard to Oleg Golenkoff:
DN> In general, firstly, when you press past the icon, then all icons should
DN> be deselected.
let's fix it!
DN> Secondly, when you press past the "Start" window, it should
DN> close (and not only when you press this button).
Let's fix it!
DN> Thirdly, why, when you close the "Start" window, all the icons
DN> are redrawn?
DN> If you don't redraw them, it will be faster.
Let's try to fix it!
DN> Fourthly, the icons are glitchy. The latter applies to the mouse; it has not been tested on the
DN> keyboard. The glitch is that the cursor “moves” from the
DN> icon, sometimes by 5-8 characters, as a result of which a problem arises when dragging the
DN> icon to the edge of the screen (the cursor has already reached the edge, but the
DN> icon has not).
Apparently you will have to redo the entire mechanism from scratch :(
DN> And one more thing - I would like when dragging an object (left mouse button),
DN> if I hold it down and press the right mouse button, then the object returns to the place
DN> from where I started dragging it - that is, as if I didn’t move it. Why
DN> is this needed? For example, I want to drag an icon, but I accidentally grab the window
DN> and drag it to another corner of the screen before I realize that I grabbed
DN> the wrong object.do not drag the window back, I just press the second
DN> mouse button without releasing the first one, as a result of which the window will move
DN> to its starting position.
Amiga rulez ? :) I understand everything, I will take it into account when remaking...
DN> P.S. And something is not clear about the purpose of the program ;)
navigator like WB (Amiga) & Explorer (pC)
OG> in any case, you can always express yourself in two words: steering wheel/not steering wheel!
Maybe you meant steering wheel/suks? Well, it doesn’t fit on the steering wheel... So I asked for it ;)
Well, bye! Tigrr from -■Brainwave^X-Project■-
The interface can exist without the system, like a demo. It is much more interesting how
this is implemented from the inside - then you can decide whether a given system is good or
not.
And in general, the interface is not an operating system and calling a demo, which
only shows the interface and that’s all, is IMHO wrong.
Therefore
nothing can be said about D2k. As an example of a demo :) look at the MythOS package that I
threw - although there is not much information, you can understand the principles of the internal
structure and decide whether it is interesting or straight to the trash.
Sincerely, Artem
RT>> this is not good.
OG> I just implemented what I wanted :) when the system is ready, no one
OG> is stopping you from writing a navigator ala AMIGA WorkBench: P
OG> Moreover, you can change everything in the system! at least 100% of the entire interface...
Give me at least a little information about how it works? How difficult is it to change the interface, for example? Again referring to MythOS - there this is done by replacing one
file of approximately 1.5 KB or adding the user's own object libraries.
Regards, Artem
C ya in nE>
Once Artem O. Kozakov tapped Oleg Golenkoff on the keyboard:
AOK> look at the MythOS package that I threw - although there is not much information, you can
AOK> understand the principles of the internal structure and decide whether it is interesting or
AOK> straight to the trash.
To be honest, I still don’t understand how to write for it :( and the interface in MythOS
leaves much to be desired.... :(
And about the docks.... now I have finished the first chapter of the book "How to write a program
for Doors 2000" which describes the complete structure of the system, a bunch
of examples of writing in ASM, the general concept and much more.... (today it is 56 pages in MSWORD97 with a bunch of illustrations and diagrams!)
In the second The chapter will tell you how to create your own modules and components
for D2K... In the third chapter - the creation and compilation of complete applications for
D2K....
AOK> Sincerely, Artem
OG> My dear! For your information, I have been “licking” my doors since
OG> 1996!
Wow patience!
OG> And during this period the system changed not only the appearance but also the
OG> ideology and kernel by 100%!!!
Imho, during this time you gained a huge experience in coding. Continue in the same
spirit.
OG> So don’t put me on a par with the pioneers!
I don’t consider you a pioneer.
██▓▓▓▒▒▒░░░ Sergey aka Cyber from Cobra Software.
█▓▓▓▒▒▒░░░ 500:322/62 500:322/67.16
... [I ZX] [Beer] [Storm] [Turbo Commander] [ZXNet] [FidoNet] [Offspring]
perverts. :)
OG> PS: can anyone help with the ISDOS reading/writing firewood
what exactly do you need?
OG> & CP/M ?
to Kirill Frolov.
[ WBR, Oleg. ]
[ 13:49 2 August XXXV A.S. ]
Dear Oleg.
In a chit of 01 Jan 00 Oleg Golenkoff wrote to Artem O. Kozakov:
OG> And about the docket.... now I have finished the first chapter of the book "How to write
OG> a program for Doors 2000" which describes the complete structure
OG> of the system, a bunch of examples of writing in ASM, the general concept and much
OG> more.... (today this 56 pages in MSWORD97 with a bunch of
OG> illustrations and diagrams!)
Great. How about the same in AC-EDIT? :)
OG> The second chapter will tell you how to create your own modules and
OG> components for D2K... In the third chapter - the creation and compilation of
OG> complete applications for D2K....
That is. Since 1996, 56 pages have been written describing a non-existent
system? If not, privately send me your Doors again (I rubbed it
as soon as I saw it, although I have 4Gb of 6.3Gb free on the drive), and
at least one application to the conference. Under pink floyd, at least there was a reader
of html files. And all the same, it was my and Max’s great stupidity and
my ranting about pf, in logros then as well. And in the doors I
don’t see anything at all. Prove the opposite.
Cordially yours.
Once Tue 1 Aug 2000 at 13:47:10 Oleg and Artem were arguing about Doors'2ooo:
D2K_LAST.$z
OG> under D2K... In the third chapter - the creation and compilation of
OG> complete applications under
OG> D2K....
In text - to the masses !
▒▒▓▓▓ ▄▀█▀▀▀ ▓▓▓▒▒░░░ Sincerely yours, Yuri /I \
▒▓▓▓ ▐▌▀█▀ ▓▓▓▓▓▓▒▒▒░░░░ Jerri / Alien Factory \ZX/
it doesn’t work very quickly and there aren’t many workers there yet. I would like to hope that
spectrums will not have to be turbocharged up to 21 MHz... one of the glitches I noticed is that if
you move the folder icon, then it sometimes opens by itself - you can also
scatter all the bytes across the screen :)))))))))))
Now more seriously. The cries of some comrades about the incorrectness of the offtopic
interface are unfounded, because this type of interface can be seen not only in Windows, but also in many other places (KDE, iceWM, GNOME...) and, in my opinion, of the graphical interfaces this type is the most convenient and logical. And for stubborn lovers of simplicity
you can make a console :)
WBR, Sergei Dubarev
OG> will be :)
OG> PS: I threw this in to remind you that the project is not down!
So you could tell in more detail. Look, someone will help ;)
╥ ╥│ ╥ ╥ ,│, ╔╦╗╥ ╥╔╡╞═╗╔═╗╔═╡╥ ╥ ,│, Powered __
║│║╠═╗║│║ ─╬─ ║║║╚═╣╚═╗ ║╠═╝║ ╚═╣ ─╬─ by __/ Amiga \_\/
OG> apparently we will have to redo the entire mechanism from scratch :(
Is it really so difficult? In general, tell us in more detail how they
now drag around - maybe I can recommend something. Better with soap.
OG> Amiga rulez? :) I understood everything, I will take everything into account when remaking...
;)
OG> And about the docks.... now I have finished the first chapter of the book "How to write
OG> a program for Doors 2000" which describes the complete structure of the
OG> system, a bunch of examples of writing in ASM, the general concept and much
OG> more.... (today it is 56 pages in MSWORD97 with a bunch of
OG> illustrations and diagrams!)
Once upon a time, Mon Jul 31, 2000, Oleg Golenkoff and Nicolas Davidov thought on the topic:
Doors'2ooo: D2K_LAST.$z
OG>>> With such a general approach.... it will definitely bend :(
OG>>> well, yes... but is the interface a by-product? :(
ND>> and what not?
OG> and what yes? Are you satisfied with the is-dos interface?
imagine yes. If only it had died and supported 512x192...
ES> And in the doors I don’t see anything at all. Prove the opposite.
uh-huh.
// 2OlegGolenkoff: will there be some kind of SDK for doors? look, we
will write something...
zmej//sclr/rzl ___.______._____________.____________
zmej#chaosite.com ` [-zx\\_[-poweramiga zine\\_[-lowres art\\__
C ya in nE>
Somehow Eugene Sobolev tapped Oleg Golenkoff on the keyboard:
OG>> And about the docket....
OG>> (today it is 56 pages in MSWORD97 with a bunch of illustrations and
OG>> diagrams!)
ES> Great. How about the same in AC-EDIT? :)
In principle, it’s possible... to draw tables & make illustrations in the form of *.scr
ES> That is. Since 1996, 56 pages have been written describing a non-existent
ES> system?
Are you kidding me? since 1996, it has changed a hundred times... and I only
recently wrote the doc, since everything was in drafts...
ES> If not, privately send me your Doors again (I rubbed it
ES> as soon as I saw it, although I have 4Gb of 6.3Gb free on the drive), and
ES> at least one application to the conference.
Rubbed!? apparently for the better :) I think it doesn’t make sense, since I threw the subj
only for the purpose of showing that the project is not dead...
ES> Under pink floyd, at least there was a reader of html files. And all the same, it was
ES> my and Max’s great stupidity and my ranting about pf, including logros
ES> then.
Sorry, such a reader takes an hour to write :)
ES> And in the doors I don’t see anything at all. Prove the opposite.
I won’t prove anything - it’s not in my rules. There will be something to look at
I’ll throw it in the echo.!
PS: As for the history of the creation of the Doors, I’ll throw a piece frombooks...
C ya in nE>
03 Aug 00, 14:37,
Oleg Golenkoff (2:451/19.16) wrote to Nicolas Davidov
OG> AHA! Now, if it hadn’t slowed down yet and the kernel wasn’t 48 :) and
OG> the mouse would have been screwed by someone and that the screw could have been cut by any size and not
OG> unfortunate 96...
Well, firstly 128 meg. Secondly, /19.5 has a tool that supposedly allows
to connect as many devices as desired.
OG> then I would say the steering wheel...
WBR, Sergey! [I ZX] [ZXNetBY RC] ZXNet -=> 500:152/4
FIDONet -=> 2:451/16.71
np: silence (Winamp is not active ;-)
... mailto: doc...@mailru.com
C ya in nE>
SD> I looked at it just now - it’s very nice :) why repeat the main mistake of M$
SD> - depicting a crooked falling door? ;) they depicted a crooked window - and
SD> the OS turned out like this...
Cough! Let's assume that this is a joke: P
[...skip...]
SD> Now it’s more serious. The cries of some comrades about the incorrectness of the
SD> offtopic interface are unfounded, because this type of interface can be seen
SD> not only in Windows, but also in many other places (KDE, iceWM, GNOME...) and,
SD> in my opinion, of the graphical interfaces this type is the most convenient and logical. And
SD> for stubborn lovers of simplicity, you can make a console :)
which is self-evident.... :)
C ya in nE>
SS> IMHO, during this time you have gained a lot of experience in coding. Continue in
SS> in the same spirit.
After the subject is completed, he will sit and think - but
it was possible to do this and that - I know from my own experience ;)
As they say, a good thought comes later :)
Dear Oleg.
In a chit of 03 Jan 00 Oleg Golenkoff wrote to me:
[skip]
OG> PS: As for the history of the creation of Doors, I’ll throw in a piece from the book...
Did I ask you about this? I asked for a document on the kernel from your “book”
to find out what else is there besides the arrows and how it’s done. Or
maybe there are fears that everyone will immediately rush to write software for Doors?
As for the history of creation, you will tell it to grateful descendants.
P.S. I would really like to see a #?.html reader in the final version.
Cordially yours.
C ya in nE>
OG> 1.Read dir
OG> 2.Read file
OG> 3.Write file
OG> 4.Create dir
OG> 5.Delete dir
OG> 6.Delete file
This is more of an fs driver. It can also be on a screw and in the frame.
But don’t you need to open the device? :)
And at what level is caching performed? do you have a memory manager?
give me some info, in short. I will criticize. :)
[ WBR, Oleg. ]
[ 16:39 4 August XXXV A.S. ]
Once upon a time Thu 3 Aug 2000, Oleg Golenkoff and Nicolas Davidov thought on the topic:
Doors'2ooo: D2K_LAST.$z
OG>>> I prefer to silently go about my business...
OG> AHA! Now, if it hadn’t slowed down yet and the kernel wasn’t 48 :) and the mouse
OG> would have been screwed by someone and that the screw could have been cut to any size and not the unfortunate
OG> 96...
... then would it have been doors? ;)
OG> then I would say the steering wheel...
who doesn’t? but the most important thing is that it works, but the doors are not there yet.
ES> Did I ask you about this? I asked for a document on the kernal from your “book”
ES> to find out what else is there besides the arrow and how it’s done.
you will have a document too :)
ES> Or maybe there are fears that everyone will immediately rush to write software for
ES> Doors?
out of the blue :)
ES> And as for the history of creation - you will tell it to grateful descendants.
cough :) interesting what will they say...
ES> P.S. I would really like to see a #?.html reader in the final version.
It will definitely be there! - if you write it, of course :)
C ya in nE>
[ ..gnawed off by the evil three-headed Snake.. ]
OG> this is more of an fs driver. isdos after all can be on a screw and in the frame.
OG> But you don’t need to open the device? :)
OG> and at what level is caching performed? is there a memory manager?
Yes! but if I had a document from the dos, then I would write it myself :( really
0 free time! :( and grabbing at everything is also not the best idea...
OG> let’s get the info, in short. I’ll criticize. :)
I’ll give the info! but I can criticize myself :)
C ya in nE>
C ya in nE>
OG> He will definitely be there! - if you write it, of course :)
This is unlikely. Spectrum needs this as much as the Doors (read
- not necessary). And I need this as much as you need it (read -
just as doubtfully necessary). But it seems like who was whistling about html
viewer on the Spectrum for 2 hours? Or did I hear it? So I made
a proposal... By the way, in a normal OS there should be something for viewing
documentation, and it is very desirable for this something to support links to
other documents (for linking documents and a more holistic
perception of information by the user). HTML - this is how I understood the last
century, but probably some kind of Doors Guide is already on the way, which will help everyone. Am I guessing right?
Cordially yours.
ND>> nothing.
OG> let him who has eyes see :) but seriously, the one who wanted to write
OG> is not soap to me! and not with idiotic statements that this is a sax, no one needs this
OG>, it would be better to do something else.... etc. and with
OG> specific proposals!
When did I say that this is a Saxon? I proposed a very specific thing -
to make an HTML viewer, especially since according to the author
the time it is planned to spend on this is 2 hours. And documentation for Doors in HTML (Sort of
ZX-HTML, of course). The text format is ZXWord, and even supports Ac-Edit
(Sort of ZX-ANSI). Ask the author of Ac-Edit if he plans to support Doors? Will there be Alasm (Some kind of DAlasm) under Doors?
And in general, establish contacts with developers. Why are you laughing? I
seriously...
C ya in nE>
zmej//sclr/rzl ___.______.___________________.____________
zmej#chaosite.com ` [-zx\\_[-poweramiga zine\\_[-lowres art\\__
╥ ╥│ ╥ ╥ ,│, ╔╦╗╥ ╥╔╡╞═╗╔═╗╔═╡╥ ╥ ,│, Powered __
║│║╠═╗║│║ ─╬─ ║║║╚═╣╚═╗ ║╠═╝║ ╚═╣ ─╬─ by __/ /
╚╩╝╚═╝╚╩╝ '│` ╨│╨╞═╝╞═╝ ╨╚═╡╨╞═══╝ '│` Amiga \_\/
ND>> opinions about nothing? :) because, I already told you, what you threw is nothing.
OG> let him who has eyes see :) but seriously, the one who wanted to wrote to me
and what did they write to you, if it’s not a secret?
OG> not soap! and not with idiotic statements that this is a sax, this is not for anyone
did I personally tell you that this is a sax?
OG> it is necessary, it would be better to do something else.... etc. and with specific
OG> proposals!
I’m glad for you. for that matter, then to someone from your brethren N number
months ago I even sent some source codes of one program for dors, does that not count?
OG>>> AHA! Now, if it hadn’t slowed down yet and the kernel wasn’t 48 :) and the mouse would have been screwed up by
OG>>> and that the screw could have been cut to any size and not
OG>>> unfortunate 96...
ND>> ... would it have turned out to be doors? ;)
ZS> why in soap? SDK - into this echo.
OK! What do you mean by SDK for Speck? More precisely, what functions should be
implemented?
ZS> everyone will see how slender and beautiful the new OS is, and will immediately rush to write mountains of
ZS> software for it.
breathe more smoothly... you say.... :|
ZS> // I'm serious.
I hope...
Minisoft avec NRJ^Ascendancy Creative Labs [I ZX] [I AMIGA] [I BEER]
ZS>> mountains of software for it.
OG> breathe more smoothly... you say.... :|
uh-huh.
OS is not a piece of hardware a-la Sprinter. There is no need to buy it.
// or is it still necessary? %)
ZS>> // I'm serious.
OG> I hope...
in all matters relating to the Spectrum, I'm rarely not serious.
this, after all, is the platform that raised me... and it's dear to me like
I don't know what. I'll pay for the Spectrum. >8)
Minisoft avec NRJ^Ascendancy Creative Labs [I ZX] [I AMIGA] [I BEER]
ASCENDANCY HQ: ascen...@mail.ru http://www.ascendancy.homepad.com
ZX-Spectrum Banner NetWork: http://zxbn.narod.ru Let's United!
Minisoft avec NRJ^Ascendancy Creative Labs [I ZX] [I AMIGA] [I BEER]
ASCENDANCY HQ: ascen...@mail.ru http://www.ascendancy.homepad.com
ZX-Spectrum Banner NetWork: http://zxbn.narod.ru Let's United!
Minisoft avec NRJ^Ascendancy Creative Labs [I ZX] [I AMIGA] [I BEER]
ASCENDANCY HQ: ascen...@mail.ru http://www.ascendancy.homepad.com
ZX-Spectrum Banner NetWork: http://zxbn.narod.ru Let's United!
OG> Yes! but if I had a document from dos, I would have written it myself:(
no problem. It should be enough:
── { Begin } ──────────────────── ───────────────────── {adj_01.txt} ──
┌────────────────────── ─────────────────┐
│APPENDIX IE 1. Structure of the device (disk) descriptor │
│ │
│0th BLOCK: (0th sector of the 0th track) │
├───────────────────── ──────────────────┤
│sme- length- comments │
│on │
│nie │
├──┬──┬───────────── ────────────────────┤
│ 0│ 2│Reserve │
│ 2│ 8│Device name │
│10│ 3│iS-DOS attribute: "DSK" │
│13│ 5│Reserve │
│18│ 2│Device size │
│ │ │(in blocks of 256 bytes) │
│20│ 2│ number of the 0th block of the main catalog - │
│ │ │ga │
│22│ 1│Number of tracks on the device │
│23│ 1│Disk type (0/1): │
│ │ │ 0 - 40/80 tracks │
│ │ │ 1 - 1/2 sides │
│24│ 1│Sector size: │
│ │ │1/2/4: 256/512/1024 bytes │
│25│ 1│Number of sectors per track │
│26│ 1│Reserve │
│27│ 1│Controlsum of 32 byte │
│ │ │descriptor ????_dos.sys │
│28│ 2│Reserve │
│30│ 2│Date │
│32│32│Descriptor ????_dos.sys │
│64│16│Table of sector numbers │
│ │ │on the track │
├──┴──┴───────────── ────────────────────┤
│ 1st BLOCK: Device bitmap.│
│ 1 bit/block: 0-free/1-busy│
└──────────
The ????_dos.sys descriptor with offset 32
is placed in the 0th block by the program con.com and
read by boot.sys.
── { End } ───────────────────── ────────────────────── { adj_01 .txt } ──
── { Begin } ──────────────────── ───────────────────── {adj_09.txt} ──
┌───────────────────────────
│ APPENDIX 9. Resident vector of the file service │
│ / bkfcb(#35) DUD.SYS / │
│ │
│ offset name length comment │
│ tion │
││
│ -8 DSIZE 2 Open device size in blocks │
│ -6 BMSIZ 2 Bitmap size in bytes (see APPENDIX AND │
│ -4 FCBA 2 User file descriptor address │
│ -2 1 Temporary file number │
│ -1 FNUMB 1 file number (#FF if the file is not open) │
│ │
│ 0 32 Descriptor of the current (open) file: │
│ 0 FNAME 8 Name │
│ 8 FTYPE 3 Type │
│ 11 FSTAT 1 File status register Bits. (0/1): │
│ 0 - deleted/exists │
│ 2 - read-protected(1) │
│ 3 - write-protected(1) │
│ 4 - visible/hidden file │
│ 5 - file/directory (root file) │
│ 6 - segmented/continuous │
│ 7 - protected from deletion(1) │
│ │
│ 12 FLSA 2 Default load address │
│ 14 FLENG 3 Length │
│ 17 FSDBN 2 segment descriptor block number │
│ (For continuous file - number of the zero │
│ blockfile) │
│ 19 WRKST 1 "Special" │
│ 20 6 Reserve │
│ 26 FSUM 2 File checksum │
│ 28 FTIME 2 Time │
│ 30 FDATE 2 Date │
│ │
│ 32 23 Descriptor of the current (open) directory │
│ (internal) │
│ 32/0 CATLG 8 Name of the current directory │
│ 40/8 3 spaces (directory type) │
│ 43/11 1 CSR of the directory │
│ 44/12 CDLSA 2 CBBN of the parent directory │
│ 46/14 *CSIZE 2 Directory size in bytes │
│ 48/16 *LEVEL 1 Subdirectory nesting level │
│ 49/17 CSDBN 2 descriptor block number segment │
│ 51/19 CBBN 2 number of the 0th block of the directory │
│ 53/21 *NFILE 1 Total number of files (including the directory itself │
│ and deleted ones) │
│ 54/22 *NEFIL 1 Number of files without a directory and deleted │
│ │
│ 55 1 │
││
│* - unused variables in the external directory │
│ descriptor. │
└───────────────────────────
── { End } ───────────────────── ────────────────────── { adj_09 .txt } ──
OG> truth
OG> free time 0! :( and grabbing everything is also not a good idea...
Minisoft avec NRJ^Ascendancy Creative Labs [I ZX] [I AMIGA] [I BEER]
ASCENDANCY HQ: ascen...@mail.ru http://www.ascendancy.homepad.com
ZX-Spectrum Banner NetWork: http://zxbn.narod.ru Let's United!
3.08.2000 at 15:58 Dmitry Naboka wrote to Sergey Selev:
SS>> Continue in the same spirit.
DN> After the subject is completed, he will sit and think - but
DN> it was possible to do this and that - I know from my own experience ;)
DN> As they say, a good thought comes later :)
And then the first service pack will be released ;)
Bye, Yuri.
[I ZX] [Chemists] [For full address] [Ski poles]
/_500:322/33@ZXNet_/ /_dang...@bigfoot.com_/ /_dang...@mail.ru_/
/_2:462/93.33@FidoNet_/
... Dig yourself a hole and make it easier for others.
╥ ╥│ ╥ ╥ ,│, ╔╦╗╥ ╥╔╡╞═╗╔═╗╔═╡╥ ╥ ,│, Powered __
║│║╠═╗║│║ ─╬─ ║║║╚═╣╚═╗ ║╠═╝║ ╚═╣ ─╬─ by __/ /
╚╩╝╚═╝╚╩╝ '│` ╨│╨╞═╝╞═╝ ╨╚═╡╨╞═══╝ '│` Amiga \_\/
╥ ╥│ ╥ ╥ ,│, ╔╦╗╥ ╥╔╡╞═╗╔═╗╔═╡╥ ╥ ,│, Powered __
║│║╠═╗║│║ ─╬─ ║║║╚═╣╚═╗ ║╠═╝║ ╚═╣ ─╬─ by __/ /
╚╩╝╚═╝╚╩╝ '│` ╨│╨╞═╝╞═╝ ╨╚═╡╨╞═══╝ '│` Amiga \_\/
OG> I think this will happen!
as it happens, throw it into the Spectrum echoes.
// throw it BEFORE you exit the doors. ready-made software is needed in order for
people to become interested in the system. Agree with the groups writing popular
software [well, I don’t know what’s out there - graphic editors, music editors, assemblers,
something else] - let them make an expanded/improved version for doors...
in short, we need to promote the system. otherwise all the work will go down the drain.
ZS>> OS is not a piece of hardware a la Sprinter. there is no need to buy it. // or is that all
ZS>> necessary? %)
OG> in order to sell something, you need to write it first :)
ja-ja. 8)
_dworkin//rzl/cc/sclr zmej#chaosite.com
07 Aug 00 23:59, Eugene Sobolev wrote to Oleg Golenkoff:
ES> When did I say that this is a Saxon? I proposed a very specific
ES> thing - to make an HTML viewer, especially since according to
ES> the author's assurances it is planned to spend 2 hours on this. And documentation for
ES> Doors in HTML (Sort of ZX-HTML, of course). Text format - ZXWord,
ES> and even Ac-Edit support (Sort of ZX-ANSI). Ask the author of
ES> Ac-Edit if he plans to support Doors?
Somehow I didn’t think about it... Somehow I haven’t delved into the full depth of this system.
So far it is only clear that the author has been writing a program for N years that, in fact,
does nothing... Somehow it’s not right to release all this...
- Alone Coder
Minisoft avec NRJ^Ascendancy Creative Labs [I ZX] [I AMIGA] [I BEER]
ASCENDANCY HQ: ascen...@mail.ru http://www.ascendancy.homepad.com
ZX-Spectrum Banner NetWork: http://zxbn.narod.ru Let's United!
Minisoft avec NRJ^Ascendancy Creative Labs [I ZX] [I AMIGA] [I BEER]
ASCENDANCY HQ: ascen...@mail.ru http://www.ascendancy.homepad.com
ZX-Spectrum Banner NetWork: http://zxbn.narod.ru Let's United!
Minisoft avec NRJ^Ascendancy Creative Labs [I ZX] [I AMIGA] [I BEER]
ASCENDANCY HQ: ascen...@mail.ru http://www.ascendancy.homepad.com
ZX-Spectrum Banner NetWork: http://zxbn.narod.ru Let's United!
OG> we are writing.... together with RUM, so things went a little faster....
will you make me happy for the New Year?
For this Au Revoire, CompoWellcome. aka:
2:5085/1.149
2:5085/26.51
OG> Ops!? this is even interesting.... but what exactly?
I’m also interested in this, it’s easy to forget...
these were the source codes of test 4.30, which you asked for for the sake of procedures for determining
external devices.
db 'Ku,Oleg!', 0dh,0ah,'$'
not so long ago, Oleg Golenkoff wrote about something to Yuri Potapov:
OG>>> under D2K... In the third chapter - the creation and compilation of complete
OG>>> applications under D2K....
YP>> In text - to the masses !
OG> after such conversations, I have big doubts that the masses need this!?
OG> whoever is interested - he wrote in nonsense...
and there are also many silent readers! :)
Good luck,Oleg !
[ Sandra ] [ZX] [Intel Must Die] [CoModerator of NetMail] [Punks Not Dead]
Dear Dima.
In a chit of 13 Jan 00 Dima Bystrov wrote to me:
ES>> Ac-Edit support (Sort of ZX-ANSI). Ask the author of Ac-Edit
ES>> if he plans to support Doors?
DB> Somehow I haven’t thought about it... Somehow I haven’t delved into the full depth of this system.
DB> So far it is only clear that the author has been writing a program for N years, which,
DB> in fact, does nothing... Somehow it’s not right to release all this...
And I had no doubt that I didn’t think about it. I always take any idea to the point of absurdity and see what happens. In a situation with all these _axes_, writing any good software for them is already absurd. AC-EDIT is
good software, it’s understandable for me now, who is sitting on an Amiga and rarely uses spec
software, and VL agreed with this yesterday. Writing a version of AC-EDIT under
ISDOS is already between the real/ and the unreal (IMHO), again it needs to
be rewritten, and not just adapted. So TRDOS is the optimal rulez for the Spectrum, ISDOS is a potential rulez if it is improved. Everything else
goes to the garden.
Cordially yours.
OG> however :( not everything is so fast.... here you still need to figure out the isdos inside :(
it’s not necessary. It would be easier to find a person who knows the isdos like his own 10
fingers. You will need more than one week of dense, everyday
proceedings.
Let your enemies, Eugene, die without sons!
14 Aug 2000 at 22:17, Eugene Sobolev ═> Dima Bystrov:
ES> Spectrum, ISDOS potential rulez if it is modified. Everything
ES> the rest
ES> goes to the garden.
unfortunately, it is impossible to modify the isdos without losing compatibility. at one time I very seriously studied this possibility, tinkered with it, disassembled
the three lower levels of the system, and... that's it. Only extenders are possible, such as dosx from a
wild mailer - he, in fact, uses isdos only as a file system, everything else is his own. and even then he has wild limitations.
it’s impossible to climb the tree and not get your ass ripped off.
[ WBR, Oleg. ]
[ 01:17 15 August XXXV A.S. ]
Minisoft avec NRJ^Ascendancy Creative Labs [I ZX] [I AMIGA] [I BEER]
ASCENDANCY HQ: ascen...@mail.ru http://www.ascendancy.homepad.com
ZX-Spectrum Banner NetWork: http://zxbn.narod.ru Let's United!
Minisoft avec NRJ^Ascendancy Creative Labs [I ZX] [I AMIGA] [I BEER]
ASCENDANCY HQ: ascen...@mail.ru http://www.ascendancy.homepad.com
ZX-Spectrum Banner NetWork: http://zxbn.narod.ru Let's United!
Minisoft avec NRJ^Ascendancy Creative Labs [I ZX] [I AMIGA] [I BEER]
ASCENDANCY HQ: ascen...@mail.ru http://www.ascendancy.homepad.com
ZX-Spectrum Banner NetWork: http://zxbn.narod.ru Let's United!
> OG>> after such conversations, I have big doubts that the masses need this!?
> OG>> whoever is interested - he wrote in nonsense...
> WS> and there are also many silent readers! :)
OG> here after the announcement of the general cry... people somehow showed a strong desire
OG> to take part in writing software for the subzh! so I think that very
you see, but he complained...
OG> maybe even earlier...
nu-nu ;-)
OG> well, let’s say I never received anything :( but QUASAR sent them to me!
well, let’s say I didn’t say that I sent them to you, and who gave them to me
for a damn. They asked specifically for the back, so I sent them.
03 Aug 00 09:42, Oleg Golenkoff wrote to Oleg Grigoriev:
OG>>> PS: can anyone help with the ISDOS read/write drivers
OG>> what exactly do you need?
OG> 1. Read dir
OG> 2. Read file
OG> 3.Write file
OG> 4.Create dir
OG> 5.Delete dir
OG> 6.Delete file
Reference sheet on the iS-DOS file system. Version 1.1.
This file is compiled on the basis of widespread information about the iS-DOS system
and based on the analysis of *.img disk images. All kinds of additions and clarifications are welcome. This describes only the old disk structure used in
versions of the system released before 1998; in the new version of the system iS-DOS'98
the disk structure was changed, but I do not have complete information.
At the end there are sources of information, but sometimes they contain errors
and there is simply a lack of information, questions arise that are left unanswered.
Here in general there is more information and some errors have been corrected.
The iS-DOS file system can exist on any block device
which can have from 3 to 65535 blocks. The size of one block is always 256
bytes. Blocks are numbered from 0 to maximum. On block 0 of each device
there is a DEVICE DESCRIBER which contains the device size,
description of the physical media, disk name andother system parameters.
The device descriptor also contains the number of the initial block of the main directory.
There is always a main directory on the disk; it cannot be deleted. The main directory
always contains descriptors for two files: a descriptor for the
directory itself with the name "FF-dot" and a disk descriptor, which includes
DEVICE DESCRIBER (0 block) and DISK USE BITMAP (always
starts with 1 block). In the disk occupancy bitmap, each bit represents the occupancy of one device block. The disk descriptor file is always called
device.sys and has all the bits set in the attribute byte - it is an invisible
system directory and cannot be read, written, or deleted, and is
CONTINUOUS (other files may be segmented). After the disk occupancy map, the MAIN DIRECTORY usually begins, which can be segmented or continuous. In any case, its length cannot exceed 16 blocks or
128 file or directory descriptors. It is clear that any file or directory file
always occupies an integer or zero number of blocks. The main directory and the disk occupancy bitmap file cannot have a length of zero.
In addition to the above files, the main directory always contains a boot.sys file
if the DISK IS BOOT. The boot.sys file contains
the system boot loader which loads into memorycomputer file is_dos.sys
from the same disk and launches it. All bits in the attribute bytes of the boot.sys file are also
set. To make it easier to find the is_dos.sys file, its descriptor is duplicated in the DEVICE DESCRIBER on block 0. The system file with the system image may have a name different from is_dos.sys, but system utilities require ????_dos.sys. For a boot disk, the is_dos.sys file must be
CONTINUOUS! To boot from floppy disks via TR-DOS, a disk with kilobyte sectors is used. The numbers of sectors used are: 1,2,3,4 and 9.
In sector 9 there are 0 tracks and the boot.sys file is located, 4 blocks long.
The iS-DOS file system for the user is similar to the MS-DOS file system,
from the inside there are significant differences. There is a developed system of subdirectories - each directory can contain subdirectories, which in turn may contain other directories. But the nesting level of directories cannot exceed 6. The main directory has nesting level 0, its subdirectories have level 1... The total number of files or directories in one
directory is limited to 128 file descriptors INCLUDING THE DESCRIBER OF THE DIRECTORY ITSELF.
Each directory has a descriptor of itself - the most The first file descriptor
in a directory that has the name of that directory. Files, like directories, can be
contiguous or segmented. Only device.sys files (bit-mapbusy
device) and boot.sys (system bootloader) are always continuous. Some
programs also impose restrictions on the type of files and work only with
continuous or only with segmented ones. Continuous files occupy one continuous area on the disk equal to their length (rounded up to a block) and can be read at high speed. Segmented
files can contain from 0 (a zero-length file) to 85 segments of size from
0 to 255 blocks of 256 bytes, they can take a long time to read,
but it is possible to add or remove blocks from anywhere in the file
(for example, you can insert several blocks in the middle of the file). The file length in its descriptor is limited to 16 MB, and the maximum size of an iS-DOS disk can be the same. But if the file is segmented, then its size is limited to only
5548800 bytes (try multiplying 256 bytes by 255 blocks in 85 segments).
The contiguous file descriptor directly specifies the number of the file's starting block
on disk. A segmented file descriptor points to a block of
segment descriptors, three bytes per segment (starting block number and length), hence
85 segments. For a segmented file of zero length, the block of descriptors
segments is filled with zeros.
CHARACTER ENCODING IN THE NAMES OF FILES, DISKS AND DIRECTORIES.
In the iS-DOS system for characters withcodes 0x00..0x7F accept ASCII character encoding, for characters with codes 0x80..0xFF 866-alternative encoding is accepted. The names of files, disks and directories can use numbers, lowercase and capital letters of the Russian and Latin alphabet, as well as symbols with codes 0x23, 0x24, 0x26, 0x2B, 0x2D, 0x3D, 0x5F, 0x60. The remaining characters
cannot be used - this may lead to inaccessibility of files and directories.
DEVICE DESCRIBER STRUCTURE.
Offset from Size Description
beginning of block
0x00 2 reserve
0x02 8 disk name
0x0A 3 0x44, 0x53, 0x4b -- iS-DOS disk attribute.
0x0D 5 reserves
0x12 2 device size in blocks
0x14 2 number of the starting block of the main directory
0x16 1 * number of tracks on the disk
0x17 1 * disk type
0x18 1 * size sectors
0x19 1 * number of sectors on track
0x1A 1 reserve
0x1B 1 checksum descriptor ????_dos.sys
0x1C 1 reserve
0x1E 2 device creation date
0x20 0x20 descriptor ????_dos.sys
0x40 0x10 *table of sector numbers on a track
Data fields in the structure of the device descriptor
indicated by the symbol "*" asterisk are used only for floppy magnetic disks. Fields marked
as "reserve" and the undescribed data area after the table of sector numbers
are not recommended to be used.
The sector size is indicated in blocks and can be 1, 2 or 4 blocks (256, 512 or
1024 bytes, respectively). Only two bits are used in the disk type byte:
bit0=0 40 tracks, otherwise 80, bit1=0 I side, otherwise 2. Sector numbers in the table with offset 0x40 are indicated in the form that TR-DOS understands them, i.e.
reduced by one, in reality they are located in the sector header on the disk values are greater by
one. In the table, the sectors are located in the order in which
they are located on the track. The file descriptor field is_dos.sys contains a copy
of the descriptor of such a file located on disk in some directory (any)
and is only necessary for loading the system image into memory from the boot disk.
The descriptor checksum field is the sum of all 32 bytes of the descriptor
modulo 2 (this is XOR).
STRUCTURE OF A DISK USE BITMAP.
The disk busy bitmap file has one bit for each
device block. The length of this file is 8 times less than the size of the device in blocks.
If the byte number in the file is designated by the letter F, the numberbit with the letter B, and the block number on the device with the letter N, then each bit in the file can be put in
correspondence to the block numbers on the disk using the following formulas:
F = N div 8 and B = 7 - (N mod 8).
The div operation is an integer division, and mod is the remainder of the division.
For occupied blocks, the bits are set, for free ones are cleared (contain zeros).
STRUCTURE OF THE BLOCK OF SEGMENT DESCRIPTORS.
In the directory, the descriptor of a segmented file contains a link not to the
initial block of the file (as in a continuous file), but to the block of descriptors
of segments, which determines the location of the files on disk. The segment descriptor block is one block of the iS-DOS device and has a size of 256 bytes. The very first byte in the segment descriptor block contains the total number of segments in the file and can be in the range from 0 to 85. The remaining bytes are divided
into records of 3 bytes, the first two from which indicate the starting block of a segment on the disk, and the third indicates the length of the segment, which can range from 1 to 255 blocks. For zero-length files, the block of descriptors
segments must be filled with zeros, but whether this is always so unknown,
it is better to rely on the file descriptor in the directory.
FILE AND DIRECTORY DESCRIBER STRUCTURES.
Files and subdirectories are described in the directory in a 32-byte descriptor.
Purpose of fields file descriptorthe following:
Offset Size Description
0x00 8 file name
0x08 3 file extension
0x0B 1 file attributes
0x0C 2 download address for COM files
0x0E 3 file length in bytes
0x11 2 segment descriptor block number
for segmented files or
file starting block number for
continuous files
0x13 1 special purpose byte
0x14 6 reserve
0x1A 2 file checksum
0x1C 2 file last modification time
0x1E 2 file last modification date
The checksum word is simply the arithmetic sum of all bytes
subtracted from zero. The checksum is used by the system when loading and running executable COM files. The special purpose byte
of the boot.sys and device.sys files is always set to 0xFF, for the remaining
files it can be used for various purposes, usually 0 is written there.
The data field designated as reserve is actually used by various
application programs.
Purpose of directory descriptor fields:
OffsetSize Description
0x00 8 directory name
0x08 3 directory extension
0x0B 1 directory attributes
0x0C 2 starting block number
parent directory
0x0E 2 directory size in bytes
0x10 1 * nesting level subdirectory
0x11 2 segment descriptor block
number for a segmented directory
0x13 2 directory starting block number
0x15 1 * total number of used
file and subdirectory
descriptors in the directory, including the descriptor of the directory itself
and deleted files
0x16 1 * number of files in the directory without
descriptor of the directory itself and
deleted files
0x17 7 reserve
0x1E 2 date of creation of the directory
Fields marked with the symbol "*" asterisk in the structure of the directory descriptor
contain correct information only in the directory descriptor located in the same
directory. In the descriptor of this directory in its parentcatalogue, these fields
may contain incorrect information. The date for all directories except
the parent
is indicated in the descriptor. For the parent directory, you should look at the creation date
of the disk in the device descriptor.
Structure of the file or directory descriptor attribute byte:
Bit Description If cleared (0) If set (1)
0 file deleted file exists
1 reserve
2 file is read-protected
3 file is write-protected
4 file invisible
5 descriptor type file directory
6 file type segmented continuous
7 file protected from deletion
Bit 0 determines whether the descriptor is used or not. Bit 5 allows
to distinguish files from directories; it MUST be set for all directories.
Since when creating a file, filling in the fields of the file descriptor responsible
for the date and time in the system is assigned to the application program, there is no
unambiguous determination of the date of creation or last modification. These fields are responsible. The system also does not itself modify these fields when accessing the file
both for writing and reading.
DIRECTORY STRUCTURE.
A directory isjust a file containing descriptors for other files and directories and
it can also be segmented or continuous. If the directory is contiguous,
a situation may arise where it will be impossible to create new files or
subdirectories in this directory. Regardless of whether a directory is contiguous or
segmented, it cannot contain more than 128 file or subdirectory handles of 32 bytes each. The directory length is limited to 4096 bytes. The very
first file descriptor in a directory contains a descriptor for the same directory and
a link to the parent directory. More complete information is contained in the directory descriptor within the same directory than in the parent directory - this is worth paying attention to. The main directory of the disk (the root directory or the 0-level directory) does not have a parent directory. The name of the main directory as written in its descriptor is defined as "FF-dot": 0xFF, 0x2E, 0x20,
0x20, 0x20, 0x20, 0x20, 0x20 and a 3-space extension. The attribute of this
descriptor is always equal to 0xE1.
That's all for now. But it seems to me that this is enough to understand how the files are located on the disk. All information is available in "notes for a programmer" written by Leontyev. And no one is a disassemblerотменял...
Minisoft avec NRJ^Ascendancy Creative Labs [I ZX] [I AMIGA] [I BEER]
ASCENDANCY HQ: ascen...@mail.ru http://www.ascendancy.homepad.com
ZX-Spectrum Banner NetWork: http://zxbn.narod.ru Let's United!
Minisoft avec NRJ^Ascendancy Creative Labs [I ZX] [I AMIGA] [I BEER]
ASCENDANCY HQ: ascen...@mail.ru http://www.ascendancy.homepad.com
ZX-Spectrum Banner NetWork: http://zxbn.narod.ru Let's United!
Wednesday August 16 2000, 18:38,
Vitaliy Nozhko (2:451/19.1) wrote to Oleg Golenkoff
[ ...skipus longus... ]
VN> ps: please send me the address where you can read real.speccy
VN> please.
VN> pps: this is where it gets interesting :-)
www.fidonet-online.com (or .ru definitely not I remember)
WBR, Sergey! [I ZX] ZXNet -=> 500:152/4
FIDONet -=> 2:451/16.71
np: Avaria - Pei Pivo
... mailto:doc...@mailru.com
26 Aug 00 19:56, Sergey Orlov -> Vitaliy Nozhko:
VN>> where from the Internet you can
VN>> read
VN>> real.speccy
SO> www.fidonet-online.com (or .ru I don’t remember exactly)
www.fido-online.com
See my origin when I write from there ;) .
With the best - Wlodek. mailto: wlb...@chat.ru
[ZX] [Golyanovo] [Radio "Retro" 72.92 MHz]