pf@lda.leissner.se (Peter Fassberg) (05/04/91)
> We use D-link's DE-100 (ne1000 clone) and DE-150 (3c501 clone) cards. > LanSmart runs fine ON ITS OWN, and CUTCP is happy with the relevant > packet drivers, in the absence of LanSmart. Does the s/w interface > btw LanSmart and the D-link drivers allow intervention, in the manner > of BYU's IPXPKT solution? LanSmart does not seem to know about packet > drivers, and the NetBios packet driver solution is inapplicable, as we > use CUTE/CUTCP to talk to non-DOS machines. No problem. Almost ... The only problem is that there is two versions of DE100 cards. The old version has serial number beginning with "EX 0" (Ethernet addr. 00:de:01) and the newer has serial numbers "EX 1" (Eth. addr. 00:80:c8). Seems that DATEX Inc. has a new chip-vendor ... For the older ones you must have a special driver called "DE100.EXE" and a special packet driver "DE100FTP". These programs comes with a special version of PC/TCP for D-Link. DE100 requires no argument. DE100FTP requires only the packet interrupt number. For the newer you must have av packet driver called "DE100PD.COM" and a driver for LanSMART called "LANSMAPD.EXE". The name "DE100PD.COM" is the same as the driver from the Clarkson collection, but it is not the same program ! Clarkson's driver cannot coexist with LanSMART. Those programs comes with Datex' own TCP/IP (LOCUS). I have used both the old and the new cards with PC/TCP+, NCSA and CUTCP. -- Peter Fassberg Internet: pf@leissner.se Leissner Data AB UUCP: ...!uunet!leissner.se!pf P.O. Box 912 S-461 29 TROLLHATTAN SWEDEN