Looking for information on low level disk i/o calls

Страница 3/3
1 | 2 |

By Eugeny_Brychkov

Paragon (1232)

Аватар пользователя Eugeny_Brychkov

27-11-2011, 16:46

Yes, it seems to be the status quo I have - stack at exactly this location. Thank you.
Is there any workaround/solution to it? Let's say, have buffer for only one 1.44 drive. Or format 1.44 with non-standard parameters (e.g. 1K cluster - will have twice less FAT).

Another question: can kernel 2.0 fit into 16K ROM chip? Or to 32K ROM chip?

By Eugeny_Brychkov

Paragon (1232)

Аватар пользователя Eugeny_Brychkov

27-11-2011, 17:43

With 2K cluster 1,44 disk will have the same number of FAT sectors as 720K disk. If storing 224 small files (all the dir entries are occupied) only 448K of the disk will be occupied.

By zeilemaker54

Champion (345)

Аватар пользователя zeilemaker54

28-11-2011, 09:54

kernel 2.0 need 48K ROM, but in a memorymapper style (so all ROM pages are at page 1 04000H-07FFFH).
I would combine the kernel 1.0 and kernel 2.0 in one 64K ROM, just like the Turbo-R. There are a number of conditions when it automaticly selects kernel 1.0 (for example pressing the '1' key).

I would advise against using a non-default 1.44 format with smaller FATs, because you can not read 'normal' 1.44 disks that way.

I would use the combined kernel solution which i provide, and use in kernel 1.0 only 720K as max supported diskformat. In kernel 2.0 you can support 1.44 as dosformat.

Страница 3/3
1 | 2 |