Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!sdd.hp.com!caen!ox.com!umich!terminator!terminator.cc.umich.edu!swood
From: swood@terminator.cc.umich.edu (Scott Wood)
Newsgroups: comp.sys.atari.st
Subject: Sozobon C and dstart.o <==> Ram Disk
Message-ID: <1991Feb4.183344.12478@terminator.cc.umich.edu>
Date: 4 Feb 91 18:33:44 GMT
Sender: usenet@terminator.cc.umich.edu (usenet news)
Organization: U of Michigan, ITD Research Systems
Lines: 21

I have just gotten my Sozobon C set-up going, and I am having a lot of fun
with it.  I thank all of you for the help and suggestions with getting it 
going.  However, I was noting that with my single drive set-up, the thing
works very slow, so instead of adding my libraries to the ram disk, I am
trying to get my bin directory to work from there.  I noted there-after, that
the cc program was unable to find the dstart.o file that is usually in the
sozobon/lib directory.
	For a background to what I have set up, I am using gulam as a cli, and
I am using a file called sozo.g to copy the sozobon bin directory and the
sozobon lib directory into the corresponding directories in my RamDisk
(H:) that I set up with rambuffer.acc.  I then set paths to h:\sozobon\bin,h:\,
a:\,. and do my work from the a: drive.  the ue works fine for my editing, and
then cc main.c gives me the error that it can find the dstart.o file.  I
tried cc -IH:\sozobon\lib but that returns the same result.
	I have discovered that if I move to the H: drive, and compile the
file in the a:\drive from there, it does work (cc a:\main.c) but it is a
bit annoying, and I would hope that it may not be necessary to do this.

thanks in advance for the help...

swood