error, or spurious error

Mike Schwartz mschw at athenet.net
Tue Jan 26 18:46:42 PST 2010


> > I'm running an xterm under kde 3.5 on OSR 6. My filePro is 5.6.10D4.
> >
> > Trying 'p' or 'dclerk' errors out with:
> >
> > 	*** A filePro Error Has Occurred ***
> >
> > 	Cannot run:
> >
> > 	Entry: cm
> >
> > 	On File: /appl/fp/lib/config
> >
> > 	Required terminal feature not available.
> >
> > If there's a termcap error, why is the 'config' file being blamed?
> >
> > I've copied the linux and xterm entries from the 5.6.10D4/termcap
> file
> > into an fp4.8/termcap file, and when connecting via ssh from
> > an xterm to
> > that fp4.8 machine, I see no such filePro error.
> >
> > --
> > JP

     Hmmm...   I noticed that same exact error message yesterday when I was
testing the Putty terminal emulator on a freshly installed SCO Openserver
6.0 system running filepro 5.6.10.  Facetwin and Anzio terminal emulators
installed and ran just fine, but I needed to access the server from a
Windows workstation that had only Putty installed.

     I tried various terminal emulations on the Putty, and was finally able
to get it working well enough to finish licensing the Facetwin, although I
never did get the graphics looking well enough on Putty to pull up the
filePro menu and look at a few things in filePro.

     Every time I tried some combination of settings in Putty that filePro
didn't like, I got that message.

     I didn't think to copy the linux and xterm entries into the filepro
termcap.  I thought filePro would take care of filling in any missing
termcap entries as I played with different "TERM=" settings in the shell.

Mike Schwartz  



More information about the Filepro-list mailing list