So, all MNBIOS applications can be seem like a MegaROM?
How you handle CALLs/JPs to other pages? Calling a MNBIOS function, I
suppose...
YES
MSXDOS2 has this ability. Breeze, from Daniel Caetano, too. It's a damn
hard thing to program ASM codes with such thing. That's why I chose not
doing this in UZIX, even using C to write user applications...
Yes, nowaday hard need the correct driver for MNBIOS that is one issue
today, but the correct drivers will be programmed.
That's the bad side of ASM: you tie things too much. You have to waste space
in parameters/tables/etc because, in the future, you need an extra byte in
somewhere, and simply adding it may cause a complete rewrite of many
applications/drivers. Using C it's much easier.
But, anyway, when we try to anticipate everything, we reach nothing, because
we don't know in fact what will happen. I think an approach "make things work
now, and update later when needed" is better, because it's optimized.
I don't confuse nothing... you can do a "sector" driver based by example for
support RAMDRIVE or FLASH cards...and use it as a DISK.
Or you can define a "sector" as chunk of bytes that, for the upper level,
is a structure, and the kernel doesn't need to know this. Less effort to the
kernel, less code, more speed.
Structure based is the next level to the sector based level... then come the
file based as next level....
Implementing such abstraction for each device it's a waste of resources.
I hope you're not doing this in MNBIOS.
With file based you not need do a MSCDDRV and MSCDEX separated (like
MSDOS)... you only need one.
Right.
Regards,
Adriano
