Hi Pat,
This sounds liuke a good strategy.
I would say 2038 as default, 2037 (including winkrnl) as option--unless
2039 shows up first (doesn't look likely). If 2039 gets something
worthwhile, 1.11 is an option.
I agree - same as in 1.0, the stable kernel is the
default and the unstable
Still no reason to add experimental things to stable now :-)
The solution is easy: Add it to the UNSTABLE fork
No. Because first, I don't develope DOS-C, and second, forking is bad and
makes merging changes back in harder. Since your opinion seems to be that
filesystem extensions can never
Indeed JAM only works on non-FAT32 kernels because of different
data structures...
Any other different structures besides the SFT?
JAM apparently needs the start cluster of
the compressed disk file so it can use lowlevel (int 25/26...?)
calls to access that file without causing reentrancy
Hi,
Jim reinstated SVN write access so I committed a patch that I have
used internally in a not so clean fashion for a long time:
cross-compiling from Linux using Open Watcom. The reason why: well it
is more convenient and quicker (less than 2 vs. 20+ seconds here) to
cross-compile than fire up
