Some thoughts about the axes. Dan- This article was written quite a long time ago under the impression of conversations with himself (With SA- MIM!:)) XOR. He even said that there are people who have similar ideas and he will publish them in the next issue "Paragraph", but for now I'm reading some of these articles I haven't seen it. So I decided not to throw it away this text into oblivion, but use it to increase the volume of the native "Moore- zilki". --------------------------------------- What's wrong with is dos? I answer point by point, starting with the most serious deficiencies kov: A) Incompatibility with Tr dos. The one who thinks tr dos is outdated/does not reflect/ does not allow/etc. doesn't want to accept objective reality: everything that has been done on the speck (not counting the loading container) lano under tr dos. And just like that take it all and throw it away (adapt no one will do anything) no one agreed sits. And even if programs are written under is dos or other non tr dos system I, for example, will think about buying one program or not (if the program is under isdos, then I definitely have it even with a friend I won’t copy for free); 1) Everything done in isdosslows down terrible force. From this point it follows several sub-points: a) Copying tr dos/ms dosis files dos represents masochism, I already I'm not talking about trying to transfer files from ms dos to tr dos and vice versa the essence of this system. Despite the fact that such operations have to be done very often and with large amounts of information - only no one works under is dos, because because people on Speck are not accounting departments after all, they lead and do not use it only like a typewriter/calculator. Im need graphic/musical/etc. editors/assemblers/packers/and everything other. Need to merge a lot of files into one release - and this is often in tr dos done manually, under is dos that's all impossible. Serious people will say: yes After all, it’s not serious - stitching programs into one file (game, for example). If you if you want to make a game, create it for it directory, subdirectories, indicate these subdirectories in setup (.ini?), in general install (what a scary word ) - this is what the OS is programmed for. And I’m a spektrumist and, besides, I love sometimes code and if the program is < 255 sectors and occupies more than 1 in the directory file, then I consider this a flame (this is Of course, refers to ready-made programs). All this, I repeat, is impossible in isdos.b) I'm a coder and I need an assembler. Ska- I’ll tell you right away - write assembler under isdos no use. There is a simple download st file to view it with multiple forceful driving of the head on the disk causes a lot of unpleasant emotions. So what? talk about assembler with its include/incbins - even imagine scary (ugh - really some kind of horror! ). In addition, when writing the above-mentioned the assembler is reset you know how many times per unit of time. Now imagine if you every time downloaded isdos... 2) Glitches that lead (quite often) to the failure of the system itself. And since the authors of the axis at one time wanted make money from it (what are they, of course, no one reproaches - praise - clear and understandable desire) and copying system is quite a tedious task - not even by pirate copiers, not not to mention the legal way, which only perverts could come up with this all the glitches (in themselves quite harmless) tender and characteristic of anyone and not isdos programs) again very effective get on your nerves. Of course, isdos has many advantages. However the ideas contained in it, it seems to me, notThey fit the Spectrum perfectly. In general, I want to offer a number of thoughts about the ways in which it is possible to create give a new axis. First, what do I want from the new axis: 1) Compatible with trdos - at least for that level so that trdos programs without trial- lem worked under the new system; and pro- gi, already made for a new axis with the same Lanes could be launched from trdos; 2) Multi-directory; H) Maximum speed of work with dis- com: this means no fragmentation with clusters, fat, etc.; 4) Minimum restrictions on writing programs for a new axle; 5) Ability to exit programs directly into the system (without resetting the computer), availability some kind of clipboard; 6) Ability to open files according to existing programs. These are the minimum requirements. How to implement all this. Firstly, the underlying problem isthis is the standard: for- disk mat and system connection with programs (entrance/exit from the program, addresses of the res- dent programs load file/save file). The disk should be as similar as possible to normal trdos: root directory det be considered a regular trdos directory, located, as is known, at zero path. Subdirectories can be placed in end of the disk, let them grow from above down to the intersection with the last recorded ny file. Compatible with trdos dos- tiguna. It remains to develop a standard to work with programs from the system. For this needs to be found in memory for residents providing normal exit from the program, enter with loading desired file and program operation with dis- com if needed. In general, working with disk, every programmer can write tell yourself how it is done now under trdos and then the resident area can be will bang, etc. there will only be logout routine. Those. not There will be virtually no restrictions. After the development of the standard, the system itself Any programmer can write it. Nap- For example, it will be possible to make it exact Pia jemini comander, but with subdirectories and other bells and whistles - who cares want it. The main thing is that there are opportunities there will be much more of all these programs than for all currently existing boot's.
Thoughts - Some thoughts about the axes.
Share your thoughts about the article