Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!husc6!bloom-beacon!gatech!purdue!decwrl!labrea!polya!ali
From: ali@polya.STANFORD.EDU (Ali T. Ozer)
Newsgroups: comp.sys.amiga
Subject: Re: Manx 3.6a and SDB
Keywords: HELP!
Message-ID: <2823@polya.STANFORD.EDU>
Date: 13 May 88 17:23:30 GMT
Reply-To: ali@polya.Stanford.EDU (Ali T. Ozer)
Distribution: na
Organization: Stanford University
Lines: 28
References:

In article <11212@sunybcs.UUCP> ugblaszy@sunybcs.UUCP (Dave Blaszyk) writes:
>	I was hoping to run MANX, on a vanilla A2000 ( with (1) floppy, 
>and (1)meg of ram, and using VD0:).

I would mail to you directly if I could, but I can't. I know a person who
was developing on a 512K, 1 floppy Amiga until last night (when his 2 Meg
expansion finally arrived). You can fit cc, as, ln, emacs, the include 
files, c.lib (or c32.lib), and various CLI commands such as list, copy, etc,
on a single floppy, and still have 8-9% of the disk empty.  For doing small
development, this might be fine. For speed, copy cc, as, and c.lib into
VD0:. 

For bigger projects, you might copy most everything from the boot disk
to VD0: (possibly filling up half your memory), then take out the boot disk
and stick in your work disk. One problem with this is that everytime you
guru, you'll have to insert the boot disk in. (This will be remedied when
we all have 1.3, with recoverable RAMdisk boot. Right?)

You might also look into using precompiled header files --- if you're 
working on a project for which you have a good idea of what system .h files
you need, you can create a precompiled header file, put it on your work 
disk, and thus avoid copying all the .h files into VD0: during boot time.
This also speeds up compiles considerably.

In my experience, you will not be able to fit SDB on the boot disk with the
other Manx stuff. I usually put a copy of SDB on my work disk.

Ali Ozer, ali@polya.stanford.edu