Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Not a silly question. However, (at a guess) I reckon a lot of the underlying net code is probably POSIX based, which MS-DOS is not.

I notice there's a framebuffer version, so building a nano-linux distro that boots instantly into that shouldn't be that hard.



So there's the framebuffer code that's needed and then it's netcode.

So for the framebuffer code, maybe an MSDOS UNIVBE wrapper could be used.

For netcode, I have no idea, but a wrapper for POSIX calls must surely exist there also.

Anyyways. I guess the userbase would be pretty much nil, for this as alternatives do exist on DOS :)


For networking on msdos I recommend mTCP. Although it's C++.

The biggest problem however will be compiling the code. The only viable compiler for msdos is openwatcom so the question is if the code uses any fancy extensions or gnuisms. Also the only version of openwatcom that didn't produce broken binaries is the Windows version (or at least was about two years ago).

Happy porting :-)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: