Pseudo-ROM function.

ZXNet echo conference «code.zx»

From Wladimir Nikolaev To All 16 January 2000

┌─ Forwarded by Wladimir Nikolaev ─────Not─a─niger─── │ Posted from: REAL.NEOS │ From: Alexander Bondarenko (34:1/90.1) Sat 25 Dec 1999 16:40:05 │ To : All () │ Subj: [FWD] Pseudo-ROM function. └────────────────────────────── ─────────────────────────────── === So get forwarded msg, All === -= STUDIO STALL =- GOOD DAY, All! So, let's continue our debate about the operating system... The use of pseudo-ROM is questionable. Some comrades suggest cramming an operating system into it so that you can Use its functions through all sorts of RSTs. I’m going to throw this idea aside, because I’m not only thinking about myself. You can play with RSTs even with a regular 48 ROM. At least remember how it is done in all known IS-DOS... At the same time, however, when calling all functions through this contraption, you will have to follow behind address 23633 - the address of the function handler address will be there. Also, you will have to save the contents of DE'. And the beginning of the function handler will be the following: EX DE,HL INC SP INC SP POP HL EXX ... Many people who need an operating system don't have such a thing as a pseudo-ROM. Not all of them can soon shovel their computer so that such the thing appeared. Hence the conclusion - the system should not be based on the type of computers with pseudo-ROM.Pseudo-ROM must be used to cram code into it that works with high memory, with several pages at once, and cannot be posted on the page. For example, you can install a RAM disk driver there, or procedures for exchanging large amounts of data between memory and external devices. In the acceptable minimum, where there is no pseudo-ROM and little lower memory, you will have to create such a thing as an “exchange buffer”. At the same time, all drivers of the above type there should be two types of work: buffer and direct. With direct - everything is clear, all memory is available to the driver. With a buffer, this is when the driver sits in the upper memory, it will take data from the external device and throw it into buffer. Then, when the buffer is full, it will jump to the serving buffer procedure sitting in the lower memory, which will click the page and throw contents of the buffer to the appropriate place... During its initialization, the driver itself must “guess” which mode is needed enable, direct or buffer... And with a straight line, it’s still faster. Hence the conclusion - we install the appropriate bells and whistles. ;))) SEE YOU, All! -+-----▄█▄--▄--▄▄▄▄--■-▄█▄▄---------[STUDIO STALL]-[ZX-CLUB]--- -+-(C)▐█▄█▌▐█▌▐█▐▌█▌▐█▌▐█▌-/STALL---[ASSM]-[GFX]-[GAMEMAKING]-- -+-----▀-▀--▀▀-▀--▀--▀--▀▀▀---------[BEER]-[SAMOGON]-[PC-SUXX]- -+- Lara Croft MED 4.40 ---------------------------------------+ Origin: Abbreviation: Ministry of Internal Affairs - we are in shit... (34:1/90.1) === CUT === Hi, All! With Best regards, Lynx^XPL0S!VE ... [team Plutonium] [Firestarter] [Girls] [GMD] { Our name is Legion. }