[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Part01 - Part02 - Part03 - Part04 - Part05 - Part06 - Part07 - Part08 - Part09 - Part10 - Part11 - Part12 - Part13 - Part14 - Single Page
Top Document: Win95 FAQ Part 8 of 14: Dial-up Networking
Previous Document: 8.11. How can I track time and costs for my dial-up connection?
Next Document: 8.13. How do I write a dial-up script?
-
Search the FAQ Archives
Part01 - Part02 - Part03 - Part04 - Part05 - Part06 - Part07 - Part08 - Part09 - Part10 - Part11 - Part12 - Part13 - Part14 - Single Page
Top Document: Win95 FAQ Part 8 of 14: Dial-up Networking
Previous Document: 8.11. How can I track time and costs for my dial-up connection?
Next Document: 8.13. How do I write a dial-up script?
8.12. How can I get dial-up networking to work with a null modem cable?
MS didn't include a null modem driver for the Telephony Interface (TAPI). However, check out this bogus MODEM.INF file, which serves the purpose. One installed, you can treat the null modem like any other modem in Win95. NOTE: Windows 98 and NT 4.0 include descriptors for null modem cables already.
Top Document: Win95 FAQ Part 8 of 14: Dial-up Networking
Previous Document: 8.11. How can I track time and costs for my dial-up connection?
Next Document: 8.13. How do I write a dial-up script?
Part01 - Part02 - Part03 - Part04 - Part05 - Part06 - Part07 - Part08 - Part09 - Part10 - Part11 - Part12 - Part13 - Part14 - Single Page
[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
gordonf@intouch.bc.ca
Last Update October 13 2008 @ 00:13 AM