system ala boot

Hello Paul! 10/13/97 you wrote about the “booth system” PF> ram disk 8 page and above PF> something can hang there with overlays PF> whatever... so nothing PF> I can’t say anything particularly specific. PF> if you have interesting thoughts - write, PF> only without swearing :) Of course, there are thoughts. I understand that this is will be like a program with the ability to work with tr-dos files + ram disk + overlays? If “yes”, then imho 128K will not work. -= RAM DISK =- If you imagine why you need a ramdisk: 1.to copy files 2.for fast loading of overlays. 3.to combine (1)+(2) it is necessary as minimum 512K, because even 256K is not enough, no that's 128K. -= OVERLAYS =- 1. definitely different disk doctors, track copier, etc. 2. a simple text editor based on capabilities comparable to ZxAsm. 3. calculator (good level Scientific in Vyndouz). 4. file converters (different systems in text and back to asmy/musical back and forth/pictures BMP-PCX-etc <=>speccy) 5. simple toys (I was just kidding over ZxAsm3.10 demo/MineSweeper :) 6. work with MS-DOS/IS-DOS disks Nothing else comes to mind :) -= SYSTEM CONCEPT =- 1. It is absolutely necessary that the system beas open and flexible as possible. This means that everyone with sufficient qualification could without studying tracers and write system code disassemblers overlay to suit your needs. Because it doesn't the capabilities of the system are so important in the sense functions, such as the system's capabilities for management and interaction of overlays. 2. each overlay must have its own data area. Even if one overlay launched 2 times (I don’t know why yet this may be necessary, but it may) each You must have your own area! 3. pay special attention to survivability systems. When one overlay crashes - the system should terminate/close it and continue working. PS: what I just wrote in the last section is similar to the requirements for example to Wyndows. Actually it's not quite yes. These are the requirements for any open system, and I think that’s what you intended like this. If I'm wrong, tell me! Waiting for an answer, Valker/Style Group -+- ZxAsm's editor

Hi Valentin! PF>> frame disk 8 page and above PF>> something can hang there in overlays PF>> whatever... so nothing PF>> I can’t say anything particularly specific. PF>> if you have interesting thoughts - write, PF>> only without swearing :) VP> Of course, there are thoughts. I understand that this is VP> will be like a program with the ability to work with VP> tr-dos files + ram disk + overlays? VP> If “yes”, then imho 128K will not work. and here you can dodge :) leave page for such a case, now about testing the machine, if there are more than 5 pages then it cuts from the table of available all 128 pages. VP> -= RAM DISK =- VP> If you imagine why VP> RAM disk needed: VP> 1.to copy files VP> 2.for fast loading of overlays. VP> 3. to combine (1)+(2) it is necessary as VP> minimum 512K, because even 256K is not enough, no VP> that's 128K. depending on what overlays we'll tell youDo you need everything at once? remember is-dos there leave only the very best if that’s all There will be no space left on the disk. at 256<>1024 kb 128 memory remains in system for overlays. VP> -= OVERLAYS =- VP> 1. certainly different disk doctors, VP> track-copier, etc. it will be in the system. VP> 2. a simple text editor based on its capabilities VP> comparable to ZxAsm. but that’s why I thought of an overlay system. VP> 3. calculator (good level VP> Scientific in Vyndouz). what I saw in Windows is strange with buttons... VP> 4. file converters (different systems in VP> text and back to music/ music VP> here and there/ pictures BMP-PCX-etc <=>speccy) and this is necessary. VP> 5. simple toys (here I was kidding VP> over ZxAsm3.10 demo/MineSweeper :) VP> 6. working with MS-DOS/IS-DOS disks don’t think that I’ll write everything right away, This is what I need alone. VP> nothing else comes to mind :) VP> -= SYSTEM CONCEPT =- VP> 1. it is absolutely necessary that the system be VP> is as open and flexible as possible. This means VP> that everyone has sufficient VP> could qualify without studying tracers VP> and write system code disassemblers VP> overlay to suit your needs. Because it doesn't VP> the capabilities of the system are so important in the sense VP> functions as system capabilities VP> management and interaction of overlays. and more specifically, now the window is working in the following way: rst 16 db 3,1,1,1,1,1,"handle",0,"text",0 code ^ ^ ^ ^ ^ ^ ^ ^ ^ ^end coord. y ┘ │ │ │ │ │ │ └window text coord. x ┘ │ │ │ │ └end code y size ┘ │ │ └ window title x size ┘ └ window color You can only remove the last one installed window, and it’s very simple: rst 16 db 4 window with key polling, specified as and the usual but code 5, and the program will not work from drawing window until pressed required key "enter" - confirmation "edit" - cancel and list of letters which are marked in the text of the window like: db "drive A ( )",13 db "drive B ( )",0 or db "eXit to dos ( )",13 db "exit to Basic ( )",0 that is, in capital letters, and the brackets are needed to display the "labels", they can bedon’t put it, but then it will be unclear what is selected. return procedure will return the code of the pressed key to register A, if "enter" is pressed or 0 if cancel. Now I'll make trigger functions so that when you click the corresponding key inverted value.look it will be like this: db "Tested drive [√]",0 as in TXT_WRTd :) well, I liked the idea. all changes are entered in _text_ _windows_! that is, if you need to find out the state of any item, then 1: scan the window for this case and 2: enter the variable into the window text and check its condition along the way. Page 7 is allocated for the buffer for windows. VP> 2. each overlay must have its own VP> data area. Even if one overlay VP> launched 2 times (I don’t know why yet VP> this may be needed, but it can) each VP> This must have its own area! Do you want multitasking? easy, but this will take a long time to do... because steamy. VP> 3. pay special attention to survivability VP> systems. When one overlay crashes - VP> the system must terminate/close it and VP> continue working. Well, this is not Windows or some other OS, here you have to take care of the “relegation” overlay. and the system will process it as best it can. VP> PS: what I just wrote in the last one VP> section is similar to requirements for example VP> to Vyndouz. In fact, this is not quite VP> so. These are the requirements for any open VP> system, and I think that’s what you had in mind VP> like this. If I'm wrong, tell me! mostly right, but come on more specifically, what and where... ▌▌║▌█▐│▌▌▐▐ WiTh The BeST wIsheS fROM ▌▌║▌█▐│▌▌▐▐ *C*R*E*A*T*O*R* ▌812/03.00▐ -+- zxasm+ positive

Hi All! In short, in just 14 hours, a lot changed, now when opening windows do not need to specify x and y lengths, the procedure will find them itself, length in x is calculated from the length of the "handle", and the height by the number of lines in "text+1 . Windows can open in 32 and 64 characters, Russian letters cannot appear in window text with key polling, only in regular windows and in xas format. support for other encodings under larger question, only in overlay programs. Most likely it will be possible to change the address fonts. and more specifically, now the window is working in the following way: rst 16 db 3,1,1,1,"handle",0,"text",0 code ^ ^ ^ ^ ^ ^ ^ ^end coord. y ┘ │ │ │ │ └window text coord. x ┘ │ │ └end code │ └ window title └ window color You can only remove the last one installed window, and it’s very simple: rst 16 db 4 Now I'll finish removing all the windows with one command like: rst 16 db 6 window with key polling, set as and normal but code 5, and the program will not work from drawing window until pressed required key "enter" - confirmation "edit" - cancel, and list of letters which are marked in the text of the window like: db "drive A ( )",13 db "drive B ( )",0 or db "eXit to dos ( )",13 db "exit to Basic ( )",0 or so, but here is already a reaction to trigger based, that is, either selected or not, regardless of other points.db "eXit to dos [ ]",13 db "exit to Basic [ ]",0 that is, in capital letters, and brackets are needed to display the "labels", they can be do not put it, then exit the survey will be carried out by pressing a key without confirmation by "enter". return procedure will return the code of the pressed key to register A or 0 if cancel. to separate groups of items you need separate them with "------", like this: db "eXit to dos [ ]",13 db "exit to Basic [ ]",13 db "-----------------",13 db "exit to Basic [ ]",13 db "eXit to dos [ ]",13 db "exit to Basic [ ]",0 Here you will choose either between two the top or three bottom points. as in TXT_WRTd :) well, I liked the idea. all changes are entered in _text_ _windows_! that is, if you need to find out the state of any item, then 1: scan the window for this case and 2: enter the variable into the window text and check its condition along the way. Page 7 is allocated for the buffer for windows. ▌▌║▌█▐│▌▌▐▐ WiTh The BeST wIsheS fROM ▌▌║▌█▐│▌▌▐▐ *C*R*E*A*T*O*R* ▌812/03.00▐ -+- zxasm+ positive