Hi Volkert,
> By the way, the dosemu2 developers are also developing fdpp, a 64-bit DOS > kernel that aims to provide a DOS-compatible userspace and that can run in > Dosemu2. (Not sure if it always uses fdpp by default.) Since it's a 64-bit > process, I'm not sure how fdpp and dosemu2 handle the running of 16-bit > code without some kind of software emulation. As far as I remember, FDPP just does most of the DOS work on the Linux (or potentially Windows) host side of your reality. The DOS apps still run in the same good old 16/32 bit tasks as before, although you will more often be using an emulated CPU compared to classic DOSEMU now. I could claim that FDPP is a very elaborate change in the memory model when compiling a classic FreeDOS kernel, but I am sure that is a rather bad description. Also, FDPP got heavily tuned since the DOSEMU2 product cycle involves frequent testing of many features and compatibility etc. While DOSEMU2 tends to change quickly and sometimes in unexpected ways, it usually works better than classic DOSEMU. So if you are fine with updating your config or autoexec from time to time, or even sticking to package-maintained default versions of those, you should try it :-) Of course you can still run DOSEMU2 with classic FreeDOS kernels instead of FDPP. You can also still boot disk images containing other DOS etc. Note: If you use the cool "a Linux directory is presented as C: drive" boot style, you will now have to explicitly load a driver to gain write access. In the old DOSEMU, some automatic magic made it work "without". Cheers, Eric _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
