PC/TCP Packet Driver
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "PC/TCP Packet Driver" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|PC/TCP Packet Driver|concern=Fails [[WP:NSOFT]]}} ~~~~ Timestamp: 20250317221601 22:16, 17 March 2025 (UTC) Administrators: delete |
PC/TCP Packet Driver is a networking API for MS-DOS, PC DOS, and later x86 DOS implementations such as DR-DOS, FreeDOS, etc. It implements the lowest levels of a TCP/IP stack, where the remainder is typically implemented either by terminate-and-stay-resident drivers or as a library linked into an application program. It was invented in 1983 at MIT's Lab for Computer Science (CSR/CSC group under Jerry Saltzer and David D. Clark), and was commercialized in 1986 by FTP Software.
A packet driver uses an x86 interrupt number (INT) between 60h .. 80h. The number used is detected at runtime, it is most commonly 60h but may be changed to avoid application programs which use fixed interrupts for internal communications. The interrupt vector is used as a pointer (4-bytes little endian) to the address of a possible interrupt handler. If the null-terminated ASCII text string "PKT DRVR" is found within the first 12-bytes -- more specifically in bytes 3 through 11 -- immediately following the entry point then a driver has been located.[1]
Packet drivers can implement many different network interfaces, including Ethernet, Token Ring, RS-232, Arcnet, and X.25.[2]
Functions
Function | AH(Dec) | Category |
---|---|---|
driver_info | 1 | Basic |
access_type | 2 | |
release_type | 3 | |
send_pkt | 4 | |
terminate | 5 | |
get_address | 6 | |
reset_interface | 7 | |
get_parameters | 10 | High-performance packet driver |
as_send_pkt | 11 | |
set_rcv_mode | 20 | Extended packet driver |
get_rcv_mode | 21 | |
set_multicast_list | 22 | |
get_multicast_list | 23 | |
get_statistics | 24 | |
set_address | 25 |
Drivers
WinPKT is a driver that enables use of packet drivers under Microsoft Windows that moves around applications in memory.[3]
W3C507 is a DLL to packet driver for the Microsoft Windows environment.
Support for Ethernet alike network interface over Serial line IP (using 8250 UART), CSLIP, Parallel line IP, IPX, Token Ring, LocalTalk, ARCNET.
See also
- Crynwr Collection - alternative free packet driver collection
- Network Driver Interface Specification (NDIS) - developed by Microsoft and 3Com, free wrappers
- Open Data-Link Interface (ODI) - developed by Apple and Novell
- Universal Network Device Interface (UNDI) - used by Intel PXE
- Uniform Driver Interface (UDI) - defunct
- Preboot Execution Environment - network boot by Intel, widespread
References
- ^ "PC/TCP Version 1.09 Packet Driver Specification". FTP Software, Inc. September 14, 1989. Retrieved 2023-02-22.
- ^ "PC/TCP Packet Driver Specification". Archived from the original on November 27, 2022. crynwr.com
- ^ winpkt/winpkt.asm
Further reading
- Petrosky, Mary (5 September 1988). "Banyan seals deal with FTP for TCP/IP support: PC/TCP will work with VINES-supported nets". Network World. Vol. 5, no. 36. IDG. pp. 2, 4. ISSN 0887-7661.
- Derfler, Frank J., Jr. (July 1992). "TCP/IP packages for NetWare 3.11: Using the Alphabet Soup". PC Magazine. Vol. 11, no. 13. Ziff Davis. pp. 415, 417, 419, 420, 423, 425, 426, 438, 441. ISSN 0888-8507.
{{cite magazine}}
: CS1 maint: multiple names: authors list (link) - "Reviews/Product comparison, PC/TCP for OS/2 Version 1.3". InfoWorld. Vol. 16, no. 37. IDG. 12 September 1994. p. 86. ISSN 0199-6649.