Ram Disk Driver. ;-)

Let your enemies, Aleksandr, die without sons! 13-07-98 at 19:05:18 Aleksandr Majorov ═> Oleg Grigoriev: OG>> Nope. Reading from the screw via #3d13 is still faster than reading from OG>> disk via #3d2f. I won’t tell you the numbers - I haven’t checked; I don't care for it OG>> it is necessary - through #3d13 something. :) But purely visually faster. OG>> A little bit. :) AM> ??? AM> strange, I think Kir told me that according to the test results, AM> which the LD fast-loader threw to him slightly overtook the screw! AM> Although I could be wrong - it was a long time ago... Oh... In short, the confusion in this matter bothers me a little... tala, and I spent 5 minutes with a stopwatch... And the scribblings are half- It'll probably be an hour... So... Reading 640 kilos from a floppy disk using a turbo loader ra takes 32 seconds regardless of the address it goes to reading. Screw. I read 640 kilos through #3d13 in 3 different ways - mi: 1. Reading in pieces of 16 kilos per jar starting from #c000. 2. Reading 16 kilo chunks into memory starting from #8000. 3. Reading in pieces of 32 kilograms into memory starting from #8000. The reading procedure is given in listing1. Naturally everyone times the register values were adjusted. Result:1. Operating time: 33.5 s. Reading speed: 19.1 kb/s. 2. Operating time: 24.0 s. Reading speed: 26.6 kb/s. 3. Operating time: 28.7 s. Reading speed: 22.2 kb/s. Frightened by the results I received, I decided to check that will be when using rst8. listing2. 1. Operating time: 16.0 s. Reading speed: 40.0 kb/s. 2. Operating time: 7.0 s. Reading speed: 91.4 kb/s. 3. Operating time: 11.5 s. Reading speed: 55.6 kb/s. You can already live with these numbers. I hope it’s clear why reading into memory above #c000 works melts much more slowly. We'll have to convert the copier to mode 2.2 :) Now it's 2.1 Or maybe I won’t... I’ll mess around with the transfer. But recording slows down significantly... Moreover, regardless of the address sa. 1:33:5 with #3d13 and 23:8 via rst8... I'm crazy... =============================================================================== ;listing1 │ ;listing2 ORG #7000 │ ORG #7000 LD HL,#0000 │ LD HL,#0001 LD (23796),HL │ LD (23796),HL LD B,40 │ LD B,40 LOOP PUSH BC │ LOOP PUSH BC LD HL,#C000 │ LD HL,#C000 LD DE,(23796) │ LD DE,(23796) LD BC,#4005 │ LD BC,#2024 CALL #3D13 │ RST #08POP BC │ DEFB #81 DJNZ LOOP │ LD HL,(23796) RET │ LD DE,32 │ ADD HL,DE │ LD (23796),HL │ POP BC │ DJNZ LOOP │ RET =============================================================================== [hum about crispy screws and menus] OG>>>> I hope gmx _will not_ have a ramdisk. :) Naturally, I meant the hard drive ramdisk. AM> everything is logical: AM> if there is a ramdisk for 256K (in dos), then for 2MB - why not AM> and no? Iron logic. :) I wrote 2 block ramdisks for gmx for isdos still around January-February. What I threw into the echo is the latest edition dated 04/23/98. At one time I even I was not too lazy to write help. I'll look for it right now... Yeah: ========cut======== ;(c) Ruiner ;21-01-98 AT 14:53:02 Drivers for RAM disk for Scorpion-2000 computer or for Scorpion with GMX controller. ed_gmx0.blk - uses all GMX memory and pages 9 to 15 Scorpion main memory. ed_gmx1.blk - uses only GMX memory. Since there are several options for installing memory incontroller, then writing its own driver for each of them seems difficult. You will have to mark up your email. disk using the create.com program based on the amount of memory that you have installed. To make this easier, see below On the table below you will find all possible options. ┌─────────────╥──────┬─── ───┬──────┬──────┬──────┐ │Memory capacity ║ 256 │ 512 │ 1024 │ 1280 │ 2048 │ ├─────────────╫──────┼─── ───┼──────┼──────┼──────┤ │ ed_gmx0.blk ║ 448 │ 1472 │ 3520 │ 4544 │ 7616 │ ├─────────────╫──────┼─── ───┼──────┼──────┼──────┤ │ ed_gmx1.blk ║ 0 │ 1024 │ 3072 │ 4096 │ 7168 │ └─────────────╨──────┴─── ───┴──────┴──────┴──────┘ ========cut======== Hehe... How do you like it, ramdisk for 7616 blocks? :) AM> Moreover, if the addressing is like on Pro, then all drivers AM> suitable, Why do we need crooked professional drivers? They themselves have no hands, what? :) AM> and in SPF they boasted about what rulez with is-dos AM> use 1MB RAM disk... In general, the SPF praised the pros very strongly... Well, where is this pro? :-> AM> Or did you mean a RAM disk made at the computer BIOS level? AM> As in spring? I don’t know about this... Yeah. Restarts, braking... "People like that don't win..." =) AM> But there is this IMHO: AM> 1) why? when there is a screw, with easily connected images Well, it’s not so easy... Climb into the shadows and press three Three buttons are just a little bit long... (I got greedy... :))) ) But a violinist (ramdisk) is not needed... If I need memory, then I I'll find it myself and use it as _I_ need... :) AM> 2) if it is possible to “resolve” the ROM firmware, then you do it yourself AM> you can make a RAM disk for yourself... Yes, I’d rather hang myself, as Merle advised... :) Best wishes, Oleg aka Ruiner.