DOS ain't dead - ActionTec PCMCIA FastNet Plus PE1500 DOS driver needed

RayeR

CZ,
26.09.2015, 13:57

ActionTec PCMCIA FastNet Plus PE1500 DOS driver needed (Users)

Hi,
I got this PCMCIA network adapter
http://rayer.g6.cz/1tmp/asekol4.jpg
and I'm looking for usable packet/odi driver for DOS. I googled hard and found in archives only drivers for Pro PE2000 and PE200 that doesn't work. I found only Windows driver for PE1500 that consist of TX100NDS.SYS and OEM7.INF. This driver works fine under Win98.
Maybe someone luckily have/had this card and may have a driver diskette somewhere, plaease look for that if so...

---
DOS gives me freedom to unlimited HW access.

bearwindows missing nowhere, 26.09.2015, 18:25 @ RayeR	ActionTec PCMCIA FastNet Plus PE1500 DOS driver needed Post reply
	This one? http://www.wou.edu/~bwitt/SMC%20PCMCIA%20Ethernet%20Card/ http://bama.ua.edu/~recovery/Files/Drivers/SMC%20PCMCIA%20Driver/ http://ifsc2.ifsc.usp.br/drivers/LAN/PCMCIA/TRUST/ IF not, try search internet for "TX100NDS.SYS" Hope this helps. :)

RayeR

CZ,
29.09.2015, 23:43

@ bearwindows

ActionTec PCMCIA FastNet Plus PE1500 DOS driver needed

Post reply

> This one?
> http://www.wou.edu/~bwitt/SMC%20PCMCIA%20Ethernet%20Card/
> http://bama.ua.edu/~recovery/Files/Drivers/SMC%20PCMCIA%20Driver/
> http://ifsc2.ifsc.usp.br/drivers/LAN/PCMCIA/TRUST/
> IF not, try search internet for "TX100NDS.SYS"
> Hope this helps. :)

Thanks, you're my hero! :)
I found, that there was not problem in packet driver itself but PCMCIA enabler (a real mess of various manufacturers under DOS). I found that if I load packet driver for ActionTec PE200 under Win98 where I pass args of IQR and port acquired from devmgr then the driver loads OK displaying right MAC. But not under DOS with same args. Then I tried enabler (lanen.exe, 11483B) from your link and voala, packet driver loaded successfully. landiag also passed. So I uplpoaded doslinks on this old Toshiba Sattelite 470CDT and kicked up the network connection and just sending this post. Hope it doesn't crash :)

---
DOS gives me freedom to unlimited HW access.

RayeR

CZ,
30.09.2015, 11:40

@ RayeR

ActionTec FastNet Plus in HP 200LX using mTCP problem

Post reply

So when I tested the eth. card is working I got an idea to push it into ancient wonderfull HP 200LX (PC XT) handheld (it has one PCMCIA and people used it with some modem and ethernet cards). I found alternative OpenSOurce enabler LXCIC.COM and packet driver LXEN2216.COM specially made for 200LX. The driver loaded OK and reported the right MAC.
C:\LXCIC\LXCIC.COM /l LXCIC v2.1 (c) 99 Stefan Peichl, Heidelberg ------------------------------------------- Fast Ethernet ADR=0300 COR=45 FCSR=na BASE=01E0 ID=06 active loaded resident Card powered C:\LXCIC\LXEN2216.COM 0x60 HP200LX packet driver for EN2216, version 11.1.3 Packet driver skeleton copyright 1988-93, Crynwr Software. This program is freely copyable; source must be available; NO WARRANTY. See the file COPYING.DOC for details; send FAX to +1-315-268-9201 for a copy. Packet driver software interrupt is 0x60 (96) My Ethernet address is 00:B1:47:23:17:6B

Then I use LXTCP and latest mTCP to run DHCP and some TCP tools but it failed to connect DHCP. Even If I write IP addresses into config file manually utilities doesn't work, e.g. ping timeouted...
C:\MTCP\dhcp mTCP DHCP Client by M Brutman (mbbrutman^gmail.com) (C)opyright 2008-2015 Version: Jul 5 2015 Timeout per request: 10 seconds, Retry attempts: 3 Sending DHCP requests, Press [ESC] to abort. DHCP request sent, attempt 1: Timeout DHCP request sent, attempt 2: Timeout DHCP request sent, attempt 3: Timeout Error: Your Ethernet card reported an error for every packet we sent. Check your cabling and packet driver settings.

But driver seems to be detected by mTCP and there are some received and sent packets but lot of them is lost
C:\MTCP\pkttool scan mTCP pkttool by M Brutman (mbbrutman^gmail.com) (C)opyright 2008-2015 Version: Jul 5 2015 Scanning: Details for driver at software interrupt: 0x60 Name: EN2216 Entry point: 066F:0382 Version: 11 Class: 1 Type: 65480 Interface Number: 0 Function flag: 2 (basic and extended functions) Current receive mode: packets for this MAC and broadcast packets MAC address: 00:B1:47:23:17:6B C:\MTCP\pkttool stats 0x60 mTCP pkttool by M Brutman (mbbrutman^gmail.com) (C)opyright 2008-2015 Version: Jul 5 2015 Details for driver at software interrupt: 0x60 Name: EN2216 Entry point: 066F:0382 Version: 11 Class: 1 Type: 65480 Interface Number: 0 Function flag: 2 (basic and extended functions) Current receive mode: packets for this MAC and broadcast packets MAC address: 00:B1:47:23:17:6B All statistics are from when the packet driver was loaded. Packets in: 157 Packets received Packets out: 55 Packets sent Bytes in: 5065 Bytes received (includes Ethernet headers) Bytes out: 3300 Bytes sent (includes Ethernet headers) Errors in: 0 Receive errors Errors out: 0 Sending errors Packets lost: 2463 Lost due to no packet handler, out of buffers, etc.

When I run pkttool sniffer listen mode I can see
C:\MTCP\pkttool listen 0x60 -v mTCP pkttool by M Brutman (mbbrutman^gmail.com) (C)opyright 2008-2015 Version: Jul 5 2015 Details for driver at software interrupt: 0x60 Name: EN2216 Entry point: 066F:0382 Version: 11 Class: 1 Type: 65480 Interface Number: 0 Function flag: 2 (basic and extended functions) Current receive mode: packets for this MAC and broadcast packets MAC address: 00:B1:47:23:17:6B Listening for incoming packets. Press [ESC] to quit. 04:33:35.80 To: FF:FF:FF:FF:FF:FF From: FF:FF:FF:FF:FF:01 Len: 29 Type: 0001 04:33:36.24 To: FF:FF:FF:FF:FF:FF From: FF:FF:FF:FF:FF:01 Len: 29 Type: 0001 04:33:36.35 To: FF:FF:FF:FF:FF:FF From: FF:FF:FF:FF:FF:01 Len: 29 Type: 0001 ... 04:33:39.42 To: FF:FF:FF:FF:FF:FF From: FF:FF:FF:FF:FF:01 Len: 285 Type: 0001 04:33:39.42 To: FF:FF:FF:FF:FF:FF From: FF:FF:FF:FF:FF:01 Len: 29 Type: 0001 ... Tracing active for 0 minutes, 8 seconds Packets received: 36 Packets dropped: 0 Ethernet broadcast packets: 36 Unique MACs detected: 1 MAC addr: FF:FF:FF:FF:FF:01 Packets sent: 36 Bytes sent: 1556 Packets: 36 Bytes: 1556 Type: ---- (IEEE 802.3 packet) All hosts combined: Packets sent: 36 Bytes sent: 1556 Packets: 36 Bytes: 1556 Type: ---- (IEEE 802.3 packet) MAC addresses and their possible IP addresses (based on ARP traffic):

and raw
C:\MTCP\pkttool listen 0x60 -raw mTCP pkttool by M Brutman (mbbrutman^gmail.com) (C)opyright 2008-2015 Version: Jul 5 2015 Details for driver at software interrupt: 0x60 Name: EN2216 Entry point: 066F:0382 Version: 11 Class: 1 Type: 65480 Interface Number: 0 Function flag: 2 (basic and extended functions) Current receive mode: packets for this MAC and broadcast packets MAC address: 00:B1:47:23:17:6B Listening for incoming packets. Press [ESC] to quit. 0000 FF FF FF FF FF FF FF FF FF FF FF 01 00 01 00 31 ...............1 0010 5C 31 5C 6E 46 6E 46 06 08 06 08 01 00 \1\nFnF...... 0000 FF FF FF FF FF FF FF FF FF FF FF 01 00 01 00 31 ...............1 0010 5C 31 5C 6E 46 6E 46 06 08 06 08 01 00 \1\nFnF...... ... 0000 FF FF FF FF FF FF FF FF FF FF FF 01 00 01 00 31 ...............1 0010 5C 31 5C 6E 46 6E 46 00 08 00 08 00 45 00 45 48 \1\nFnF.....E.EH 0020 01 48 01 7B 1F 7B 1F 00 00 00 00 11 40 11 40 9C .H.{.{......@.@. 0030 EF 9C EF 8D 0A 8D 0A 01 60 01 60 FF FF FF FF FF ........`.`..... 0040 FF FF FF 43 00 43 00 44 00 44 00 34 01 34 01 F7 ...C.C.D.D.4.4.. 0050 DE F7 DE 01 02 01 02 01 06 01 06 9A 70 9A 70 75 ............p.pu 0060 7E 75 7E 00 00 00 00 00 00 00 00 00 00 00 00 00 ~u~............. 0070 00 00 00 66 4E 66 4E B6 34 B6 34 2E D5 2E D5 AE ...fNfN.4.4..... 0080 AC AE AC 8D 0A 8D 0A 01 60 01 60 46 50 46 50 BD ........`.`FPFP. 0090 5D BD 5D 69 E4 69 E4 00 00 00 00 00 00 00 00 00 ].]i.i.......... 00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0110 00 00 00 00 00 00 00 00 00 00 00 00 00 ............. 0000 FF FF FF FF FF FF FF FF FF FF FF 01 00 01 00 31 ...............1 0010 5C 31 5C 6E 46 6E 46 06 08 06 08 01 00 \1\nFnF...... ... Tracing active for 0 minutes, 17 seconds Packets received: 87 Packets dropped: 0 Ethernet broadcast packets: 87 Unique MACs detected: 1 MAC addr: FF:FF:FF:FF:FF:01 Packets sent: 87 Bytes sent: 2779 Packets: 87 Bytes: 2779 Type: ---- (IEEE 802.3 packet) All hosts combined: Packets sent: 87 Bytes sent: 2779 Packets: 87 Bytes: 2779 Type: ---- (IEEE 802.3 packet) MAC addresses and their possible IP addresses (based on ARP traffic):

If I copy my mTCP setup to the old Toshiba NTB mentioned above and run enabler suggested by BW and packet driver for PE200 (this driver and enabler don't work on 200LX) it runs fine, even there are also lost packets it got address from DHCP within 1 second and all tools worked as expected.
Only one minor issue was that mTCP complained about DHCP lease time was less than 3600 (was 3200) so I have to manually edit tcp.cfg to increase the lease time. I would rather display only a warning than stop the functionality but maybe it can be configured too.

Do you see what is the problem? Should I try to play with MTU size or what else? Anybody experienced networking on HP 200LX here?

---
DOS gives me freedom to unlimited HW access.

mbbrutman

Washington, USA,
16.10.2015, 03:43

@ RayeR

ActionTec FastNet Plus in HP 200LX using mTCP problem

Post reply

Just for giggles please try to use software interrupt 0x66 instead of software interrupt 0x60. It should not matter, but every usage of the LXEN2216 driver shows it using 0x66. (Don't forget to update the mTCP configuration file too.)

This setup is known to work with mTCP, or at least it did at one time:

http://www.vintage-computer.com/vcforum/archive/index.php/t-38300.html

Does anybody have the source code for this driver? It's based on the Crynwr framework so source code is supposed to be available, but I have not found it yet. Seeing the return codes in the packet driver source code would be nice.

---
mTCP - TCP/IP apps for vintage DOS machines!
http://www.brutman.com/mTCP

RayeR

CZ,
16.10.2015, 20:20

@ mbbrutman

ActionTec FastNet Plus in HP 200LX using mTCP problem

Post reply

> Does anybody have the source code for this driver? It's based on the
> Crynwr framework so source code is supposed to be available, but I have not
> found it yet. Seeing the return codes in the packet driver source code
> would be nice.

Sources are here
http://sourceforge.net/projects/rwhitby/files/HP200LX%20Ethernet%20Drivers/1.0/
http://hplx.pgdn.de/lxcic.zip

---
DOS gives me freedom to unlimited HW access.

mbbrutman

Washington, USA,
17.10.2015, 08:24

@ RayeR

ActionTec FastNet Plus in HP 200LX using mTCP problem

Post reply

Just updating everybody else on the debugging that has been happening in private:

The incoming packets do not look to be valid. mTCP gets an error from the packet driver every time it tries to send a packet. I strongly suspect that the Ethernet card is bad.

I've asked RayeR to try one of the 16 bit WatTCP based programs as an experiment. If anything can work with the card then I know I have a problem with mTCP, but I also know that mTCP has worked with this combination before.

RayeR

CZ,
28.10.2015, 00:52

@ mbbrutman

ActionTec FastNet Plus in HP 200LX using mTCP problem

Post reply

> I've asked RayeR to try one of the 16 bit WatTCP based programs as an
> experiment. If anything can work with the card then I know I have a
> problem with mTCP, but I also know that mTCP has worked with this
> combination before.

I tried with an old 16b wattcp from 1992 and lxtcp packages but it doesn't work. Neither with manual IP config neither via DHCP. Ping or other program just timeouts. Only what works is displaying MAC address by TCPINFO. There's no diagnostic tool like pktool. So maybe the ethernet card is not fully compatible with the packet driver or some IRQ problem? I cannot specify IRQ as parameter for driver it's probably hardwired in HP 200LX and in code). But in that case I would expect that any packet would arrive not damaged ones...

---
DOS gives me freedom to unlimited HW access.