To catch up with all sorts of loaders...

Hi, All! After some thought, I decided to speak out on this issue. du. So. 1. We get out of the Mazda storm and load the steering wheel. 2. Type a program like this: ORG #8000 LD HL,#C9F1 LD (#5CC2),HL LD HL,#???? LDSP,HL PUSH HL LD DE,(#5CF4) LD BC,#??05 JP #3D13 3. Broadcast and find out the length. 4. Go to Basic and type approximately the following: 1 CLOZE #USR 0:REM ... After REM, all sorts of heresy equal in number to oxen length of the prog minus 2. 5. Back to Tasm! There we change ORG to #5d48 and assemble. 6. Press magic and write #48, #5d at address #5d45. If such a button is missing on your computer, or its functionality is yours differs from what I assumed, then you will have to write bytes to memory in any other way. =) 7. Say CLEAR (to make it beautiful :)) and write to disk/screw/bolt/or whatever-you-have-plays-the-role-of-a-drive- la this prog. 8. Then we write down after BASIC a piece of code that it was necessary to load and change the length in sectors of BASIC. Best wishes, Oleg aka Ruiner. ps. Something got me into the epistolary genre... Not good... pps. Just like for an FAQ... Eh? How's that for an idea? For example, about the carThen start the disk, if sclerosis is not lying, they have already asked 3 times. ppps. Or did I disobey Therion? :)

Hi, Oleg! OG> Hi, All! OG> After some thought, I decided to speak out on this matter. OG> So. OG> 1. We get out of the Mazda storm and load the steering wheel. like that myself :) OG> 2. We create a program like: straight to STORME... OG> ORG #8000 org #8000,#5d48 OG> LD HL,#C9F1 OG> LD (#5CC2),HL OG> LD HL,#???? OG> LD SP,HL OG>PUSH HL OG> LD DE,(#5CF4) OG> LD BC,#??05 OG>JP #3D13 OG> 3. Broadcast and find out the length. yeah OG> 4. Go to BASIC and type approximately the following: OG> 1 CLOZE #USR 0:REM ... OG> After REM all sorts of heresy is stuffed, equal in number of sims OG> oxen the length of the program minus 2. yeah OG> 5. Back to Tasm! in STORM :) OG> There we change ORG to #5d48 and assemble.we don’t change it, but we assemble it OG> 6. Press magic and at address #5d45 write #48, #5d. Yeah, EXT-D, and the same STS. and transfer the block from #8000 to #5d48. kudos to you Tasm :) All the best. Dmitry. ..LD..X-TRADE..

Hello to you, Oleg!!! One day on the 14th of Nov 98 at exactly 01:59:00 Oleg Grigoriev wrote to All on the topic 'To catch up with all sorts of loaders...': OG> 8. Then we write a piece of code after BASIC OG> which needed to be loaded and change the length in sectors y OG> BASIC. It's all complicated, today I invented a new method ;-))) From the very beginning there is MAKE , #5d3b then there is a memory dump, which will be obtained if you fill in the line 10 randomize usr 0 and after it, I write the actual loader on ASMA. Well, basically like this: make loader,#5d3b defb 0,#a,#a,0,#f9,#c9,#30,#e,0,0,#49,#5d,0,#d ;at address #5d49 you get the bootloader ; #5d49 ........................... ........................... ret And after assembly you get a file on disk whose extension you change to "B", and instead of the starting address you put length of the received code. Well, after it you place everything you were going to load ;-) With best wishes, Dmitry.

Hello, hello Oleg! One day, in the cold summer, something around (14-11-98/01:59:00) Oleg Grigoriev once wrote to All... OG> 1. We get out of the Mazda storm and load the steering wheel. 2. We get out of the tasma and load the storm again ;) 3. Type a program like this: - 8< - cut here - 8< ------------------------- START EQU #6000;Code download address AUTORUN EQU 0; Autorun 0/1 ORG #6000 M0 DW #0100,M2-M1+21 DB "@FD300E0000FF5F003AF9" DB "@C0300E0000535D003AEA" M1 XOR A OUT(#FE),A LD HL,#5AFF LD (HL),A:DEC HL BIT 6,H JR NZ,$-4 LD HL,#C9F1 LD (#5CC2),HL LD HL,START LDSP,HL PUSH HL LD DE,(#5CF4) LD BC,(M4-M3)^!5 JP #3D13 M2 DB "@0D80AA",AUTORUN,0 BSIZE EQU M2-M0+1 DS 252-BSIZE M3 INCB "CODEFILE" M4 - 8< - cut here - 8< ------------------------- After compilation, save the object and use debugger set the type in the file header "B" and both lengths equal to the BSIZE value. Works for 0.49999999 minutes... evil Vitalik AKA Dark/X-Trade -+- What if your gasket can't do this? G8(c)Advertising

Hello Kirill! Once 16 Nov 98 at 02:18:52 Kirill Frolov argued with Oleg Grigoriev on topic B catching up with all sorts of loaders... and I decided to answer about this KF> Probably. Only everything is done easier than yours. Less manual work Finally, at least one of them figured it out...I'm doing this in STS. KF> at least. What other kind of autostart did they ask about? :-/ Yes, all this crap still doesn’t know that in the TR-Dos format the line number autorun is specified not in the file header, but in the BASIC itself in the form: 10 REM: All your lame stuff here 20 .....Similarly...... 30....etc..... Next, after the code #0D, which ends the last line, you need to put the following garbage: #80,#AA, and after that another 2 bytes, which are a string autostart...But that's not all! In the header of the BASIC file itself, after the extension “B” there should be 2 bytes, which mean the offset relative to the beginning of the BASIC of our 2 bytes #80 #AA... I advise you to do this in STS or Disk Doctor... By the way, I laughed for a long time when some lamers advised first the line after Fill in REM with spaces, and then insert code in their place If there are any requests, I can also explain the format for storing numbers in BASIC... (actuSH). Always yours, LEO/SG.

Hi Leonid! 16-11-98 at 02:37:23 Leonid Mishankov ═> Oleg Grigoriev: OG>> LD DE,(#5CF4) OG>> LD BC,#??05 OG>> JP #3D13 LM> All this is Mazda, it’s time to understand the beauty of a turboloader long ago... Why should I... I don’t know shit about trdos... Judging by your letter, you understand this much better than me. Nya, so maybe you can answer a few questions for me, the lamer? I, You could say I can’t sleep at night - they torment me terribly. 1. How can you get all the bits of the status register? nia? 2. Is it possible, and if so, how to get the contents of the register paths? 3. Similarly with the sector register. 4. Which bit of the control register is responsible for the density write to disk? 5. What is the 3rd bit of the control register used for? 6. Why is the VG unavailable for some time after the reset, and perhaps Is it possible to reduce this time? 7. How many ways to stop a disk drive do you know? Enough for a start. Best wishes, Oleg aka Ruiner. 2LD: 1. Just on topic... :) 2. Okay, okay... What if he does tell something... be smart... Look, it will come in handy. When you show someone an infinite number of entities that make up your knowledge, be prepared for the fact that

Hello Leonid! 17 Nov 98 at 01:10:53, Leonid Mishankov ===> Dmitry Sharikov: DS>> Depending on which turboloader, if it doesn’t support the screw, then DS>> this DS>> is not rulez DS>> ;-( LM> I will load software from the flop faster than from any screw in the mode LM> trdos emulation... I wonder why rst 8 then? I use it and am quite pleased. What about faster... nu-nu... If the program is on the screw, then you need it: 1. Copy to a floppy disk. 2. Run from a floppy disk. 3. Enjoy the loading speed through the pipe breaker. Item 1 will take three times longer than item 3. Therefore, points 1 and 3 are necessary cancel, and perform step 2 on the screw. The gain in speed is 4 times. ;) In general, the disk drive in my computer is like a decoration - I use it once a week. And in the end I use a driver that gives 280 kb/s. You'll have to unscrew the drive for now Yes, if you position it, I’ll have time to read 200 kilos from the screw. LM> SMUC by Scorpion - mustdie forever! Mockery LM> users... Young man, don't argue about the taste of lobster with those who have eaten it. Not a single Scorpionist has yet abandoned the screw in favor of a disk drive, arguing this in line with what was stated above.Firstly, there is no "disk error" on the screw. I already forgot when I the last time anything was killed. Secondly, professional education and SMUC are not a single whole. Therefore, the hunchback of one does not affect the other. SMUC is a very good piece of hardware. No worse than others. But the professional education needs to be torn away from her and hidden away. Or rewrite what would be more correct. And then there will be an unclouded rulez. WBR, Jason.

Hello Leonid! 16 Nov 98 at 02:37:23, Leonid Mishankov ===> Oleg Grigoriev: LM> All this is crazy, it’s time to understand the beauty long ago LM> turboloader... Mlyn, how much can you explain: _TURBOLOADER_ _MUST_ _LOAD_ _IN_ _ROM_!!! It should be written once and for everyone! And be called through ldc,5 call #3d13 Is it unrealistic to create such firmware? In zx.spectrum last year they threw such hellish firmware, they say very It worked quickly, it's a pity I don't remember the version number. The turbo loader provides immediate benefits - increased disk processing speed some specific program. But there is one very insidious and terrible _EVIL_ in it, thanks to which we are all we are sitting with the poor firmware of the 1986 model, and we are afraid to change/fix it at least one byte, because there is a craze for pipe-breakers and low qualifications coders will immediately be faced with glitches, incompatibility and all other delights. To access the disk you must use DOS tools! And if the access speed is unsatisfactory, then DOS needs to be changed! But not take over its functions! Am I doing something wrong? Get a programming textbook and read a few pages on topical topics. You will be surprised, but it says about the same thing: I said above.Then look at the names of venerable professors on the cover, and prove to me that you more experienced and smarter than them. WBR, Jason.

Let your enemies, Dmitry, die without sons! 11/19/98 at 02:29:01 Dmitry Sharikov ═> Dmitry Lomov: DS>>> and if via rst8, then the screw is faster DL>> but recording seems to be slower anyway :-) DS> I don’t know about writing, but reading is definitely faster. Children, learn fucking history!!! =) In July I made for Mas... === cut === So... Reading 640 kilos from a floppy disk using a turbo loader ra takes 32 seconds regardless of the address it goes to reading. Screw. I read 640 kilos through #3d13 in 3 different ways - mi: 1. Reading in pieces of 16 kilos per jar starting from #c000. 2. Reading 16 kilo chunks into memory starting from #8000. 3. Reading in pieces of 32 kilograms into memory starting from #8000. The reading procedure is given in listing1. Naturally everyone times the register values were adjusted. Result: 1. Operating time: 33.5 s. Reading speed: 19.1 kb/s. 2. Operating time: 24.0 s. Reading speed: 26.6 kb/s. 3. Operating time: 28.7 s. Reading speed: 22.2 kb/s. Frightened by the results I received, I decided to check that will be when using rst8. listing2. 1. Operating time: 16.0 s. Reading speed: 40.0 kb/s. 2. Operating time: 7.0 s. Reading speed: 91.4 kb/s. 3. Operating time: 11.5 s. Reading speed: 55.6 kb/s. [crunch]But recording slows down significantly... Moreover, regardless of the address sa. 1:33:5 with #3d13 and 23:8 via rst8... I'm crazy... === cut === As they say, the result is in your face. Best wishes, Oleg aka Ruiner.

Hello to you, Kirill!!! One day on November 19, 98 at exactly 01:18:00 Kirill Frolov wrote to Dmitry Sharikov on the topic 'To catch up with all sorts of loaders...': DS>> And right now xl-design has a bug, really. turboloader... KF> And now again, in Russian. What to eat, where to go KF> is inserted and what does it do? And what language did I actually say? In general, this is (in Russian): There is a certain Permanent Storage Device (abbreviated ROM) ;-) This ROM has been modified by XL=DESIGN, replacing the old #3d13 a new one is inserted, i.e. the same turboloader, cat. and previously mentioned, cleaning memory occurs using the stack, i.e. faster. etc. And it is inserted where regular ROMs are inserted. Is that better? ;-))) With best wishes, Dmitry.

├┤i, Igor! 18-11-98 15:54:00 Igor Krauklis ==> Kirill Frolov To catch up with all sorts of loaders... IK> I once asked about autorun... IK> nothing sensible, of course, no one said...:-( In #0f sector #00 of the road, be sure to install a tr-wheel drive The first 2 letters AM are imported, and then push your code. And don't ask where it is loaded, how to determine where it has loaded and why doesn’t #3d13 work after that. W!7h Be$7 W!5he$, FK0.

Let your enemies, Dmitry, die without sons! 22-11-98 at 01:22:01 Dmitry Sharikov ═> Valerij Kozhevni- koff: VK>> In general, I have a disk drive in my computer as a decoration - I use it VK>> once a week. DS> But how to transfer files to IS-DOS? Does not read directly from a screw drive DS> however... :-( He's been reading since the beginning of November. One of these days I’ll finish it and post it. The whole tor- It's tricky to work with the drive - a very flexible driver is needed... VK>> And in isdos I use a driver that gives 280 kb/s. You DS> kbyte or kbit? ;-) Baud VK>> Firstly, there is no "disk error" on the screw. I already forgot VK>> when was the last time something was killed for me. DS> As a rule, something is killed only through one’s own negligence... Either because of software glitches, or because of car glitches, or... Best wishes, Oleg aka Ruiner.

Hello Leonid! 23 Nov 98 at 05:16:13, Leonid Mishankov => Valerij Kozhevnikoff: VK>> Or do you mean that the turboloader should work on VK>> screw? That is VK>> emulate not at the level of entry points, but at the port level VK>> VG? LM> Why not?! From all the software that is written at the level LM> ports VG, no one is going to refuse... The screw is a fundamentally different device. Look: Tape recorder: bits 4 and 5 of #FE port Drive: ports #1F,#3F,#5F,#7F,#FF Screw: 11 ports #xxBE or #xxAF I'll try to follow your logic. According to you: "all tape loaders should be emulated by the controller disk drive". Because “from all software written at the level of bits 4 and 5 No one is going to refuse the #FE port." If someone had said this 6 years ago, when disk drives were just appearing, he would not have been understood. ;) Most branded games don't use push-button tape loaders. VK>> Well, you know. I once dealt with this - hemorrhoids, and the price VK>> turns out VK>> solid. It's easier and cheaper to remake the program. LM> I haven’t thought about how this will be implemented yet... But IMHO, it’s possible.If you don't know, don't talk. And I was thinking. Can. But it will cost so much that no one will want to pay. LM> And if a person cannot remake it himself, huh? Buy them from LM>software distributors? Download from friends/acquaintances. Or should I lather, I’ll yuknu, if in this person’s city no one knows how to use shadow/STS. LM> Imagine the situation: some team releases a game in LM> variant for flop and only for scorpion, so what? I do this to Damn it, the procedure for detecting the screw and setting up the driver takes ~ 100 bytes, oh what "options" are you talking about? Nobody releases games in different versions, separately for different joysticks? Or for the keyboard, or only for Kempston joystick? LM> to the fact that all magazines and games, as a rule, have protection and LM> your format... Here the issue of copyright protection is already touched upon. In commercial programs/magazines, direct work with VG is not used so much for its own sake, as much as for copy protection. Just imagine the situation: what kind of cool hacker will release an old toy 198x year of manufacture, with a ridiculous size of 100 sectors, but the spreading pipeloader only from drive A. It's insanity and nonsense, but it happens all the time.VK>> And do you know what the speed of such a propeller will be? Not really VK>> large. When VK>> with a competent approach, it could be done through #3d13 VK>> faster. LM> A competent approach is possible only through #3d2f A competent approach to what? To address the screw? You're wrong. A smart approach is to replace what is called by #3d13. My dos ports are opening, so #3d2f is sent to the garden. VK>> Reading a byte takes at least 112 clock cycles on the drive VK>> and always 20 VK>> cycles on the screw. Is there a difference? LM> Well there is... That's why you're wrong. See my letter to LD. VK>> About all sorts of cross-sector brakes and delays for promotion VK>> i VK>> I’m not saying - yet VK>> the drive is spinning up, I manage to read 100kb from the screw. LM> What's the difference? Now even on the flop it takes longer LM> for depacking. For compressors like HRUST, the unpacking speed is about 70 kb per second. And anyway, did you see this? You probably also have a screw? And I see all this every day, it loads instantly.VK>> Mlyn, what does Scorpio have to do with it??????? LM> Despite the fact that this is his product, it's a freak... Do you know the address of at least one port of at least one device on this product? Let me make an analogy: program │ device ────────────┼────────────── trdos │ VG93, analogue of WD-1793 shadow │ SMUC Tr-dos was developed by Technology Research. But you're probably infuriated by the policies of Western Digital, which developed VG93? VK>> They just made a piece of hardware!!!! And _very_ good VK>> piece of hardware, you can VK>> believe me! And Larchenko wrote software for it! LM> Perhaps... But for myself, I decided that buying smuc is not What's possible? That the piece of hardware is good? It turns out that you are calling the piece of hardware a freak, without knowing anything about it and even do you admit that she is good? LM> justifies the cost of it. VK>> ps by the way, for Nema even #3d13 on the screw does not work - screw VK>> just like naked VK>> piece of iron. LM> So what! But I will be very happy to assemble it _myself_ LM> circuit for connecting the screw, I'll spend the minimum on this And you will write the driver yourself.LM> means and I will work in IS-DOS no slower than you do LM> smuc! Break it off. Nemovsky driver even on whiteless Kai with its 175% acceleration in The turbo gives only 150 kb/s. If they give me the port addresses of the Nemov screw, then I will create my own driver for it I will create. And if they give me the Nemov driver itself, then they will even be compatible and are interchangeable. According to estimates, without cache on Kaya there will be about 270 kb/s. Or maybe more - no the limit of perfection. ps\n Look at your tireline. Do you see what's there? And how will Lara work in isdos? WBR, Jason.

Hello Leonid! 23 Nov 98 at 05:29:55, Leonid Mishankov => Valerij Kozhevnikoff: VK>> If the program is on a screw, then you need it: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ VK>> 1. Copy to a floppy disk. VK>> 2. Run from floppy disk. VK>> 3. Enjoy the download speed through the pipe loader. LM> Great! And this is not through the railway? See underlined. Such programs are usually not located on the screw. They are either stored on floppy disks or converted into a screw. If everyone sucks - then they are immediately mercilessly removed. LM>>> SMUC by Scorpion - mustdie forever! Mockery LM>>> users... VK>> Not a single scorpionist has yet given up the screw in VK>> benefit of the drive, VK>> arguing this is consistent with what was quoted above. LM> Of course! First I spent a lot of money on smuc, and then LM> refuse? Oddly enough, archives on a screw are zipped/unzipped much faster, The mail is also arriving faster, well, literally faster and faster. This is due to access time. It doesn’t matter where the sector is on the screw - on track 0 or on the 159th, the access time to them is the same, and close to zero.If you read from the screw 255 sectors scattered on different tracks, then The reading time will be the same as if they were coming one after the other. The drive will spend a lot of time fidgeting with its head and positioning. And as for the “heap of money” - smuc with a medium-sized screw costs about the same as a heap floppy disks of similar capacity. Alas, it is recognized all over the world that the disk space on a screw is much cheaper than a disk drive. LM> Besides, we are not talking about the screw, bro, but about the controller and LM> poor software for it. What is the controller's fault??? You’re not shouting that VG is Mazda, only because trdos works slowly with it? As for the wretchedness of the software - in trdos it is treated by using rst 8, and in isdos - climbing directly. VK>> Firstly, there is no "disk error" on the screw. I already forgot VK>> when I have VK>> last time something was killed. LM> Look above... I'm all for the screw, but not for smuc! Oh... let me explain what SMUC is. You just don't know it. I give an _approximate_ correspondence, based on the characteristics that are as similar as possible, but devices known to you, so that you can get an idea of functionality of this board. 1. Screw controller by Nemo. 2. Clock according to the zxnews scheme3. ISA slot with an interrupt controller (in fact, it is not much different from modem slot according to Kondratieff). The clock interrupt is set to IRQ0 of the interrupt controller. 4. 2 kB NVRAM chip, for storing all kinds of settings. The differences are minimal - only in port addresses. All this is simply collected together on one board. By the way, after this: LD A,#04 LD BC,#1FFD OUT(C),A all ports of these devices are directly accessible. WHERE did you see Mazda Forever? WBR, Jason.

Hello, Dmitry! 22 Nov 98 at 01:21:00, Dmitry Lomov => Valerij Kozhevnikoff: VK>> not at the level of entry points, but at the level of VG ports? VK>> Well, you know. I once dealt with this - hemorrhoids, eh VK>> price VK>> turns out to be solid. VK>> It’s easier and cheaper to remake the program. DL> yes. one, two... but the sea? VK>> And do you know what the speed of such a propeller will be? Not really VK>> large. DL> is wrong, IMHO. do you mean hardware emulation? what is she DL> will be slower? Yes. If the data byte from the screw can only be obtained through IN A, (#7F), then the speed of such a screw will be equal to the speed of the pipe breaker, minus the delay by promotion, positioning and waiting for DRQ plus the operating time of the emulator. VK>> approach, through #3d13 it would be possible to do it faster. DL> possible. In short: there are three approaches to emulating trdos on a screw. 1. Full interception #3d13. That is, at this same (or another) address there is transition to a certain procedure that will find out the status of the current drive, and either will return control to trdos, or completely replace it, i.e. will do everythingit should be, but on a screw. 2. Port emulation. Those. there is a spider hanging on the bus parallel to the processor, which filters the command flow and analyzes calls to VG ports. And if current drive on the screw, then this spider must block the VG and execute it functions. Those. slip into ports #1f,#3f,#5f,#7f,#ff respectively. meanings as if everything would be on the disk drive. 3. Emulation of basic low-level subroutines. - drive switching - sector reading - sector record That is in the trdos ROM in three places there are transitions to procedures that either immediately return control to trdos, or climb to the shadow with the command "connect image", "read sector" or "write sector". This is exactly how it is done in Scorpio. And that’s what causes the brakes in the scorpion. As you know, the sector size on the screw is 512 byte. This program will read 512 bytes, i.e. two short sectors or one long: ld de,(#5cf4) ldc,5 rst 8 defb #81 ldc,5 rst 8 defb #81 ld (#5cf4),de How does shadow work here: First appeal: - read a (long) sector into the buffer - rerolled half Second appeal: - read the _same_ sector into the _same_ _buffer - got over the other half. Thus, after #3d13 everything is read from the screw _twice_. For each a kilobyte read takes two to pass through the IDE bus. If you write two (short) sectors in the same way, then it’s even worse. First appeal:- read a (long) sector into the buffer - transferred 256 bytes to the first half - wrote the sector back Second appeal: - read the _same_ sector _same_ into the buffer - transferred 256 bytes to the other half - I wrote it back. For every kilobyte written, two kilobytes pass through the IDE bus into one side and then they go the other way. It's a pity I'm not Larchenko. For me, #3d13 would work a little slower than rst 8 in isdos. You just have to not re-read everything twice. VK>> ps by the way, for Nema even #3d13 on the screw does not work - screw VK>> just like bare metal. DL> Nema does not have a programmer of the level of Larchenko to DL> completely DL> plow everything. You can take Scorpov's trdos and instead of RST 8 climb to the isdos driver. See clause 3. WBR, Jason.

Let your enemies, Igor, die without sons! 26-11-98 at 00:22:00 Igor Krauklis ═> Oleg Grigoriev: IK> What about the ramdisk? Ramdisk at all? or in isdos in particular? these are two big ones difference. In general, it is 10 times faster than a turboloader. About this in the summer wrote (canonize). IK> what is its practical speed? theoretical? Theoretical - 17 clock cycles per byte. Maybe a couple more bars squeeze, but not necessary. 3500000/17 = 205882 bytes per second. But the practical one depends on the clockability, waits, etc... And considering that copiers most of the time spend on shipping from/to cans, plus the brakes of the isdos itself, that turns out to be about 50 kilos per second on a turbocharged car (mine, with my old alter). The previous paragraph also applies to screws with disk drives. These are the pies with kittens. Best wishes, Oleg aka Ruiner.

Hi, Dmitry & Igor! Once upon a time, a long time ago Igor Krauklis wrote to Kirill Frolov on the topic 'To catch up with all sorts of loaders...' IK>> I once asked about autorun... IK>> nothing sensible, of course, no one said...:-( DS> Autorun what? Loaded BASIC ? If you mean autorun of your program after submission to any command, then I’ll explain how to do it: 1). Format 0 track next. format: track head sector size 0 0 1 x - sector length from 128 to 256 bytes 0 0 2 x (for trdos disks) 0 0 3 x 0 0 4 x 0 0 5 x 0 0 6 x 0 0 7 x 0 0 8 x 0 0 9 2 - sector length 512 bytes (1024 possible) 0 0 10 x but not less than :-7 0 0 11 x 0 0 12 x 0 0 13 x 0 0 14 x 0 0 15 x 0 0 16 x 2). We manufacture the sector: Sector 9 is formed as follows: Program for STORM 1.XX REAL EQU 23845 ; where is the sector loaded with commands from trdos? SECTOR EQU #6000 ; where do we place the sector? ORG REAL,SECTOR ; we place the sector at #6000, and it will work at 23845 DEFS #200 ; clear 512 bytes ORG REAL,SECTOR MAINPRG D.I. LOOP LD A,R AND 7 OUT(#FE),A JR LOOPORG SECTOR+258 DEFW MAINPRG ; at offset 258 the program launch address is pushed into the sector ; in this case it points to 23845 3). Assembling... Pass 0.... Pass 1... Found errors: Unclear program Object len 512 (K)b Ok. 4). We go to debugger and do save to track #00 sector #08 from #6000 len #01 5). QUIT to TR-DOS 6). CAT 7). VARIOUS EFFECTS ON THE CURB!!!! cool!!! That's it, it seems, that's all... If it doesn’t work, write me, I typed everything in from memory and it might work don't make money... With best wishes, Vladimir Galtscev.

Hello, Dmitry! 28 Nov 98 at 02:27:00, Dmitry Lomov => Valerij Kozhevnikoff: VK>> Yes. If a byte of data can only be obtained from the screw VK>> via IN A,(#7F), DL> who said? I have a solution - “both yours and ours.” DL> share DL> I won't :) You've already let it slip for a long time. ;) You will replace the ROM. By the way, this is how the screw is connected in RST 7. Emulation is complete. VK>> In short: there are three approaches to emulating trdos on VK>> screw. VK>> 1. Complete interception #3d13. That is, by this very thing (or VK>> to another) address is worth going to VK>> to a certain procedure that will find out the status of the current DL> software interception with ROM correction. What Zonov has. This is not quite the case with Zonov. VK>> 3. Emulation of basic low-level subroutines. VK>> - drive switching VK>> - reading sector VK>> - sector record VK>> That is. in trdos ROM there are transitions to in three places VK>> procedures that either immediatelyDL> IMHO, Zonov has the same as in case 1 + the same as in case 3. DL> i.e. complete stuffing in ROM. No. Case 3 in its purest form. The truth is intercepted there not at three points, but a little more. A couple more functions are used. Interception is not done at the level of the interpreter of the contents of the C register, but lower. I've seen many loaders without #3D13 at all, but still on the screw they worked. I once uploaded a disassembler of a piece of scorpion trdos here, everything is clear there it was. VK>> You can take the Scorpov trdos and instead of RST 8 climb to VK>> to the perfect driver. See VK>> point 3. DL> i.e. in some places violate the Larchenkovsky/Zonovsky copyright. Where is their copyright? Should I put the firmware here? ;) I only saw Technology there Research Ltd ;) Larchenko probably didn’t ask permission. WBR, Jason.

Hi Denis! DD>>> But what if, for example, there is a magazine whose disk format contains DD>>> different lengths of sectors, cross-sector delights, etc.? DL>> this was not mentioned. talked about the standard format and DL>> non-standard loaders. DD> Well, this is done relatively simply (in software), and therefore not very well DD> interesting ;) hmm. I wouldn't say that... this means that all points where the loader can go must be replace it in ROM? there are curves and actually used entry points, and everything is needed support. IMHO - it’s impossible to do it right, even after plowing ROM completely. We need hardware implementation of VG replacement. I can offhand name 10 trdos points that I use. and then I take Format, read Max Petrov’s article, and see that he uses completely different points. then I pick at something and see What else is there? DD>>> ps: I have a thought about this, but a perverted one... DL>> share :) I had a lot of thoughts at one time, yes DL>> everything was forgotten. I realized that if I do something, DL>> then without emulation of curved formats. DD> Well, in any case, the disk image carrier file on the screw will not be in .trd DD> format; uh huh. DD> for a simple case with different sector lengths, it is enough to have a small DD> field describing each individual sector on the track (exactly those four bytes DD> and CRC), and then everything is quite simple (if there is where to store this DD> descriptor while working with the track). The only bad thing is that the image structure DD> of the disk will be non-linear, but this can also be solved if at the beginning of the image DD> describe where each track begins (again, preferably this descriptor DD> keep constantly in memory, which may not exist). IMHO, you need a broken image of the track. or, if not so, then reserve obviously more for each track; nothing screw regret. but if the program decides to write in this non-standard format will be worse... DD> So, I agree with you about the perverted track formats - more DD> fuss, what's the point. so we decided :) to take him to the bath... All the best. Dmitry. ..LD..X-TRADE..

Hello, Oleg! 07 Dec 98 at 04:18:17, Oleg Grigoriev => Valerij Kozhevnikoff: EP>>>> Why now support 40 tracks or EP>>>> single-sided drives ? OG>>> Not sure about the need. I'll probably remove it. Byte at 30 OG>>> will be reduced. :) VK>> Leave it. Does it interfere with anything? OG> Size. I threw it out - it became 22 (not 30) bytes shorter. :) oh, so many ;) OG> If you return it, and the drives are like that, then the byte will increase by a hundred... OG> Ka-achma-ar!!! :) OG> Okay, let's see. A compromise option is two versions. One will say “yes, of course,” and the other shouting “no, fuck it!” And everyone will be able to choose the right one for themselves. ps by the way, about the sizes. Here in zx.spectrum they threw a spreading peeper of ZX pictures under MD'95. With scaling, changing palettes, smoothing the squareness of points, and with built-in converter to .bmp. An unpacked .exe weighing 11 kilos. And do you know why it’s unpacked? As its author (Oldman) said: "the size of the unpacker exceeds the size the program itself." 8-[ ] And in our hrum 3.5i the depacker size is #77 bytes. I'm crazy. WBR, Jason.

Hi, Igor! IK>>> How to find out how many bars a green scorpion has in a line? DL>> 224, and there is nothing to learn. IK> That is, if I understand correctly, with the arrival of int it begins IK> build the screen line by line? we need to think differently. the raster is always built. it starts from (conditionally) zero lines, then first, second... and 311 (for scorpion). During the time the beam is on the line, the processor works 224 cycles (on green scorpion/pentagon). and all that remains is add that the visible part of the lines (out of 312) are (conditionally) from number 30 to number 280, screen (192 lines) corresponds to lines 80...271, and int appears (conditionally) on the 40th cycle of the Z80 from the beginning of line number 16.. a little confusing, I guess. and the degree of conditionality is unclear... But can we take the line number zero as the line where the int... in short, create, invent, try :) there’s a cool one for that the language is called assembler ;-) IK> If my memory serves me correctly, then IK> are there 320 lines in total? it's at the Pentagon. in scorpion - 312. VG>>>> LD L,3 VG>>>> LD H,4 VG>>>> LD E,5 VG>>>> LD D,6 IK>>> I don’t understand why we need LD l,3 ... ld e,5 ?? IK>>> to kill time? Or should the colors be different? DL>> the registers are filled with colors and then spat on the screen. IK> HERE IT IS!!! this? what's below? IK> Interesting glitch: IK> one person made an inscription on the border on a yellow scorpion - that's all IK> ok, oh (even the music is playing, but everything is stable) IK> And on my green turbo+ it SHAKES!!! (for one familiar place), but IK> not always. And after turning the turbo on/off. IK> Let's say I'm launching a program (everything is stable, if without music), IK> then I turn on the turbo, turn it off and STARTS TO JERKLE TO ONE IK> SIGN PLACE. IK> Then I activate the hardware pause several times (ground at 24 IK> leg z80), and the image is STABILIZED!!! I know the nature of this, but I won’t explain it - it’s complicated... if very if necessary - tell me, there will be a night sermon :) and ask if the guy has an 1858VM3 in place of the Z80? Best wishes. Dmitry. ..LD..X-TRADE..