a couple of questions about is-dos

+-Hello, |All! +-------- 1.application 6 "block device vector" - status register do the options correspond to "0/1" or "1/0"? 2.in the same place "driver without buffer" means that the parameter "number current sector in buffer" does not make sense? (and why the sector, if operations occur with blocks (or is it with sectors?). 3. what kind of tricky QVST address is the request for? when accessing the device. 4.what does read/write prohibit/allow mean for RST? +-All the best, All! |I was with you |Valentin Pimenov aka Valker/Style_Group +---------------

Let your enemies, Valentin, die without sons! Thu 14 Oct 1999 at 23:09, Valentin Pimenov ═> All: VP> 1.application 6 "block device vector" - status register VP> do the options correspond to "0/1" or "1/0"? ────[ The file app_06 .t begins here ]─────────────────────── APPENDIX 6. Block device vector structure [censored] 0 SCCSR 1 Status Register. Bits 0/1 0..3 - cache device number 3 - driver without/with buffer 4 - auto-flush when recording (1) 5 - read prohibition/enable for RST 6 - prohibit/enable recording for RST 7 - past the cache / through it 1 DRCSR 1 Status Register. Bits 0/1: 0 - request for an address in QVST when accessing a device (APPENDIX 3 1 - auto-flush flag (reset by user) 2 - TRDOS/no 7 - do not/handle errors (erdrv(#1F)) 2 6 (see APPENDIX 4.) . ────[The file app_06 .t ends here]──────────────────────── VP> 2. in the same place "driver without buffer" means that the parameter "number VP> of the current sector in the buffer" does not make sense? Rather, a pointer to a buffer address is meaningless.VP> (and why sector, VP> if operations occur with blocks (or with sectors?). At the physical level (disk) - with sectors. Used to exclude repeated reading of the same sector. Otherwise, with kilobyte sectors and block-by-block reading (well, such a perversion), each sector would be read 4 times. VP> 3. what is this tricky QVST address - the request is made VP> when accessing the device. Pointer to the address of the request procedure for the device in wait mode. You can hang your procedure. :) ────[ The wait .h file begins here ]─────────────────────── WAIT.com - translation program indicated - block devices in standby mode pressing the key when switching yah. wait [keys] The keys indicate which devices are required We need to switch to this mode. In case absence of keys, the program removes from All block devices are in standby mode. Keys can be specified in the form: /A/C or /B /D . For example, if system device A, and current C, then the command: wait /s/b/T/d will allow YOU to transfer block devices A,B,C,D to keypress standby mode when switching. Useful when working with multiple logic ical devices on one drive.***************************************** 1993, IskraSOFT corp. St. Petersburg, Russia ***************************************** . ────[ This is where the wait .h file ends ]──────────────────────── VP> 4.what does read/write prohibition/permission mean for RST? But idk. I'm guessing that to set devices to readonly mode and writeonly. :) However, I have not seen a single program that would switch these bits in blockers, and also, I have not seen a single blocker that would check these bits when working. [WBR, Oleg. ] [ 04:45 16 October XXXIV A.S. ]