#C Beginner
2 messages in this thread
Fran-
Now THAT's a responce. I believe you hit the nail squarely on the
head. First off, I needed to know what to focus on first. I tried so many
assigns and created so many directories in so many combinations that I
couldn't honestly tell what all I've tried. I'll go right to work on this.
Here's a silly question, what is the >NIL: redirection for in this line?:
copy >NIL: DICE:bin all to ram:c
Does this squelch the report the CON:?
I'm not too concerned with Amiga specifics yet. I'm sure I'll get
the Native Developers Kit eventually, but not 'til I'm sure I'll have any
use for it; that is to say, not until I'm pretty sure I'll be writing
ANYTHING. Ofcourse if this does start to produce results I'll want to send
Matt his due (suppose I'll have to get a job, eh?). Anyway, after changing
it's name to amiga.lib, I ran LIBTOS on ami.lib from the ZC package. That
should be OK, shouldn't it?. I'll just use the general headers for now, if
that'll work.
As far as hard resources go, I've got CBM's standard 512K expansion
for RAM and a single external drive. I'm not sure what I'll be able to do
with 1Meg and two drives. Again, this is just C-101 for me, I'll be
thrilled (for a while anyway) if I ever get the likes of "Hello, World" to
execute. I mount a recoverable ramdisk in my startup-sequence. It's
limited to something like 260K of room. I suppose that's not going to do
it, is it? I'll have to check out my startup to see if if I did cut any of
those ASSIGNs and MAKEDIRs anyway, I may just leave it (ramdisk) out for
use with this.
BTW, to tax you some more, I, being unemployed as it were, will
probably be forced to spend less and less time on here for a while. I like
the Doctor's Inn. I noticed that you're a sysop there, correct? However,
I'm not having the success I should. How do I go about extending my access
and (oops)
Steve,
The ">NIL:" redirects output to the NIL: device which simply throws it
away. As for using ami.lib from ZC, I dunno if that will work, I'm new to
the 68000 & Amiga & haven't reached the point where I understand all the
gritty details of how things work at a very low level… I guess you'll
just have to try it and see. If you don't want to spend the $20 bucks on
the 1.3 Kit, I believe you can get one from the local user's group for
free, leave me a note on Doctor's Inn & I'll try to direct you to the
proper person.
Looking in my StartupII file, I see the following:
makedir ram:env ;set up the ENV: directory
assign ENV: ram:env
Perhaps you can simply add this to your startup-sequence. To see which
assignments have been made already, just type ASSIGN on the CLI, you get a
list of assignments and mounted devices.
The installation doc you quoted from is, I believe, for those folks wishing
to rebuild the libraries themselves & make modifications. Ignore it for
now.
The primary sysop at Doctor's Inn is away on business & of course, there's
been a spate of thunderstorms around here :-/ I believe the board has
crashed & nobody's home to reset it, so it may be a week or two till it's
back up (it's too far away for me to reset, maybe if I ever get a car…).
I've been a co-sysop there for about 3 years, but have only been building
up the Amiga areas since January (when I bought one). DI is one of the
oldest local BBSs & one of the largest, we've got 80 message areas & about
1100 Megs online storage. The whole thing is a small part of a network of
13-14 computers in the sysops home. I think he has his eyes on a A3000, so
we Amigans might end up dominating the board ;-). Once you get into the
message areas, type "a53" to get to the local Amiga areas & leave me a
note, I'll direct you to all the help files & see about bumping up your
access.
–Fran