home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!wupost!cs.utexas.edu!bcm!rice!ruf.rice.edu!amitp
- From: amitp@ruf.rice.edu (Amit J Patel)
- Subject: Re: BC++ for OS/2
- Message-ID: <BxyvCK.E8B@rice.edu>
- Sender: news@rice.edu (News)
- Reply-To: amitp@owlnet.rice.edu
- Organization: Rice University
- References: <1992Nov18.191828.21649@rose.com> <NmJguB1w165w@tcscs.UUCP>
- Date: Thu, 19 Nov 1992 14:09:55 GMT
- Lines: 38
-
- In article <NmJguB1w165w@tcscs.UUCP>, tcscs!zeta@src.honeywell.com (Gregory Youngblood) writes:
- |> From what I understand the current DOS version eats 53 to 58 megs with full
- |> install. Whats another 40. :)
- |>
- |> Seriously though, what does the current DOS BORLAND (not turbo) c++ take up?
- |> Does it really eat up 50+ megs? What makes it worth that?
- |>
-
- Are you talking DOS only or DOS+Windows? With DOS only, if you don't
- need ALL the memory models, and you don't need ALL the example code,
- it fits into 16 megs.
-
- These are my estimates:
-
- BC.EXE (IDE) 2 megs
- help file 5 megs
- BCC.EXE (cmdln) 1 meg
-
- libraries 0.5 megs [I use only 2 memory models]
- headers <1 meg
- various utils <1 meg
- turbo debugger 2 megs
- turbo profiler 2 megs
- turbo asm 1 meg
- class libraries ??
-
- If you don't need turbo assembler/profiler, delete it! I've deleted
- things like remote debugging/profiling capabilities, windows
- compiler/help/library/include files, example code, graphics library,
- extra memory models, utilties like grep/unzip/touch that I have from
- other places, help file for tasm (which requires thelp, which I also
- deleted), and other junk. [I used to have both Borland C++ 2.0 _and_
- Borland C++ 3.0 (and MS-Word, DOS, and Turbo Pascal) on my 40 meg
- drive, so I had lots of deleting to do]
-
-
-
- Amit
-