schwager@p.cs.uiuc.edu (10/25/89)
I'm having a problem that I've finally decided to either figure out,
or live with. I've got Aztec C version 3.4 (yeah, yeah, I'll upgrade
soon... real soon...), and I can't seem to get make, cc, as, and ln
resident. It seems that if I use rez by Jim Goodnow, or the 1.3 resident
command, the machine still wants to go to my disk that contains those
programs, no matter what. I've tried cd'ing to the directory and running
resident and rez using both absolute and relative pathnames, to no
avail. Is there something I'm forgetting here?
...(later)....
Well, I just did some more investigating. It looks like "make" is
resident correctly. As a matter of fact, I can run make, cc, as, or ln
from the CLI with no trouble. It seems that since these are being
called from make, they're not being found as resident programs.
Is there any way I can get around this?
By the way, I've got an A500 running WB 1.3 (with 1.2 roms) and the
A501 ram expansion.
Also, there's something else that's been bugging me. Say I have my "cd"
command on the disk in drive df1:, instead of on my boot disk. And I have my
path set to include the directory on that disk that cd lives in. So I use
cd, no problem, until I pop that disk out. Now if I try to use it, it'll
say "command not found". But let's say I pop the boot disk out. Then I'll
try to run something that's in my C: directory, on that disk. It'll put up
a requester to put the boot disk back in. The $6 million question: why
doesn't Amigados always search all the paths for a command? It seems
kinda inconsistent this way, to me.
-Mike Schwager
INTERNET:schwager@cs.uiuc.edu | "They say into every life a
UUCP:{uunet|convex|pur-ee}!uiucdcs!schwager | little rain must fall,
BITNET:schwager%cs.uiuc.edu@uiucvmd | But your dreamcloud has burst
University of Illinois, Dept. of Comp. Sci. | and dripped all over your face"
-Matt Johnson, _The The_