CNTRL.EXE: Difference between revisions
Created page with "It controls the stack for TCP/IP. TCP/IP Stack processing. CNTRL.EXE is a very important component of the stack. CNTRL.EXE provides threads for proper running of the stack. It..." |
No edit summary |
||
| Line 1: | Line 1: | ||
It controls the stack for TCP/IP. TCP/IP Stack processing. CNTRL.EXE is a very important component of the stack. CNTRL.EXE provides threads for proper running of the stack. It provides a thread for each of the following: | It controls the stack for TCP/IP. TCP/IP Stack processing. CNTRL.EXE is a very important component of the stack. CNTRL.EXE provides threads for proper running of the stack. It provides a thread for each of the following: | ||
* IP input processing | |||
* TCP slow timeout processing | |||
* Debug thread for IP | |||
* ARP timeout processing | |||
* Ifndis debug thread | |||
* Watchdog thread for the adapter status | |||
* Loopback IP packets processing | |||
CNTRL.EXE is normally started from CONFIG.SYS with a RUN=statement. It should be the first program to begin executing when TCP/IP is started. CNTRL.EXE for Version 4 is different from that in the Version 2.0 stack | |||
==Versions== | ==Versions== | ||
Revision as of 16:52, 21 July 2015
It controls the stack for TCP/IP. TCP/IP Stack processing. CNTRL.EXE is a very important component of the stack. CNTRL.EXE provides threads for proper running of the stack. It provides a thread for each of the following:
- IP input processing
- TCP slow timeout processing
- Debug thread for IP
- ARP timeout processing
- Ifndis debug thread
- Watchdog thread for the adapter status
- Loopback IP packets processing
CNTRL.EXE is normally started from CONFIG.SYS with a RUN=statement. It should be the first program to begin executing when TCP/IP is started. CNTRL.EXE for Version 4 is different from that in the Version 2.0 stack