#: 5417 S10/Tandy CoCo
    21-Jul-90  11:54:47
Sb: #5335-Basic09
Fm: Jim Peasley 72726,1153
To: Kevin Darling (UG Pres) 76703,4227

Kev;

  You were right on about the gfx2/syscall/inkey thing... I remerged them so
that the first module is the same as the name, and things are working fine now.
On reflection, it makes sense that if a Basic09 program makes a call to say,
SysCall, finds a merged set of modules named syscall in CMDS, and upon loading
it, finds that the first pgm. i.d. is something other than what it's looking
for, an error 43 would be generated.  Simple with hindsight. :-)

  As far as the apparent problem with View goes,nthe only thing that had
changed was the pre-loading of the above 3 modules, and I just don't see how
that would affect paths.  ???   Hafta do some more detective work.

(2 days later) Both View and MemberDir woHk fine now... no more flakiness.
Original question still remains - why would pre-loading gfx2/inkey/syscall
cause a paths error?  I don't see any relationship here.    Anybody??


  Thanks,
    ...Jim