On Tue, 3 Feb 2004, Luchezar Georgiev wrote: > So, now it works but probably the problem is just masked. (I wonder how > many other such problems can be masked even in the Watcom version?!) Of > course, the Watcom version is surely better but when you MUST stuff the > kernel in the BIOS ROM or in a diskette, a 2.3 KB size saving is really > very welcome (plus the 1.3 KB saving from aPack ;-) And Borland C++ 5.2 > is still used by Datalight for their ROM-DOS, so albeit inferior to > Watcom, it can't be ignored, can it? The more so as I'm sure it'll > follow the fate of Turbo C 2.01 and Turbo C++ 1.0 - will become a part > of their museum some day, which means FREE! (Did someone expect that > Turbo C[++] could be free 10 years ago? ;-)
hmm FREE is quite limited here -- being only redistributable for personal use. For Bulgaria it seems to make no difference at all anyway. anyway, the main advantage of turbo c 2.01 and c++ 1.01 over watcom is that these compilers are fast and small. What kind of advantage is there for borland c++ 5.2 then? Does it run on XTs too (Eric seems to make a big point about that)? Is it just as small? About smaller compressed kernels, did you try "-od" with Watcom? Surely that will bloat the kernel size a bit but should also decrease the entropy and therefore enable smaller compressed kernels. I already knew that turbo c 2.01 compressed kernels are smaller than the watcom equivalents. Perhaps you can see if the printf problem you encountered also happens for one of turbo c 2.01 or turbo c++ 1.01. That would at least enable me to easily reproduce it. Bart ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
