Hi ECM,

thanks for the explanations! If I understand

https://github.com/FDOS/kernel/issues/50

correctly, Windows 386enh support is not part of the
automated builds yet because there originally were
limitations regarding which compilers are supported,
which have since been resolved?

The second half of the thread sounds like it still is
non-trivial to get Windows to work smoothly, but at
least it does work to some degree, so I would suggest
to already enable all Windows support by default :-)

Regarding GPT support: The history.txt says a bit does
exist. I have not checked whether source code does...

The WIN31SUPPORT define is still not enabled/defined by default I believe. Some discussion in [7]. At some point I manually built a kernel including it. I also contributed a workaround to allow the gcc build to succeed with WIN31SUPPORT defined on 2024-02-04 [8]. However, I did not test this nor compare it to Enhanced DR-DOS's support of the same APIs, it just builds now with gcc ia16 as opposed to failing at build time.

So EDR-DOS also has improved Windows support now? How
stable is the Windows support there compared to FreeDOS?

Interesting [8] diff! The GNU C implementation seems to
handle 3 segments plus the way to tell where instance
data ends differently from the implementations for the
other compilers? And there is something about the lol
pointer in win.h, not affecting other patched places?

Maybe that just meant that GNU C wanted things to be
done properly while other compilers accepted somewhat
less elegant ways? Or to put it in a different way:
Could it be useful to use your patch for all other
compilers, without #if defined __GNUC__ condition?

Regards, Eric



[1]: https://pushbx.org/ecm/download/fdkernel.zip
[2]: https://pushbx.org/ecm/download/fdshare.zip
[3]: https://pushbx.org/ecm/download/freecom.zip

...

[7]: https://github.com/FDOS/kernel/issues/50
[8]: https://github.com/FDOS/kernel/commit/ab3cac6d0c3a6014fcf0f450c77f1e3d7177cf99





_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to