asm

Hello, Dmitry! 30-03-98 at 03:56 Dmitry Lomov wrote to Kirill Frolov on topic "PH_SMV". KF>> STORM has very terrible disadvantages - 42 characters per line KF>> (where should I write comments here?) and 7-character tags. DL> what a nightmare! Don’t let your eyes get any extra strain! :) Ideal asm in my understanding: 1. Storm speed. 2. Tasma interface4. 3. Flexibility/configurability of alasma. 4. Working with a screw via rst 8, with a disk via VG. 5. A full-fledged editor, not inferior to is-edit. 6. Output to 7 screen. 7. All 48 memories are at the disposal of the encoder. Those. opportunity writing programs running from address #4000 to the end of memory. (As copper writes in PC). 8. Loading data during assembly to a given address and to a specific page. For example: INCBIN [dr:][filename][ext] [addr][,bank] 9. Specific setting of the program start address, and not according to the sequence Ice ORG. For example, ENT $, or ENT #8765. 10. Tags up to 10 characters. In principle, 7 is almost always enough, but sometimes you still need it. If I remember anything else, I’ll write. DL> try to accept our rules. rape yourself for a week. How evil you are ;))) Best wishes Oleg aka Ruiner. -+- Shoot-Edit v6.06

Hi, Oleg! OG> Ideal asm in my understanding: OG> 1. Storm speed. :) OG> 2. Tasma4 interface. how's that? to run the file, you need to exit somewhere, while position in the text is lost? (I think so. I liked this about Tasma most of all) ;) it's not the interface, it's the lack of it... in STORME, however, too... but there is more absence there! :) OG> 3. Flexibility/configurability of alasma. yes. I want it myself. OG> 4. Working with a screw via rst 8, with a disk via VG. but comment. OG> 5. A full-fledged editor, not inferior to is-edit. yeah. do the brakes too? :) OG> 6. Output to screen 7. why? what difference does it make to you? You can compile in #4000, but this is not This means that memory cannot be swapped while the ASM is running. OG> 7. All 48 memory is at the disposal of the encoder. Those. opportunity OG> writing programs that work from address #4000 to the end of memory. yeah. Want. OG> 8. Loading data during assembly at a given address OG> and to a specific page. For example: OG> INCBIN [dr:][filename][ext] [addr][,bank]wanted... until it turned out that there was nowhere to load - no freedom. pages OG> 9. Specific setting of the program start address, and not by pos- OG> ice ORG. For example, ENT $, or ENT #8765. no, according to the first Org. if you need to do otherwise, first write: org #8000 org #6000 program org #8000 program at the same time, the first org is an analogue of your EHT. OG> 10. Labels up to 10 characters. In principle, 7 is almost always enough OG> but sometimes you still need it. well, well... OG> If I remember anything else, I’ll write. write. STORM 2.0 is just around the corner... let's get busy in the summer... DL>> try to accept our rules. rape yourself for a week. OG> How evil you are;))) Yes, I am like that :) All the best. Dmitry aka -=LD=- / X-TRADE GROUP. -+- SMM version 1.08

Hi, Oleg! DL>> you launch alasm... and it becomes tosho immediately after loading... DL>> The text _MUST NOT_ disappear from the screen. OG> What do you mean? does not disappear in the 4th tasma. Eh, there is no ideal as- OG> ma... hmm. will. starting yesterday I sat down tightly at ASM. you will scold... but more gently :) will be twice as fast (from memory). full configurability. unlimited text length. Incident files up to can length. up to 16 characters per label - all significant. HDD support. import/export are the same; IMPORT from 1.0 will be added. 22 lines of 40 characters each (exactly 40 on the screen. But I’ll put more in the format. probably). the text will take up less space, by 5 percent. there will be a selection of files from the directory. the number of tags is probably up to 4096. (and 32k in memory) local labels, macros, conditional translation. a bunch of new things in the editor (if you’re lazy, then a small bunch). a bunch of new teams. the list is attached :) 1) post/pre_inc/decremental addressing. those. LD (HL)+,DE,#00,#1234,IX = LD (HL),E:INC HL LD (HL),D:INC HL LD (HL),0:INC HL ... LD A,LX,(HL),A:INC HL LD A,HX,(HL),A:INC HLoptions (instead of HL/H/L there can be BC/B/C, DE/D/E, IX/HX/LX, IY/HY/LY) LD (HL)-,0 = LD (HL),0:DEC HL LD -(HL),0 = DEC HL:LD (HL),0 LD +(HL),0 = INC HL:LD (HL),0 LD (L)+,0 = LD (HL),0:INC L LD (H)+,0 = LD (HL),0:INC H and stuff like that. 2) Directives LAB EQU VALUE ;Constant LAB = VALUE ;Variable example: TEST = $+666 REPT 100*2-3 DW TEST TEST = TEST+8-$ ENDR 3) macro example #TRASH LD A,=1] LD H,=1[ JR =2,.TRASH=3 N.E.G. .TRASH1 INC =4 IFD =5 DB "GGG",=5,=0 EIF .TRASH2 ENDM =1 ... =X PARAMETERS =0 USAGE COUNTER .LABEL - LABEL INSIDE A MACRO/REPT USE #TRASH #3D13,NZ,1,B,"U" 4) local labels. TRASH0 ADD HL,DE ; global .ABC ADD HL,DE ; local DJNZ.ABC THRASH1; global, local ones are reset .ABC0 LD B,C .ABC DEC DE DJNZ.ABC DJNZ C,.ABC0 THRASH2 ; global, local ones are reset 5) conditional translation as in Zasma. 6) all sorts of pseudo-commands. DJNZ C,M0 = DEC C:JR NZ,M0 DJNZ DE,M0 = DEC DE:LD A,D:OR E:JR NZ,M0 LD DE,B = LD D,0:LD E,B LD (DE),BC = LD A,C:LD (DE),A:INC DE LD A,B:LD (DE),A:DEC DE LD (IX),DE = LD (IX+0),E LD (IX+1),D BRD 1 = LD A,1:OUT (#FE),ABRD A = OUT (#FE),A BRD 2,BRDON = if BRDON=0 - do not compile. CJE B,#4C,LABEL = LD A,B:CP #4C JR Z,LABEL CJNE HX,D,LABEL = LD A,HX:CP D JR NZ,LABEL LD (M0),(M1) = LD A,(M0) LD (M1),A LDW (M0),(M1) = LD HL,(M0) LD (0),HL FILL #4000,#1800,#00 = TELL ME ALL SUB HL,DE = OR A:SBC HL,DE TJZ/TJNZ B,M0 = LD A,B:OR A JR Z/NZ,M0 TJZ/TJNZ BC,M0 = LD A,B:OR C JR Z/NZ,M0 LD (HL),[ADD A,A] = LD (HL),#87 DECA (M0) = LD A,(M0):DEC A:LD (M0),A DECH (M0) = LD HL,M0:DEC (HL) DECW (M0) = LD HL,(M0):DEC HL:LD (M0),HL ADDD HL,2345 = LD DE,2345:ADD HL,DE ADDB HL,2345 = LD BC,2345:ADD HL,BC ADDI HL,#1020 = LD A,L:ADD A,#20:LD L,A ADC A,#10:SUB L:LD H,A ADDI ADCI UP SBCI DOG ANDI ORI ADDI L,#20 LD A,L:ADD A,#20:LD L,A NEG B = XOR A:SUB B:LD B,A IN A,(#FDFE) = LD A,#FD:IN A,(#FE) IN C,(#FDFE) = LD BC,#7FFD:IN C,(C) that's from what I managed to remember... There will be a bunch more on the go. Suggest your own. All good. Dmitry aka -=LD=- / X-TRADE GROUP. -+- SMM version 1.08

Hello, Dmitry! 06-04-98 at 00:27 Dmitry Lomov wrote to Oleg Grigoriev on theme "asm". OG>>>> 4. Working with a screw via rst 8, with a disk via VG. DL>>> but comment. OG>> What? I gave you all the information, nothing particularly complicated there DL> be it unto you, be it... Teeeeeeeeeeeaaaaaaaaaarrssss :EEEE Now if only there were 64 characters per line... oh...;) OG>> Otherwise I end up with something very creepy: a size chart OG>> 520 bytes, and code 175 (or 275). 13 keyboard modes. DL> no, much less... and not 13 modes there... Well, I have 13. Maybe there will be a 14th. 01. lat mode. 02. lat mode with caps shift. 03. lat mode in capital mode. 04. lat mode in capital mode with caps shift. 05. lat mode with symbol shift. 06. rus mode. 07. rus mode with caps shift. 08. rus mode in capital mode. 09. rus mode in capital mode with caps shift. 10. rus mode with symbol shift. 11. rus mode with caps & symbol shift. 12. grf mode. 13. grf mode with caps shift. In Russian it was to break;) Perhaps there will be a 3rd graphics mode - with symbol shift. For entering pseudographics with codes 0-31. But most likely - no. Each plate is 40 bytes. And the differences are quite significant. veins DL> I just don’t remember if I used ROM tables. I don't think so ;)) DL> if you really need it, I can upload it... It won't be redundant. I can return the courtesy - dare - eat.;) Best wishes Oleg aka Ruiner. -+- Shoot-Edit v6.06

Hello, Dmitry! 05-04-98 at 01:01 Dmitry Lomov => Oleg Grigoriev: DL> hmm. there will be. "And that's right." DL> starting yesterday I sat down hard at asm. you will scold... but more gently :) No, I’ll scold you when you finish it ;)))) DL> will be twice as fast (from memory). Do you mean assembly? Request: when will you write about ASMA speed, write how many lines per second it gives, otherwise I'm already sick of it: "My assembler assembles x.x times faster this, z.z times faster than this... "Similarly with tokenization. DL> full configurability. Will it be possible to integrate external drivers into the ASMA body? Or maybe they'll make some kind of Suicide-98 with memory through the port Kempston joystick... I. For example, memory driver: + 0; displacement of the integrated piece relative to the beginning of the drive faith. + 2; the length of this piece + 4; driver initialization procedure. You will need: 1. initialize the driver (for example, it will create a table cans, clicking pages [we are in the setup, the driver is below!] will do as it was and tell you how many pages are available...). 2. load the required part of ASMA, or not load... 3. throw the working piece into the body of the asma. 4. rewrite the asm on the disk. Or some other way... II.About the loaded screw driver. Why not? if it will fit into 1 kilobyte... 512 byte buffer. + 0; checking for a screw + 3; Is the current drive a screw partition? + 6; read/write. see above. III. Klava. Loadable signs or setup a'la MMD. IV. Display driver. It wouldn't be bad, but oh well. DL> unlimited text length. DL> int files up to a jar long. That is only main text unmeasured? Then there is no special meaning, since main text almost always contains initial settings and a bunch of inclusions. At least that's how it is for me. DL> up to 16 characters per label - all significant. Decided to sacrifice one bit? ;))) That's it. Now I will only make the following marks: MY_DYING_BRIDE MY_DYING_BRIDE00 ;-) 2Van: or NAPALM_DEATH ;)) DL> HDD support. DL> import/export are the same; Did you find a glitch? I wrote that my ASM was buggy during the transfer from the text in ACM, on the PROC file - half of the text simply disappeared hall By the way, you never expressed your opinion - strange...;))) How do you like Tasm4? ;))) DL> IMPORT from 1.0 will be added. Is it necessary? :- Few people saw him. DL> 22 lines of 40 characters each. (On the screen there are exactly 40. And I’ll put more in the format. DL> probably). It's funny. Those. maybe there are more operators than you can see? ;)) What prevents you from doing it like in is'edit/tasm? DL> the text will take up less space, by 5 percent. DL> will select files from the directory. DL> number of tags, probably up to 4096. (and 32k in memory) And it’s better to set this in the setup. If I have a meter of brains then what? prevents you from allocating 64 kilos to the marks? DL> local labels, macros, conditional translation. I would like to see more information after the broadcast. I I still don’t understand how to find out the remaining memory size for the met- ki... Write until there is a knock on the head out of memory - no? ;)) Although... I just can’t understand how people manage to spread make so many marks... DL> a bunch of new things in the editor (if you're lazy, then a small bunch). More indications. ;))) DL> a bunch of new commands. the list is attached :) DL> 1) post/pre_inc/decrement addressing. i.e. DL> DL> LD (HL)+,DE,#00,#1234,IX = LD (HL),E:INC HL What about the marks? those. LD (HL)+,INT = LD (HL),INT{:INC HL:LD (HL),INT} DL> options (instead of HL/H/L there can be BC/B/C, DE/D/E, IX/HX/LX, IY/HY/LY) DL> 2) Директивы DL> LAB EQU VALUE ;Константа DL> LAB = VALUE ;Переменная DL> пример: DL> TEST = $+666 DL> REPT 100*2-3 DL> DW TEST DL> TEST = TEST+8-$ DL> ENDR Как в аласме. У тебя дока на него есть? DL> 3) пример макроса DL> #TRASH LD A,=1] Лучше #DOOM ;)) DL> LD H,=1[ DL> JR =2,.TRASH=3 DL> NEG DL> .TRASH1 INC =4 DL> IFD =5 DL> DB "GGG",=5,=0 DL> EIF DL> .TRASH2 DL> ENDM DL> =1 ... =X ПАРАМЕТРЫ DL> =0 СЧЕТЧИК ИСПОЛЬЗОВАHИЯ DL> .LABEL - МЕТКА ВHУТРИ МАКРОСА/REPT'A Стало быть цифровых локальных меток нет? Ведь есть директи- ва .num DL> ИСПОЛЬЗОВАHИЕ DL> #TRASH #3D13,NZ,1,B,"U"I tried for a long time to understand what he was doing =)) But I still didn’t understand) DL> 4) local labels. DL> 5) conditional translation as in Zasma. I approve. ;)) DL> 6) all sorts of pseudo-commands. [Oh, mom!..] DL> this is from what I managed to remember... DL> there will be a bunch more along the way. DL> offer yours. I wonder if anyone will use even a tenth part of it? Although using macros makes life easier, greatly reduces the efficiency of the code, IMHO. Best wishes, Oleg aka Ruiner. -+- Shoot-Edit v6.06

Hi, Alexandr! AK> By the way, I wanted to ask: AK> What is the relationship between seconds and ticks? AK> I mean, how many seconds does one beat last? 1 tick = 1/3500000 second, i.e. 1 cycle = 285 ns, = .285*10-6 sec. 1 second = 3,500,000 ticks. for turbo cars, instead of 3,500,000, the frequency is in hertz. Best wishes. Dmitry aka -=LD=- / X-TRADE GROUP. -+- SMM version 1.08

Hi Paul! DL>> wow... like, modf. alto. encoding is an unspoken standard... DL>> so why reinvent the wheel in Xas? PF> font for 128 characters, 7 bits -> token . hmm. when was the first XAS written? It seems that it has long been a complete standard. but a bit is missing - this is not a reason for a programmer to do something bad. Best wishes. Dmitry aka -=LD=- / X-TRADE GROUP. -+- SMM version 1.08

Greetings, Dmitry! Sun 05-Apr-98 01:01, Dmitry Lomov bombed Oleg Grigoriev’s letter: DL> this is from what I managed to remember... DL> there will be a bunch more along the way. DL> offer yours. The DOOM command is still missing :) And finally, there is a perversion with the commands. By For me, it would be better to fill in macros and use them for your own pleasure. And don't sit do not adapt to the “new” set of commands. By the way, I also want to remind you about one trouble with local labels. sux ld b,#20 ld hl,#4000 .10 ld (hl),0 inc l djnz.10 A dumber example, but still. Let's remember our favorite method of self-change code. ld a,#10 ld (mustdie+1),a sux ld b,#20 ld hl,#4000 .10 mustdie ld (hl),0 inc l djnz.10 An elementary example. As you can see, the entire localization of tags is covered with mustdie. With the best wishes, John.

Hi, Oleg! DL>> starting yesterday I sat down hard at ACM. you will scold... but more gently :) DL>> will be twice as fast (from memory). OG> You mean assembly? yes. OG> Request: when will you write about OG> ASMA speed write how many lines per second it gives, otherwise OG> I'm already sick of it: "My assembler assembles x.x times faster OG> this, z.z times faster than this... "Similarly with tokenization. didn't measure. the current version of STORM is 4 times faster than your favorite one by you Tasma4. heh, heh, the coming one is at eight... DL>> full configurability. OG> For example, memory driver: OG> + 0; offset of the integrated piece relative to the beginning of the drive OG> faith. OG> + 2; the length of this piece OG> + 4; driver initialization procedure. no, not like that. 1) GMX - to the bathhouse. 2) Pro. I think it's difficult there. I didn't mess with the config :) like, do I need to jump somewhere in Dos? clarify about this. 3) other machines - memory is addressed by no more than two ports. you indicate: first port = ... (let's say #1ffd) second port = ... (let's say #7ffd)a) tag banks. to 1st port = .. 1. tag_bank_0: to the 2nd port=.. 2. tag_bank_1: to the 2nd port=.. ... .. tag_bank_N: to the 2nd port=.. b) text banks. to 1st port = .. 1. text_0: to the 2nd port =.. ... .. text_N: to the 2nd port =.. c) code banks. similarly. d) service banks. similarly. If the banks intersect somewhere, we will deal with this separately. You can somehow highlight part of the jar. It is planned, for example, to keep text and tags under the bare car in a single bank. In short, you indicate everything with pens. and then you modify the asm. OG> About the loaded screw driver. Why not? if how many screws are there? to the bathhouse. pst#8. OG> Keyboard. Loadable signs or setup a'la MMD. yeah. OG> IV. OG> Display driver. It wouldn't be bad, but oh well. slow down _it_ won't_! and the driver is like usually slow. DL>> unlimited text length. DL>> int files up to a jar long. OG> That is. only main text unmeasured? Then it doesn't have much- OG> meaning, since main text almost always contains initial ones OG> settings and a bunch of inclusions. At least that's how it is for me. well, okay. live :) DL>> up to 16 characters per label - all significant. OG> Decided to sacrifice one bit?;))) OG> That's it. Now I will only make the following marks: OG> MY_DYING_BRIDE OG> MY_DYING_BRIDE00 OG> ;-) well, well... TALES_FROM_THOUSAND_LAKES123. :) take another doom. TIAMAT - it has 6 letters :) DL>> HDD support. DL>> import/export are the same; OG> Did you find a glitch? I wrote that my ASM was buggy during the transfer OG> from the text in asm, on the PROC file - half of the text has simply disappeared OG> hall. By the way, you never expressed your opinion - strange...;))) damn. forgot... yes, how did you convert? STORM currently understands the text... or through XAS? That's definitely a glitch. but not mine... OG> How do you like Tasm4?;))) to the bathhouse. its appearance is 5 years outdated. DL>> IMPORT from 1.0 will be added. OG> Is it necessary? :- Few people have seen him. I have a lot of sources in it. DL>> 22 lines of 40 characters each. (On the screen there are exactly 40. And I’ll put more in the format. DL>> probably). OG> Funny. Those. maybe there are more operators than you can see? ;)) OG> What prevents you from doing it as in is'edit/tasm? yeah, scrolling left/right. you could also say hypertext... DL>> the text will take up less space, by 5 percent. DL>> will select files from the directory. DL>> number of tags, probably up to 4096. (and 32k in memory) OG> And it’s better to set this in the setup. If I have a meter of brains then what? OG> prevents you from allocating 64 kilos to the marks? you need 4 - there will be 4. but no more. 64 k subtags is about 8000 tags. there are 1500 of them in the STORMA source code... well, how much more? this volume of marks corresponds to 100 k of code... DL>> local labels, macros, conditional translation. OG> Although... I just can’t understand how people manage to spread out- OG> add so many tags... easy :) DL>> a bunch of new things in the editor (if you're lazy, then a small bunch). OG> More indications.;))) LEDs connected via #7FFD :) what to indicate? DL>> a bunch of new commands. the list is attached :) DL>> 1) post/pre_inc/dec_replacement addressing. i.e. DL>> DL>> LD (HL)+,DE,#00,#1234,IX = LD (HL),E:INC HL OG> What about labels? i.e. OG> LD (HL)+,INT = LD (HL),INT{:INC HL:LD (HL),INT} yeah. whatever you want. if your example is just LDW (HL),INT. if in your code you add INC HL to the right, then LDW (HL)+,INT. where can I get a document for Alasm? OG> So there are no digital local marks? After all, there are directives - OG> va .num Nope. .num - line circulation... DL>> USAGE DL>> #TRASH #3D13,NZ,1,B,"U" OG> I tried for a long time to understand what he was doing =)) But I still didn’t understand%) hehe, this is an example... DL>> 6) all sorts of pseudo-commands. OG> [Oh, mom!..] DL>> this is from what I managed to remember... DL>> there will be a bunch more along the way. DL>> offer yours. OG> I wonder if anyone will use even a tenth OG> part of this? Although using macros makes life easier, OG> greatly reduces the efficiency of the code, IMHO.I personally don’t need macros at all. I'm going to use everything else. Best wishes. Dmitry aka -=LD=- / X-TRADE GROUP. -+- SMM version 1.08

Strength and wisdom to you, oh mighty Eugeny 04/15/98 Eugeny Sobolev launched a letter to Alexandr Knyzev: [mow bite] AK>> What else can you say - Kernal was a rulez, he (a rulez) AK>> and will remain ;) ES> Sorry for the lamering. :) But what is Kernal? I remember that ES> knew the term, but forgot, since I never used it myself - ES> sya. Simply put, this is some area in memory that is not when it does not change its position in the address space. Its consequences are clear: the compatibility of something in future versions siyam, because in the kernal there are jumps: ADDR 1 JP #NNNN ADDR 2 JP #MMMM ADDR 3 JP #ыыыы The point is that if the location of a procedure in memory changes, ty, then her address is simply entered in place, say #ыыыы, and the call address of this procedure remains unchanged -ADDR 3 Kernal, this is a kind of guide to somewhere ;) [mow bite] ES> when I type comments. :( By the way, why are you apologizing? ES> we are philologists after all :) so let’s get on with it ES> as for expressions of philology. :))) Ok, after all, this is the Great and Mighty ;) By the way, can you tell me about the Pink Floyd system? Everyone says thatIt's Sax, but I don't believe it. With the same success about is-dos you can say the same about everything else. ;) Everything else has been moved to MUSIC.ZX to avoid conflict with moderator ;) Best regards, Alexander/Merlin. CMTG/Chaos Corp -+- ShiSanuty dED 6.06+

Be healthy and happy, Alexandr. [omitted] ES>> Sorry for the lamering. :) But what is Kernal? I remember that ES>> knew the term, but forgot, since I never used it myself - ES>> sya. AK> AK> Simply put, this is some area in memory that is not AK> when it does not change its position in the address space. AK> Its consequences are clear: the compatibility of something in future versions AK> siyam, because there are jumps in the kernal: AK> AK> ADDR 1 JP #NNNN AK> ADDR 2 JP #MMMM AK> ADDR 3 JP #ыыыыы AK> ...... ........ etc. AK> AK> The point is that if the location of the procedure in memory changes - AK> ty, then its address is simply entered in place, say #ыыыы, and AK> the address of the call to this procedure remains unchanged -ADDR 3 AK> Kernal, this is a kind of guide to somewhere ;) [omitted] No, I didn't know what it was. I came up with this myself at one time and I always considered it my invention. Maxim Kernal means also using called. This is called reinventing the wheel. :) ES>> when I type comments. :( By the way, why are you apologizing? ES>> we are philologists after all :) so let’s get on with it ES>> as to expressions of philology. :))) AK> AK> Ok, after all, this is the Great and Mighty ;) AK> By the way, maybe you can tell us about the Pink Floyd system. Everyone says that AK> it's a sax, but I don't believe it. With the same success and about AK> is-dos you can say the same about everything else. ;) AK> AK> Everything else has been moved to MUSIC.ZX, to avoid conflict with AK> moderator ;) I have a price list on my wall, here it is: Operating system P I N K F L O Y D Pink dream (c) DOMEN MCMXCVI 1. Multitasking. * Set of application programs for system maintenance. * Package for creating electronic publications (language of hyper-text- HTML multimedia documents). *User manual and programmer (in the form of an HTML file). 2. Object-oriented ideology. 3. Graphical interface of the SAA/CUA standard. 4. Transparent support for TR-DOS/MS-DOS (FDD/HDD/CD). 5. Expansion of TR-DOS capabilities. 6. Drag & drop server.There are no jokes here, everything is true and I stand for every point I answer. The system was way ahead of its time, just Sinclairists don't understand what multitasking is. Of course the system is crude. If I were to rewrite it now, I would have done a lot differently than Maxim did then. Then I'm in mainly engaged in the design of this very graphic ical interface. But a normally designed version from DOMEN & SCORPION & K' most have not seen, seen only the original one in the shitty DOMEN design. In PF there were initially a lot of mistakes, which later all were found/fixed, partly by Maxim, partly me. The system was criticized for the fact that if one window is open task closed the window of another open task, and then one from tasks were closed, the closed task deleted its window with these efforts (and IG> by whom or how) this is achieved is not of interest to me. When this is done, then the issue of payment must be raised. If money needed now so that in n time we receive - write now, pay - in n time receive and about what's in the future. The main thing is that it is written very clearly and concisely. I didn’t even know how to use your gate. I once wrote a letter with soap to 812/09.00 I don’t know where it went because... there was no answer, maybe the person just didn't count necessary to answer. If there are any nuances, then probably such things should lie in the formfile about how and what to use on the network in a zip at each station, well, the hub has one extreme at least exactly. ES>> should be listed in detail what and how ES>> use ES>> from SPBZXNET. Well, for example, to view HTML on ES>> Spectrum PINK FLOYD has a good VIEW'er, so ES>> means a description of all the possibilities of everything. Well let it be ES>> this letter will be the only one in the echo and will take 255 sec. ES>> :) Well, let it lie on all BBS forever, so that later ES>> no one said they didn’t know. But to make it clear two ES>> question: such and such we pay for services, such and such we receive them (services) IG> You see, what’s the matter - what and how to use on the Spectrum - for me IG> remains a mystery. Whatever one may say, I left the spectrum (maybe not IG> completely final, but nevertheless), and therefore describe with what and how IG> cannot be used on the spec for working with mail (ehi/soap/e-soap/html) IG> meaning. IMHO.There are requirements for the format of e-mail letters/fido letters, right? And they different from that format that operates in SPBZXNET. Can this be described or is it assumed that everyone was born with this knowledge? For example, in ancient times I had to use directly from fido speck, but I don’t remember a thing. IG> With all kinds of regards and wishes. IG> Igor. Good AGRESSOR. -+- Z'us t's e'us (l.)

┌┐ CM07p├0 B┴┴py┌ 26-04-98, B 09:08:35 ├┤ekT0 Viktor Kuzmin ┌┐│/│Ca/ k Alexandr Knyzev ┌┐p0 asm : ├┤i Viktor & Alexandr! [...] VK> P.S. If anyone has ALASM x.y, where x.y > 3.8, then please blur it out, and VK> then I have to finish it a little for myself (I have tags VK> occupy 1.7 banks, and I have not seen a single assembler that supports VK> more than 1). In ZXASM, the memory with tags slowly moves down until it hits text. Maximum for tags and text together is 32kb. So the pic of the tag you can allocate about 28Kb, and the rest is text including: INCLUDE "my_prog" my_prog is your program. Wi7h be57 Wi5he5, FK0. -+- SMM version 1.08

Reply-To: Alexandr_Knyzev.sp0600@zxnet.spb.ru Strength and wisdom to you, about Alexander 07/11/98 Aleksandr Majorov launched a letter to Alexandr Knyzev: *Moved this topic to the data center, otherwise KIR is probably already spitting poison ;-)))))) [ ] AK>> Already turned it on ;-) Didn't help. When you have a dozen files on your disk AK>> and they must be loaded during the compilation process (and into one file AK>> glue is lazy), that’s when the hair stands on end when working AK>> zasma with disk ;-)...and so, normal such assm, if AK>> there was a catalog cache, maybe I would have worked as a substitute...but please help me AM> a disk cache would be nice ;-( AM> although it’s not bad - well, more or less from the screw Yes, but the problem is that I personally don’t have a screw :( AM> well, from the disk: well, it’s time to have some tea AM> go while it compiles ;-)) But I won’t drink the tea ;-))))) [ ] AM>>> There is a program “from everything in zasm”, but in direct zasm you can AM>>> convert to text and back AK>> It works clumsily. I want, add. convert to text format AK>> and so that all the letters are capitalized... but no, he doesn’t want to. I even had to AK> AK>> one day write a small utility for increasing/decreasing letters, and AK>> it didn’t convert well into Tasm ;-) AM> peeps, the "everything in zasm" utility asks which ones AM> convert letters!!! If you ask, it asks, but, IMHO, it doesn’t do it ;-/ ;-) [ ] AM>>> is there no access to TR-DOS via #3D13? AK>> There is no 3d13 in ksas...or what are you talking about? AM> you wrote that XAS will restore VG after a clumsy program, AM> and calling #3D13 seems to do the same thing? But in my opinion no. Tr-dos will just hang, because the controller not restored, but ksas with his no less left pipe-loader somehow restore this opus ;-) AM> i.e. in the background after your program with a clumsy appeal to VGhe AM> do CAT or something like that - and okob Maybe it restores... but I remember that when I wrote for- shield and turboloader (one of my first), then somewhere I (not help- Nude where) I was tormented with restoring the controller ;-) [ ] AM>>> what are the sources? AK>> So it was thrown into the echo... there are subroutines there, as if to access AK>> screw and evil work with it ;-) AM> PS, is it possible to repeat them at the request of the workers? AM> It seems I missed it ;( And catch: 2Ruiner: not with your feet :-)) ;--------------------------------------- ;1.Start the program, setting variables ;--------------------------------------- D.I. LD A,(#0008) CP#C3 JR NZ,EXIT;This is not a scorpion LD BC,#1FFD LD A,#02 OUT(C),A LD A,(#00F1) ;Took the TM version number LD E,A XOR A OUT(C),A LD A,E CP 96 JR C,EXIT ;But it’s old, there’s no screw there. LD HL,DIS_BUF LD C,#09 RST #08 ;Set working buffer DB #81 ;size 512 bytes LD C,#22 RST #08 DB #81 ;Screw identification JR C,EXIT ;They don't live here LD HL,FLAG_B1 SET 3,(HL) ;Setting the screw presence flag LD A,(23798) CALL ST0_DRV EXIT ;--------------------------------------- ;2. Selecting the "disk drive". ;Selects the appropriate ;section, all further ;the work will take place with him. ;in: [A]- (0-3) drive number. ;out: 'CY=1 means not a screw, ;[A] does not change. ;--------------------------------------- ST0_DRV LD (STT_FDD+#02),A;useful LD HL,FLAG_B1 BIT 3,(HL) JR Z,STT_FDD ;well, no, what can you do. OR #80;this bit is responsible for;auto-connection i.e. connect ;what is given in the auto sector ;settings" LD H,#00 ;MOA glitch, if HL<#C000 then ;SET 4,(HL) will occur. What if ;more then most likely too ;will occur in the 8th bank. LD C,#23 RST #08 DB #81 JR C,STT_FDD ;The image is not connected. Work with ;disk drive. LD HL,DIS_BUF LD DE,#0005 ;Equivalent to reading 8 and 9 LD BC,#0124 ;sectors of track 0. RST #08 DB #81 LD A,(DIS_BUF+#00E7) CP#10 JP NZ,ERROR ;The image is connected. But it's not ;trdos image. Recommended ;write some curse- ;lity and offer to choose ;another disk. LD HL,FLAG_B1 SET 0,(HL) ;Set the "Current disk" flag ;this is the section of the screw." JR $+#03 ;----------------------------; STT_FDD SCF LD A,#00 RET ;----------------------------; ;3. The actual driver. ;in: HL - Download address, ;or the address of the data to be written. ; D - Track. ; E - Sector. ; B - Number of sectors. ; C - loading sign (#00) ;or entries (#01). ;out: ;--------------------------------------- LD A,(FLAG_B1) RRA JR NC,FDD ;work using a turbo loader. PUSH HL ;convert the coordinates on the disk ;to block number LD A,E LD L,D LD H,#20 ;in L track number SLA L RL H JR NC,$-#04 LD D,#00SRL E ADD HL,DE INC HL ;Sectors on the screw are numbered starting from 1. EX DE,HL ;DE - sector number POP HL ;If CY=1 then we need to consider RRA ;(write) into memory the second ;half of the sector. ;----------------------------; LD A,#01;second half CALL C,READ_1B LD A,B AND A RET Z;one sector? DEC A JR Z,READ_1B ;another one from the beginning of the sector. PUSH HL,DE,BC SRL B LD A,B PUSH AF SRL C LD C,#24;reading JR NC,$+#04 LD C,#25;record RST #08 DB #81 POP AF,BC,DE,HL RET NC; all sectors. PUSH HL ;another from the beginning of the sector LD L,A LD H,#00 ADD HL,DE EX (SP),HL SLA A LD D,A LD E,#00 ADD HL,DE;address POP DE;block number XOR A ;-----------------------------------; ;Read/write half of the sector. ;HL-address ;DE - block number ;C - read/write ;A =0 first 256, =1 second half. ;-----------------------------------; READ_1B PUSH HL,DE,BC,DE,HL,BC,AF LD HL,DIS_BUF LD B,#01 LD C,#24 ;Reading a sector from a screw RST #08 DB #81 POP AF LD DE,DIS_BUF ADD A,D LD D,A POP BC,HL SRL C;reading? recording? JR C,$+#03 EX DE,HL;reading.LD BC,#0100 LDIR ;transfer to sector from memory ;or vice versa. LD HL,DIS_BUF POP DE JR NC,$+#07;was reading. LD BC,#0125 ;Write the changed sector. RST #08 DB #81 POP BC,DE,HL INC DE DEC B INC H RET ;--------------------------------------- DIS_BUF DS #0200 ;------------------------------------------------------------ I don’t know, however, how fresh the above is ;-) Best regards, Alexander/Merlin. CMTG/Concern Chaos