#: 5333 S10/Tandy CoCo
    19-Jul-90  01:36:45
Sb: #Basic09
Fm: Jim Peasley 72726,1153
To: Kevin Darling 76703,42

Kevin;

  Help!  I'm not understanding what's happening here!

I've started running MemberDir after capturing the latest messages, and for
some reason, it won't pick up Syscall.  I've got copies of gfx2, Inkey, and
Syscall with all 3 merged into each, bul not RunB.  How come the system won't
pick up Syscall from a packed procedure?  Everything is fine if I pre-load the
3 modules.

  Now for the _really_ strange part... after running MemberDir, and with the 3
modules still in memory, if I try to reply to a message using View, it bombs
out when trying to save the reply with an error 201 - illegal path #. Do you
have any ideas why this is happening??  All the other file I/O functions in
View work O.K. except for the reply path... and this works O.K. if I don't
preload the gfx2, etc. modules.  ??? %-<

  ...Jim

There is 1 Reply.