Hi, I don’t know too much about the innards of checking in and out code however, if you have the current version installed, you more than likely have the source to the current kernel.
I would advise you to go the route of MSCDEX and use the network redirector interface. You may want to read Chapter 8 of Undocumented DOS, 2nd edition to get a feel for the DOS File System and Network Redirector (assuming you have that book). If you don’t have that book, then Google the DOS redirector interface, which appeared in DOS at version 3.1 That will give you some useful tidbits and examples on understanding system file tables (SFT), the current directory structures (CDS), and how things like NETX, SHARE, and ASSIGN (for example) work. With regard to the development environment, Jim has posted somewhere that the general development tools are OpenWatcom and NASM. I personally have found OpenWatcom a tad bit overwhelming because of all that it can do. If you are more familiar with the Borland C compilers, you can use those, however, I would STRONGLY suggest gratuitous use of conditional defines and such to make the code more compatible for the final OpenWatcom build. Unfortunately, Linux doesn’t have a 16-bit C compiler (that I am aware of). GCC has some fundamental differences in C dialect from OpenWatcom and Borland which would require conditional defines (especially with regard to inline assembly) and GCC doesn’t support 16-bit OBJ files as a target, mostly COFF and ELF binaries which will not work on DOS (at least at the 8/16-bit level). I have a VirtualBox VM with FreeDOS installed that I can zip up and throw in my Dropbox if you’d like. -T > On Sep 27, 2015, at 6:57 PM, Geraldo Netto <geraldone...@gmail.com> wrote: > > Hi All, > > I was talking to Eric a few days ago about this exfat thread > and while we are worried with the license issues > I would like to volunteer myself to port current exfat from linux > kernel to freedos > > Of course, once it's a no-trivial thing i would like to ask your support > i cannot promise anything by now, once i know that talk is cheap as > Mateusz and Tom reported :) > > So, what do you think? > what is the svn link to checkout the freedos kernel code? > does freedos have any vfs-equivalent interface? which files are involved? > is Pat's book a valid/current reference to freedos kernel? > which books would you suggest me to read? > what is the easiest way to setup the compiler? > > i mean, should i setup a freedos vm with with openwatcom or freeware > version of tc > or do we have a way to 'cross-compile' freedos kernel on linux and use > the vm just to test the code? > > Suggestions are always very welcomed :P > > > Kind Regards, > > Geraldo Netto > Sapere Aude => Non dvcor, dvco > São Paulo, Brasil, -3gmt > site: http://exdev.sf.net/ > > On 25 September 2015 at 19:14, Ralf Quint <freedos...@gmail.com> wrote: >> On 9/24/2015 12:33 PM, Mercury Thirteen wrote: >>> We could undercut the competition and make our own free FAT >>> implementation which does fills the same niche as exFAT. >>> >> Which will be extremely hard to do without interfering with those patents... >> >> Ralf >> >> --- >> This email has been checked for viruses by Avast antivirus software. >> https://www.avast.com/antivirus >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Freedos-devel mailing list >> Freedos-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-devel > > ------------------------------------------------------------------------------ > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ------------------------------------------------------------------------------ _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
