home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.ibm.pc.misc
- Path: sparky!uunet!utcsri!utgpu!georgen
- From: georgen@gpu.utcs.utoronto.ca (G. Ng)
- Subject: Problem: packet driven NCSA Telnet, Windows3, & MSWord-DOS
- Message-ID: <BtpGCo.H8L@gpu.utcs.utoronto.ca>
- Organization: University of Toronto Computing Services
- Date: Fri, 28 Aug 1992 17:53:12 GMT
- Lines: 31
-
- I'm having a problem getting a NCSA Telnet (v2.3.03) using a 3com 3c503
- packet driver (v9.4.0), Windows 3.0, and MS Word (DOS) working on the
- same 486 running DOS 5.
-
- It seems to stem from a problem with the packet driver and using an
- interrupt number of either 3 or 5, conflicting with DOS5's emm386.exe
- driver. Telnet works, and I believe Word works, but Windows crashes.
-
- When I change the interrupt number to 2 or 4 (or almost anything other
- than 3 or 5), Windows (and Word) works, but Telnet gives a 'wrong ioaddr'
- message and exits.
-
- Then, when I replace emm386.exe with Window's emm386.sys, telnet works,
- but Windows and/or Word sometimes crashes.
-
- Can anyone tell me what's going on here? Is it because the packet driver's
- interrupts are incompatible with that of Windows (and perhaps Word), or
- is it being allocated inappropriately in memory, or should I be using
- something else other than emm386.*, or is something else going on here?
-
- I'm not a PC-techie, so please excuse my ignorance and probable
- misusage of PC terms.
-
- Any help at all would be appreciated, preferably through email since I
- don't read this newsgroup often.
-
- thanks in advance,
- gn
- --
- georgen@resunix.ri.sickkids.on.ca (NeXTMail ok)
- molecular genetics, hospital for sick children
-