TIP: Click on subject to list as thread! ANSI
echo: cis.tandy.coco
to: Kevin Darling (UG Pres) 76703,4227 (X)
from: TONY CAPPELLINI 76370,2104
date: 1990-05-26 12:14:24
subject: #3820-#Selecting windows

#: 3830 S10/Tandy CoCo
    26-May-90  12:14:24
Sb: #3820-#Selecting windows
Fm: TONY CAPPELLINI 76370,2104
To: Kevin Darling (UG Pres) 76703,4227 (X)

Kev, the only other files that osterm uses that I know of are the osterm.ddir ,
osterm.options, and another one for user defined macros. Whenever I start it up
(from the HD) it usually finds the first 2 files and I get a 216 error for the
macro files, because it doesn't exist (I haven't created any macros yest). This
is ok, because I have been using it like this for a while. Now since I put it
in the ramdrive, I get the "unable to link to macro "error. It seesm to me that
this is a module of some sort that it is looking for in memory (which it
probably yanked out of /h0/cmds, before), and now it can't find i it. But after
doing an mdir, while it is running, the only osterm related module in memory is
osterm itself. I'll try to get in touch with Vaughn.

TC

There is 1 Reply.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.