SEWALL@UCONNVM.BITNET (10/05/87)
Steve -
You got it. The reason you get a ProDOS error trying to read
KERMIT.INIT was because PREFIX isn't set to the path for the
init file. Perhaps Ted will have the next revision set the
prefix to whatever path kermit was BRUN from if it's value is
otherwise empty.
The easiest fix is to set the prefix before Kermit is BRUN (if
you use as "startup" program try):
10 PRINT CHR$(4);"SET PREFIX <path>"
20 PRINT CHR$(4);"BRUN KERMIT379":END
The fix I used, since the program does return to the Kermit-65 prompt
after the error message was:
SET PREFIX /KERMIT ('cause I boot the program from a disk with a
volume label of KERMIT)
QUIT (exits to BASIC)
BSAVE KERMIT379,A$1000,L$6900
(Voila! the prefix is set in the program every time it is BRUN)
---------------------
ARPA: sewall%uconnvm.bitnet@wiscvm.wisc.edu Murphy A. Sewall
BITNET: SEWALL@UCONNVM School of Business Admin.
UUCP: ...ihnp4!psuvax1!UCONNVM.BITNET!SEWALL University of Connecticut