Quote:

The final version of MNBIOS will come with GUI, you knows, buttons, textboxs, windows, etc. And also will come with mouse pointer. But not all have a mouse!

Very interesting! But remember flyguille, I see three basic things that MNBIOS needs:

1. To be compatible with almost every MSX2 or higher (2+/turboR). The need of developing a FDC driver for each FDC is a disadventage. And remember that the OneChipMSX won't have even an FDC.
2. It should be easier to develop MNBIOS applications. At least it looks like it will require certain level of Z80 ASM coding skills.
3. It should be compatible with Sunrise IDE interfaces, including CF ones.

I'm sure that you are already aware of that, so I'm just remembering

About your 2nd point, Karloch: maybe some coder with plenty of spare time is willing te develop a C-library for that

For make more easy the programming on mnbios, i am doing a lot of libraries full of EQU sentences, so the programmer will be released of the task of to know the absolute values for each attribute, addresses functions, number's functions / subfunction.

But offcourse, it continue being assembler. So it will be just more readable.

On other way, i am not doing a reference manual for the programmer (like that big and dirty manual that i wrote for BETA versions). I am doing books, step by step with fully examples from the beggining to the more advance programming. But that will costs time!.

Other thing that will changes on mnbios, is back to the normal 8x3 filesystem but with the improvements that already have mnbios. And in another future version to jump to jouliet system.

Quote:

Other thing that will changes on mnbios, is back to the normal 8x3 filesystem but with the improvements that already have mnbios. And in another future version to jump to jouliet system.

Please, can you tell about jouliet system?

it is the one used on win95/98. it allows large filesnames like up to 63chrs iirc, where the extension is on the last point of the name.

How does that?

using a lot of directory entries for one filename. When larger is the name, more directory entries is used.

But it is backward compatible with msdos because all the files have also an 8x3 name that represent the large one!.

you knows, "filena~1.ext" , it is the used on CD-ROMs and on HARD DISKS (including FAT32 of WINXP).

all the directory entries that are used for long names are ignored by normal 8x3 functions because those entries have HIDDEM + SYSTEM + VOL attributed enabled, and have a INFAT = 0 (first absolute cluster of the file), that normaly is an error. And the filename starts with $E5 that iirc is ERASED file indicator. Also the name has illegal chars codes. So, all that to make sure that no one normal 8x3 aplication shows a long name dir entry as being a file.