Path: utzoo!mnetor!uunet!cbmvax!rutgers!mtune!mtunx!whuts!homxb!antique!cjp
From: cjp@antique.UUCP (Charles Poirier)
Newsgroups: comp.sys.amiga
Subject: Re: Do I have a lemon?
Message-ID: <2114@antique.UUCP>
Date: 18 Mar 88 01:02:48 GMT
References: <1021@pur-phy> <2079@phoenix.Princeton.EDU>
Reply-To: cjp@antique.UUCP (Charles Poirier)
Organization: AT&T Bell Labs, Holmdel, NJ
Lines: 23
Summary: Beats me. Workaround.

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.

-- 
	Charles Poirier   (decvax,ihnp4,attmail)!vax135!cjp

   "Docking complete...       Docking complete...       Docking complete..."