[comp.sys.amiga] MANX SET and ASSIGNs

papa@pollux.usc.edu (Marco Papa) (03/21/88)

In article <2114@antique.UUCP| cjp@antique.UUCP (Charles Poirier) writes:
|In article <2079@phoenix.Princeton.EDU| kenchiu@phoenix.Princeton.EDU (Kenneth Chiu) writes:
||In article <1021@pur-phy| tlm@newton.physics.purdue.edu.UUCP (Timothy Lee Meisenheimer) writes:
|||I just recieved Manx 3.6 etc and like that SDB! But when I compile
|||I keep getting system requests for the boot disk - I don't boot up
|||on a compiler disk, I have most everything in memory - I can
|||click cancel and it goes on its merry way. I've got the environment
|||stuff 'set' correctly, and have reassigned C:,S:,T: and SYS: etc.
||
||forgetting something.  Use 'assign' to see if anything is still assigned to
||your boot disk.  Also try 'set'.  Oh, and for more information, try 'info'.
|
|I had a similar problem.  Moved all my compiler files to hard disk, did
|"set"s and "assign"s and "info"s out the wazoo, triple-checked my
|makefile. Using Manx 3.4a.  "Make" asks for sys1: each time,
|cancellable.  I still can't figure it out -- unless maybe the commented
|lines in my makefile are being read somehow.  Anyway, work around this
|by assigning sys1: as something innocuous like nil: or ram:.  Bingo, no
|requestors.

I have been using MANX 3.4, and MANX 3.6a + SDB, on a hard disk for months now
and never had any of the mentioned problems.  

I have the manx files on my second disk partitions (DH0B:).

SET shows the following:

INCLUDE=DH0B:include!DH0B:asm
CLIB=ram:!DH0B:lib!!
FUNCLIST=DH0B:lint/manx.c
CCTEMP=ram:

NO ASSIGNS are relevant to my configuration.

PATH shows the following (note Amiga2: == DH0B:):

Current Directory
RAM:
Amiga2:bin
....

-- Marco