AUTOLOAD ISDOS

Tue 8 Jun 1999 you wrote here:

OG> But there is no ready-made one. If only because there is no specifically formulated
OG> task.

I formulate: we need the source code of the procedure placed in ROM (we will determine the location based on
the size of the procedure), at the start of which the IS-DOS system is loaded from the screw.
Controller - Nemovsky.

All the best.
Best regards, Roman.

Sun 13 Jun 1999 at 10:26:16, Roman Milukov => Oleg Grigoriev:

RM> I formulate: we need the source code of the procedure placed in the ROM (we will determine the location
RM> based on
RM> the size of the procedure), at the start of which the is-dos system is loaded from the
RM> screw.

Theoretically, you can do this: on a certain fixed place on the screw, with
the help of the utility, register information about the load capacity and location of the
isode swap. And then watch from the ROM.
By the way, something similar to this was done in the “Nemov” ROM. Therefore, in order not to reinvent the wheel, it would be nice to look at uni_con.com and uni_boot.sys. I don't have them. And the little thing itself won't hurt. :)

RM> Controller - Nemovsky.

And these are specifics. :)

WBR, Oleg.

RM> will be determined based on the size of the procedure), at the start of which
RM> the IS-DOS system is loaded from the screw. The controller is Nemovsky.

And it is not specified from which pancake/track/sector the is-dos
disk begins. You can set these parameters yourself in ide_tune.com asked. And to boot
the system you need the file is_dos.sys, and to read it from the screw you need to know
where the boot is-dos disk begins. It's a bummer, though.
You have to convert is-dos disks to ms-dos and there will be only one problem -
not enough space on the hard drive.

Kirill Frolov. [ZX]

KF> And it is not specified from which pancake/track/sector the is-dos
KF> disk begins. You can set these parameters yourself in ide_tune.com asked. And to boot
KF> the system you need the is_dos.sys file, and to read it from the screw you need to know
KF> where the boot is-dos disk begins. It's a bummer, however.

Usually the screw breaks so that the devices start with some multiples of
50-100 tracks, and damn/sector is always 0/0, it seems.
Set fixed. For example, the system disk will start from the 400th
track. (Whoever wants it before flashing it into ROM.) And in CMOS, assign special cells for this. We look in CMOS before loading, if there is no CMOS, we take the 400th track as a start.

OG> Theoretically, you can do this: at a certain fixed place on the screw, using the
OG> utility, register information about the load capacity and location of the
OG> iso swap. And now look from the ROM.

I don’t want to get confused with unnecessary utilities. And I wouldn’t want to strictly fix the place for
this information. Here you should use CMOS.
And what do you understand by the word “swap”? Like what Renat Mamedov suggested?
It is advisable to use the standard is_dos.sys.

OG> By the way, something similar to this was done in the “nemov” ROM. Therefore, in order to not
OG> reinvent the wheel, it would be nice to look at uni_con.com and uni_boot.sys.
U
OG> me them no. And the little thing itself won't hurt. :)

No one wants to show these things for some reason!.. :(
Maybe there isn’t such a thing there?!! Maybe the subject in KAI is a hoax? Or was it made there through
()()?

RM> I don't want to get confused with unnecessary utilities. And I wouldn’t want to rigidly fix the location
RM> for
RM> this information. Here it would be necessary to use CMOS.

In any case, you will have to be “confused.” The swap coordinates on the screw are not a constant - they have to be registered every time. And in cmos you can at the same time put the geometry of the screw - it will rulez. It will take only 8 bytes.

RM> And what do you understand by the word “swap”? Like what Renat Mamedov suggested?
RM> It is advisable to use the standard is_dos.sys.

And this is what it is. :)

OG> You will have to “get confused” in any case. The swap coordinates on the screw are not
OG> a constant - you have to register them every time. And in cmos you can also put the
OG> screw geometry - it will rulez. It will take only 8 bytes.

Well, put it in, please. There's a lot of space there. Anyway, someday you'll have to push it in there.

I actually didn't dream of such versatility. I would be quite happy with setting up the procedure before flashing the firmware for a specific screw model. And in CMOS to store
only the initial track of the system device. I don't plan to change screws often.