Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!PSUVM.BITNET!ART100
From: ART100@PSUVM.BITNET (Andy Tefft)
Newsgroups: comp.sys.apple
Subject: Re:  Customizing Kermit 3.85 & What are the protocols of Kermit??
Message-ID: <8905152048.aa09990@SMOKE.BRL.MIL>
Date: 16 May 89 00:48:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: ART100%psuvm.psu.edu@cornellc.cit.cornell.edu
Organization: The Internet
Lines: 18

Original note:
>I have noticed that the SET PREFIX command behaves oddly if a new volume
>isn't on a DIFFERENT DEVICE than the current volume (if I BRUN Kermit
>from S6,D1 with a volume of /KERMIT and then swap disks and
>SET PREFIX /DATA, I get an error -- however, if /DATA is on D2 there's
>no problem -- also if I BRUN from S6,D2 and /DATA is in D1 SET PREFIX
>works okay).


>Murph Sewall                       Vaporware? ---> [Gary Larson returns 1/1/90]

I've never had this problem and since I only have one drive, I ALWAYS
put a new disk in the same drive and SET PREFIX to it.

Could it be that this happens if you have a prefix set already when you
run kermit? I never have a prefix set when I run Kermit -- it's basically
run by a one-line STARTUP program and I almost always run it by booting
its disk. Do you have a prefix set when you run Kermit?