question 2

ZXNet echo conference «code.zx»

From Dima Boyko To All 18 February 2001

Khayushki, All! PRINTA PUSH AF LD C,#12 RST #10 EXX POP AF CP#0D JR NZ,LL8057 BIT 0,(HL) JR Z,LL8079 CH1 CALL LL8079 RET C LD A,#0A JR LL8079 LL8057 BIT 1,(HL) JR Z,LL8079 who can explain to me what is going on here and what is located at the address in HL and what We're checking his bits. I’ll say right away that with such bells and whistles it didn’t work for me. As soon as I removed them, it worked immediately. With the best, Dima Boyko.

From Valerij Kozhevnikoff To Dima Boyko 23 February 2001

Hello, Dima! 18 Feb 01 09:24, Dima Boyko -> All: DB> PRINTA PUSH AF DB> LD C,#12 DB> RST #10 ······------====== Monitor glass cutter ======------······ 18(12):g_tydv Return the vector of the character output device. HL' - address of the vector of the symbolic output device, (HL')= cursor length for this device (see APPENDIX 5.) A - channel number of the current character output device ······------====== Monitor glass cutter ======------······ The driver installed on the system has There is only an 8-letter name (type in channel not stored). typ can be distinguished from lpr by 0th bit in the 13th byte of the driver (5th byte in vector g_typ(#12)). In na- at the front of each driver there is a century- torus of standard structure: ······------====== Monitor glass cutter ======------······ DB> EXX DB> POP AF DB> CP #0D ;character check on CR DB> JR NZ,LL8057 DB> BIT 0,(HL) ;this bit depends on the device. ;in general, this is a glitch, you don’t need to check it ;here, and in (HL'+5), see above. DB> JR Z,LL8079 ;if the screen, then just print,DB> CH1 CALL LL8079 DB> RET C DB> LD A,#0A ;if the printer, then add LF. DB> JR LL8079 DB> LL8057 BIT 1,(HL) ;this bit does not mean anything. DB> JR Z,LL8079 Where did you find this? DB> who can explain to me what is happening here and what is located at the address in HL APPENDIX 5. Structure of the character device vector output (SUVYV) / g_tydv(#12) DOS.SYS / offset name length comment tion -10 CRTYP 1 Channel number of the current SUV -9 PRCHR 3 Transition to the withdrawal procedure (PP) character to screen (printer) /ttyoyt(#A)/ -6 PRCPL 3 PP reference inverse/normal print mode / prcpl(#B) / -3 PRAD 3 PP coordinate settings / pradd(#C) / 0 BYTTST 1 Current cursor length. screen drivers 1 XYpos 2 Current logical print coordinates 3 Xypos 2 Current physical print coordinates 5 type 1 Device type: 0-screen/1-printer 6 ertype 2 Error processing address SUVIV DB> and which bits we check. There it checks your bits. And why the hell is this not necessary. DB> I’ll say right away that I don’t have such bells and whistlesDB> worked. As soon as I removed them, it worked immediately. This standard comes from ancient versions, such as Isdos 1.0. I've never done this at all I installed it and everything always worked. The simplest type driver from ZXWord is easy redesigned, no bells and whistles needed. WBR, Jason. [Team Obituary][Team Friday 13th][Team Evil Maniacs][Team Huge Axes]