Thread View: comp.databases.xbase.fox
4 messages
4 total messages
Started by Eamon Daly
Wed, 29 Mar 1995 00:00
Console LockUp in FoxPro for UNIX
Author: Eamon Daly
Date: Wed, 29 Mar 1995 00:00
Date: Wed, 29 Mar 1995 00:00
17 lines
1422 bytes
1422 bytes
We have a foxpro program which loops continuously,
checking for the presence of input files in a
certain directory. Unfortunately, the program
locks out the function keys occasionally so that
switching between ttys on the console is
impossible.
Has anyone had this problem? We've tried using the
-i and -o options so that the terminal is treated
as a serial terminal, but the program runs so slow
in this mode that we're deathly afraid of using it
all of the time.
--
"does the fun ever start?" -kelly gillen
<URL:http://acs2.bu.edu:3000/>
bacon number: 3
Re: Console LockUp in FoxPro for UNIX
Author: Mark Davis
Date: Wed, 29 Mar 1995 00:00
Date: Wed, 29 Mar 1995 00:00
27 lines
2026 bytes
2026 bytes
vampyr@bu.edu (Eamon Daly) writes: >We have a foxpro program which loops continuously, >checking for the presence of input files in a >certain directory. Unfortunately, the program >locks out the function keys occasionally so that >switching between ttys on the console is >impossible. If you have an application which loops continuously, running under Unix (even in Foxpro), I would consider the program broken.... Try to get the loop removed, it is a waste of valuable CPU time. >Has anyone had this problem? We've tried using the >-i and -o options so that the terminal is treated >as a serial terminal, but the program runs so slow >in this mode that we're deathly afraid of using it >all of the time. It should not be much slower..... at least, it is not using any additional CPU time doing it as a serial terminal, so I wouldn't worry about it too much. I would worry more about getting the loop removed! -- /--------------------------------------------------------------------------\ | Mark A. Davis | Lake Taylor Hospital | Norfolk,VA (804)-461-5001x431 | | Director/SysAdmin | Information Systems | mark@taylor.infi.net | \--------------------------------------------------------------------------/
Re: Console LockUp in FoxPro for UNIX
Author: Timothy D. Kuehn
Date: Thu, 30 Mar 1995 03:03
Date: Thu, 30 Mar 1995 03:03
15 lines
1554 bytes
1554 bytes
In article <1995Mar29.220157.23800@taylor.infi.net>, Mark Davis <mark@taylor.infi.net> wrote: >vampyr@bu.edu (Eamon Daly) writes: >>We have a foxpro program which loops continuously, problem #1 >If you have an application which loops continuously, running under Unix >(even in Foxpro), I would consider the program broken.... Try to get the >loop removed, it is a waste of valuable CPU time. Much better to use inkey(1) to pause 1 second between looks. Much easier on CPU time. :) Tim Kuehn
Re: Console LockUp in FoxPro for UNIX
Author: Scott Michel
Date: Fri, 31 Mar 1995 00:00
Date: Fri, 31 Mar 1995 00:00
23 lines
1826 bytes
1826 bytes
Mark Davis (mark@taylor.infi.net) wrote: : vampyr@bu.edu (Eamon Daly) writes: : >We have a foxpro program which loops continuously, : >checking for the presence of input files in a : >certain directory. Unfortunately, the program : >locks out the function keys occasionally so that : >switching between ttys on the console is : >impossible. : If you have an application which loops continuously, running under Unix : (even in Foxpro), I would consider the program broken.... Try to get the : loop removed, it is a waste of valuable CPU time. I'd definitely concur there -- this works well under DOS, but not under Unix. There's some spoofing you could do with the terminal driver and termio ioctl() calls, but for some reason I doubt you can access them from inside FoxPro. Basically, I'm guess you're sitting waiting for the next keystroke and attempting to do some work procedure while there isn't one? -scottm
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads