Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!maverick.ksu.ksu.edu!umriscc!mcs213d.cs.umr.edu!mcastle From: mcastle@mcs213d.cs.umr.edu (Mike Castle (Nexus)) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: Infoplus 135 Message-ID: <1821@umriscc.isc.umr.edu> Date: 10 Dec 90 08:28:11 GMT References: <1990Dec7.121658.25371@aplcen.apl.jhu.edu> <2505@mentor.cc.purdue.edu> Sender: news@umriscc.isc.umr.edu Organization: University of Missouri - Rolla Lines: 17 How much does linking in ALL the *.bgi files into the .exe affect the size? Which would be a better deal: one .exe file with all the *.bgi files, or multiple *.exe files, each with a different (and hard coded calls to) *.bgi file? The single *.exe file would be more convenient, but possibly very large. Separate *.exe files would be more system dependent, but once the user installed just the single *.exe he needs, then he'll save some disk space. Essentially, it's a trade off between ease of use and storage space. Maybe a package with both types, and letting the user decide?? Just wondering, Mike -- Mike Castle (Nexus) S087891@UMRVMA.UMR.EDU (preferred) | ERROR: Invalid mcastle@mcs213k.cs.umr.edu (unix mail-YEACH!)| command 'HELP' Life is like a clock: You can work constantly, and be right | try 'HELP' all the time, or not work at all, and be right twice a day. |