Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uunet!mcsun!ukc!acorn!unipalm!ian
From: ian@unipalm.uucp (Ian Phillipps)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: PC/TCP Generic & PC-Xview/16
Message-ID: <1991Mar18.183702.20676@unipalm.uucp>
Date: 18 Mar 91 18:37:02 GMT
Article-I.D.: unipalm.1991Mar18.183702.20676
References: <alanh.668865698@krypton>
Distribution: comp
Organization: Unipalm Ltd., Cambridge, England
Lines: 21

alanh@logitek.co.uk (Alan Hourihane) writes:

>	But, when using PC-Xview/16 and the Generic version of PC/TCP v2.05
>with the NDIS to Packet Driver Converter v1.05, using any of the options
>to start PC-Xview/16 fails, it looks as though when PC-Xview tries to start
>the Kernel goes to sleep and PC-Xview doesn't get a response and fails with
>unknown host(xxxxx) or unknown host(xxx.xxx.xxx.xxx) if you specify an 
>internet address.

There is a clash between the default software interrupt used by the NDIS and
that used by PC-Xview. The easiest way is to change your protocol.ini:

[PKTDRV]
  DRIVERNAME = PKTDRV
  BINDINGS = ETHERLINKII		- or whatever
  INTVEC = 0X60

The interrupt vector 0x60 is usually free: if not, choose another one, but
not 0x61, which is used by the PC/TCP kernel.

Ian Phillipps, Unipalm