Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!udel!mmdf
From: kosma%human-torch@stc.lockheed.com (Monty Kosma)
Newsgroups: comp.sys.amiga
Subject: Falcon Weirdness
Message-ID: <21125@snow-white.udel.EDU>
Date: 5 Jun 90 18:15:43 GMT
Sender: mmdf@udel.EDU
Lines: 6

I had this happen with the old (v 1.0) version of falcon.  I just put a
blank disk (unformatted even!) in the drive and Falcon ran with no problems.
probably there's a "DF0" embedded in the code that could be taken out
with a disk zap utility.  But, if you are running v1.0, you really ought to
get v 1.1 (or better, the mission disk) which runs off the hard drive 
much more cleanly, and has lots of other nice things about it.