Path: utzoo!attcan!uunet!cbmvax!rutgers!sunybcs!ugblaszy
From: ugblaszy@sunybcs (Dave Blaszyk)
Newsgroups: comp.sys.amiga
Subject: Manx 3.6a and SDB
Keywords: HELP!
Message-ID: <11212@sunybcs.UUCP>
Date: 13 May 88 14:09:18 GMT
References: Manx Aztec manual
Sender: ugblaszy@sunybcs.UUCP
Reply-To: ugblaszy@sunybcs.UUCP (Dave Blaszyk)
Distribution: na
Organization: SUNY/Buffalo Computer Science
Lines: 30


In recently purchasing Manx 3.6 C compiler with SDB for the Amiga, I was hoping
to finally do some serious hacking, since I am finally graduating.  I began to
read the manual on MANX C.

	I was hoping to run MANX, on a vanilla A2000 ( with (1) floppy, 
and (1)meg of ram, and using VD0:).  In reading the section, on setting
up for one floppy drive, they suggest to trim the SYS1: disk to use this as a
workspace.  This seems stupid, I have at least one meg of Ram, could I not
just put the libs and my C source code in VD0:?  This would decrease access
to the drive and hopefully increase compile and link time.

	Here is my question, to anyone with a helpful hint on working on a 
1 drive system, (and NO I cannot afford anymore HARDWARE!), 

??????????????????????????????????????????????????????????????????????

How can I setup my MANX C compiler with my current system, what 
startup-sequence is best, how can I use SET commands to help in
finding the important libs and include's.  Could I also put SDB, either
on the SYS disk or in VD0,  Is Ronald Reagan really ALive?

??????????????????????????????????????????????????????????????????????

Any help in this problem, would be much appreciated, Please only send
me mail do NOT repost or follow-up.  And if you are wondering why
I did not figure this one out myself, I am too lazy to figure out all
the details myself, especially if someone else already knows the answer.

--DvBlaze