>> conclusion: don't use FreeDOS as a 'server' machine. > > Sure, that's the obvious "easy" way out. > > But wouldn't it be better "overall" (and wiser) to 1). actually find > out what MS-DOS does, and 2). "fix" it in FreeDOS' kernel? ;-)
If you are indicating that you want to volunteer... ;-) (... if that would indeed be the case, then I'd suggest gaining practice in C, in 86-mode 386 assembly language, and in using a capable enough 86-mode debugger to inspect DOS kernels as well as reading "Undocumented DOS" Second Edition and "DOS Internals" at least, plus optionally "FreeDOS Kernel" as well. [*] Then, one would have to become acquainted with the FreeDOS kernel's sources. And then the required course of action would either be self-evident, or one would have to start getting creative!) Regards, Chris [*] Don't read "Dissecting DOS" though. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Freedos-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-user
