[0/7] LARA_HDD.ZIP -- Scorpion HDD version

Lara Croft 4.10 -- Scorpion HDD version.

Posted with the permission of Oleg Golenkoff -- he is currently working on Lara.

If the setup has a slowdriver
line - #3D13 works, otherwise direct reading
from the partition via RST 8. Speed
corresponding =)

Disks are mounted once - when start
prog. If you need to change the disk, exit,
connect the disk, start again.

If you are interested, I will redo 4.50

WBR, Jason.

[Team Obituary][Team Friday 13th][Team Evil Maniacs][Team Huge Axes]

One day on Monday, June 5, 2000 at 01:17:45 Valerij Kozhevnikoff wrote
a letter to All about [0/7] LARA_HDD.ZIP -- Scorpion HDD version:

VK> Lara Croft 4.10 -- Scorpion HDD version.

I don’t know about anyone, but for me it’s terrible buggy. Or rather, when you work with a disk where the mail database is, then everything is fine. But as soon as Lara accesses the disk with PKT drives, the monitor loses all information about the connected subpartitions. True, if you then press MAGIC and select Auto detection hard
disk, all this information is restored, and such glitches no longer occur.

VK> Disks are mounted once - at the start of the
VK> program. If you need to change the disk, exit,
VK> connect the disk, start again.

This is not entirely convenient - often there is a need without leaving Lara,
for example, switch the disk with PKT and unpack mail from it.
In general, you are in vain using the function of connecting subpartitions, it is better to just
switch disks using the CHDRV (C=1) function and read RST #08 from them. There won’t be such inconveniences
and there will be less hassle.

VK> If you’re interested, I’ll redo it for 4.50

With both hands for it.

I wish you good luck!
Sincerely, Fyodor Odegov.

FO> This is not entirely convenient - often there is a need, without leaving
FO> Lara, for example, to switch the drive from PKT and unpack mail from it.

Of course. But the way you want it will be slower.
Now at startup I read the descriptors of the connected partitions into memory, and
in the future I connect using them. In the shadow you can mount anything, Larka
remembers what happened at the start and she doesn’t care about your manipulations. Why did I do this?
When connecting using descriptors, there is no real access to the screw => it's
fast.
You want an “auto-connection” to be done every time you change a disk, i.e.
so that the shadow guy climbs into the settings sector and looks at what is written there. ы?

FO> In general, you are in vain using the function of connecting subpartitions,
FO> it’s better to just switch the drives using the CHDRV (C=1) function and read
FO> RST #08 from them. There will be no such inconveniences, and there will be less hassle.

You see, in the subject the reading goes _directly_ from the partition, bypassing the TR-DOS file
functions, in _long_ sectors of 512 bytes. This is the lowest and fastest
level, there is nowhere lower. Isdos does exactly the same. Are you proposing to rise to the level of disks and work in sectors of 256 bytes?
This will not happen. Firstly, in this case, only
area #4000 - #BFFF can be read/written. Secondly, in terms of speed it will be muchslower.

VK> That is?
VK> It says “Mount on A:Rulezz\Disk01” only instead of “Disk01”
VK> there is an empty space?

That’s not what I’m talking about (although this also occurs). Let's say we have two disks: one with
Lara and the mail base, the other with PKTs. While we are working with the first (reading existing
messages), everything is fine, but as soon as we turn on the second
(turn on the tosser, read the file, etc.), glitches begin to occur, as if we have connected disks with an unknown format to all the drives (if we
go into the monitor and read the directory of any drive, it will write that the
disk format is not recognized :), but if we after that Let's select Auto detection disk, then everything falls into place, mail is collected, files are read, etc. That is, the whole
glitch consists precisely in the first connection of the disk with PKT's.
As I understand, the descriptors by which you connect the subpartitions are located
somewhere in the second bank, and so at the time of accessing the disk with PKT's, its
descriptor is not there, if you enter the descriptor there manually, then everything is fine.
Maybe the problem is in different ROM firmware? which one do you have? I have 4.01.

21 Jun 00 14:55, Fyodor Odegov -> Valerij Kozhevnikoff:

I apologize in advance for the brevity, it’s 2:55, and I have to get up at 7:00... In the evening
we’ll talk =)

[...]

FO> That is, the whole glitch consists precisely in the first connection of the disk with
FO> PKT's. As I understand it, the descriptors by which you connect
FO> subsections are located somewhere in the second bank,

#93CF. 21 bytes per drive, 84 bytes in total. At the moment of a glitch, look there. If the zeros
- something is wrong.

[...]

VK>> This is the lowest and fastest level, there is nowhere lower.
FO> How can there be nowhere, and the screw control bypasses the TM? :)

Completed stage =) This is how the driver works for me. The speed is almost like
a ramdisk.

Yes, and my ROM is 4.0.

VK> As soon as possible, right away. Who else needs it?

for me, for open ports. :) I'm too lazy - the brakes are not in the disk subsystem, but in the rack itself. :(

[ WBR, Oleg. ]
[ 23:56 27 June XXXV A.S. ]