Talk:PC/TCP Packet Driver

rudimentary/inefficient article
– it is NOT a TCP/IP stack, but a NIC driver oriented mostly towards TCP/IP (!) – you need a regular TCP/IP stack to use this, eg. XFS or mTCP — Preceding unsigned comment added by 77.8.83.5 (talk) 16:43, 8 March 2024 (UTC)

Re: "[clarification needed - techspeak, relevance?]"
I think the fact of how it scans dynamically for the interrupt to use is interesting and notable. It reflects the difficulty of the common use of interrupts in the MS-DOS world combined with the lack of a central authority to allocate them, and it is an ingenious solution to that problem. In terms of the complaint that it is "techspeak", one needs a fair amount of technical background to appreciate this, but this is probably not the right article to give that background. A discussion of this problem, and this and other attempts to work around it, and why it doesn't occur so much with more modern operating systems (like Windows or Linux) should probably go in another article.60.225.114.230 (talk) 07:37, 2 April 2012 (UTC)

Drivers section
I removed this section because it was very poorly written and was largely just a random list of some packet drivers. —99.99.216.248 (talk) 22:27, 4 January 2013 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on PC/TCP Packet Driver. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20110912002938/http://www.ccworld.co.uk/images/ne1000.jpg to http://www.ccworld.co.uk/images/ne1000.jpg

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 23:10, 23 May 2017 (UTC)