alanh@logitek.co.uk (Alan Hourihane) (03/13/91)
Hi, I have a problem, Using PC-Xview/16 and the Generic version of PC/TCP v2.05, with the Clarkson packet drivers for the 3C503 board work fine. 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. I am using the same IPCUST.SYS and IFCUST.SYS for both configurations. Any ideas, is there a bug in the NDIS to Packet Driver converter. Alan Hourihane email: alanh@logitek.co.uk
ian@unipalm.uucp (Ian Phillipps) (03/19/91)
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