>> ... would this have any effect on existing DOS software?
at least a bit.
to transfer data between BIOS, DOS programs and your driver you need a
buffer in the precious 640KB space.
whatever size you select (due to performance over resource usage),
you are hurting real mode programs, more or less
As Eric mentioned, a lot of disk tools would break. But I feel that
swapping out the filesystem is overkill. Better to find the underlying
software problem and fix that instead.
I'm very curious about what you said that Dark Forces is a crash culprit.
That's unexpected. Are you referring to Star W
Hi!
> That sounds a lot like using an initramfs in Linux.
Exactly.
> But kernel? Why? The idea is that ext4 would be a first-
> class citizen in kernel space just like FAT16 and FAT32
Let me give some examples... The ISO9660 driver for Linux
is more than 40 kB on disk. The one for UDF is 110
Hello Eric,
Depends. If you want to be able to BOOT from ext4, you would
have to boot a virtual MEMDISK boot floppy from GRUB, then
load your new driver to open the ext4 partition ;-)
That sounds a lot like using an initramfs in Linux. Am I getting the
right idea?
I would NOT attempt to make th
Hi Michał,
> Suppose I wanted to write an ext4 driver for FreeDOS and integrate it
> such that it's possible to use ext4 on a system partition...
You would probably write it as a protected mode TSR using the
network redirector interface, similar to VMSMOUNT for FreeDOS.
> ... would this have an
Hello everyone,
Suppose I wanted to write an ext4 driver for FreeDOS and integrate it
such that it's possible to use ext4 on a system partition. And let's say
this plan materialized - would this have any effect on existing DOS
software? I'll go on why do I even consider this, but I want to kno
