Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!mcsun!ukc!edcastle!mfg From: mfg@castle.ed.ac.uk (M Gordon) Newsgroups: comp.sys.amiga.tech Subject: Re: Which directories must be present to boot? Message-ID: <6094@castle.ed.ac.uk> Date: 4 Sep 90 08:23:03 GMT References: <5962@castle.ed.ac.uk> Organization: Edinburgh University Electrical Engineering Lines: 31 (sorry to post this but our mailer can't cope with the return address) In article hclausen@adspdk.CBMNET (Henrik Clausen) writes: #>In article <5962@castle.ed.ac.uk> mfg@castle.ed.ac.uk (M Gordon) writes: #>If sys:c and sys:libs are not present the boot will start #>the drive motor and then hang. If I create sys:c and sys:libs as empty #>directories my startup file is read and I can assign libs: and c: to their #>correct places. # # You don't happen to use BindNames or a similar program to do the assigns? #BindNames has a bug that will cause it to hang the machine under these #circumstances. # #-- #| Henrik Clausen, Graffiti Data (Fido: 2:230/22.33) | #| ...{pyramid|rutgers}!cbmvax!cbmehq!adspdk!hclausen | #\__"Do not accept the heart that is the slave to reason" - Qawwali trad__/ Yes, I am using Bindnames to set things up. Since I really don't want to switch back to explicit assigns, until the bug is fixed I'll just leave things as they now - sys:c and sys:libs empty with the hidden bit on. I'm using SKsh so I never see them. Thanks Michael -- _ _ _ _ _ Michael Gordon - mfg@castle.ed.ac.uk OR ee.ed.ac.uk | |_| |_| |__| |_| | | . . . . . . | I spilt spot remover on my dog and now he's gone! |_________|~~|_____|