INtime® 3.1 Software - tenAsys

Appendix G: Troubleshooting
Table G-2. Solution table
Category
Running
INtime
applications
Running
INtime
applications
(continued)
Solution
15 Run the INtime Explorer to obtain debug information.
For information about running the INtime Explorer, see After you start the
INtime kernel in Chapter 9, Operation.
16 Set the RT kernel tick interval above 200usec.
When the kernel tick drops below this rate, Windows slows down because
the CPU devotes too much time to switching between the Windows and
INtime kernels.
17 Ensure that the INtime I/O Service is running.
INtime applications that perform terminal I/O require that the INtime I/O
Service runs. For information about starting this service, see Starting the RT
kernel and related components in Chapter 9, Operation.
18 End the INtime application:
1. Invoke the INtime Explorer (Start>All Programs>INtime>INtime
Explorer).
2. Highlight the INtime application you want to terminate.
3. Right click the mouse. A pulldown menu displays.
4. Select Delete. INtex prompts you to confim the deletion process.
5. Select Yes.
If you cannot display the INtime Explorer (i.e., the Windows screen seems
frozen and the mouse does not respond), the INtime application may have
halted or may be monopolizing system resources. If you suspect the latter, see
solution 19.
Note:
• To verify whether Windows has halted, try to access the file system from
another system. If you can, Windows is still running but cannot respond.
• Ensure that you wait for at least ten seconds, in case the Spin Doctor
detects a spinning thread.
19 Adjust your INtime application so that the RT portion of your INtime
applications do not dominate CPU time.
Your INtime application may be designed to monopolize too many system
resources. For more information about designing applications to balance RT
and Windows activity, see Methodology in Chapter 5, Designing
RT applications.
Note: To aid in diagnosing system resource misuse, try to access the file
system from another system. If you can, Windows is still running but cannot
respond.
20 Exit INtime applications, if possible, then reboot your system:
One of these situations may have occured:
• Windows halted.
• A Windows application halted.
• An INtime application monopolized system resources.
Note: Try other solutions before trying this one.
183