Hi! > PG runtime takes up 80K, but it needs about 40K. > Turbo C 2.01, small model.
Small model = up to 64k code + up to 64k data. You could try other memory models, but I think it will NOT be worth the effort. If you use TINY model, you will get a .com with all code and pointers and data defaulting to NEAR. Well, you COULD use it. No idea how much code and data you need (not counting the heap). In .com files, the stack is always at the end of the 64k segment. I would NOT recommend moving it around because your program is written in C, not assembly language... Anyway. In .com files, default is to use ALL memory for heap. You can resize that with the normal DOS (or maybe Turbo C library) functions. As far as I understand, PG can use big amounts of heap when opening big files. Therefore you will not be able to reduce PG to tiny size anyway. And you will not be shelling out to DOS very often at all anyway. I recommend that you just leave things as they are :-). Eric. PS: I went on trying to compile ClamAV.net in DOS / DJGPP. This AUTOCONF stuff is a big pain in the a**! I had to install megabytes of Linux tools (sed, textutils, fileutils) in DJGPP. Luckily they have them precompiled on delorie.com ... but then still AUTOCONF tries to use filenames beyond 8+3 limits. I could download a new autoconf from delorie.com, but the one which comes with ClamAV already is modified for ClamAV, it seems? SUGGESTION: Could somebody with CygWin please compile clamscan WITHOUT stripping the relocation info? Then I could probably run it in DOS + WDOSX *directly* even as PE console executable. How does the CygWin / PE build process differ from building DOS / CWSDPMI executables? After all it is the same compiler!?? ./configure --disable-bzip2 --disable-pthreads --disable-cr \ --disable-urandom --disable-clamav --disable-clamuko --without-sigtool \ --without-clamd --without-clamdscan --without-clamav-milter --disable-dsig plus reduce SUBDIRS to libclamav and clamscan --> should create a lightweight and GNU gmp library free version of only the CLAMSCAN binary. Question is how to avoid stripping relocations, or even better build a DOS binary. You can put an -all-static in the clamscan/Makefile entry for clamscan$(EXEEXT) to link statically without DLLs... Uhm... excuse the double-topic posting. Eric. ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
