mshiels@watmath.waterloo.edu (Michael A. Shiels) (04/12/88)
Does anyone know what the procedures are for using WINDOWS in an interrupt driver communications system. (NOT ASYNC) but a TCP/IP over ETHERNET!!! I have to have the ethernet card interrupt driven?? Any ideas? experiences?? -- Michael A. Shiels (MaS Network Software) mshiels@watmath.waterloo.EDU UUCP: ...path...!watmath!mshiels
jbvb@VAX.FTP.COM (James Van Bokkelen) (04/15/88)
Making the TCP/IP event-driven (packet interrupts and clock ticks) is the first required step. Making it sharable between multiple programs is also useful. These are two of the reasons we moved the TCP/IP into a separate terminate & stay resident module for our 2.0 release. If you're starting with something like PC/IP, you've got a lot of work to do, because it makes the basic assumption that the tasker is always running. Windows doesn't time-slice unless the application participates in its message-passing paradigm, so a standard application gets stopped dead when another window becomes active. James VanBokkelen FTP Software Inc.