DOS IPX Networking [Solved] \ VOGONS

DOS IPX Networking [Solved]

Topic actions

Post a reply

First post, by w0lf42

Posted on 2019-01-18, 05:34

w0lf42 Offline

Rank Newbie

Rank: Newbie
Posts: 80
Joined: 2018-07-26, 04:20

Greetings. I'm hoping that someone can assist me. I'm attempting to get IPX drivers working in DOS. Any help would be greatly appreciated.

Hardware

Network Card: Linksys EtherFast PCI 10/100 Adapter (LNE100TX)
Motherboard: DFI CA64 REV.A1 SOCKET 370 VIA Apollo Pro133A

If necessary, I am willing to replace my NIC as long as it will work in Windows 98SE.

In the manual is says

Insert the EtherFast® 10/100 LAN Card Driver Disk into you CD-ROM. Enter the appropriate commands after the following prompts: • […]
Show full quote
Insert the EtherFast® 10/100 LAN Card Driver Disk into you CD-ROM. Enter the
appropriate commands after the following prompts:
• When “C:\>” appears, type “a:” then press Enter.
• When “D:\>” appears, type “cd diag” then press Enter.
• When “D:\diag>” appears, type “diag” then press Enter.
You can also copy the software to your local (c:\) drive and run DIAG from your hard disk.

The Fast Ethernet Diagnostics Program will appear, providing a display of
the Card’s basic information (Ethernet Address, IRQ, I/O Port and Media
Type). Press Enter to begin the testing cycle. If the Card isn’t found, power
off the PC and verify that the Card is properly seated in the PCI slot.

I ran the diag.exe program in both the DRIVERS\DIAG\93C46 and DRIVERS\DIAG\93C66 directories. Both resulted in a message stating:

1Find PCI Adapter
2Error !! Error!!
3
4Check the hardware setup of your personal computer.
5Linksys LNE100TX(v5) Fast Ethernet Adapter not found.
6OR it is not PCI machine.
7Contact your dealer or Linksys

This network card currently works in Windows 98SE.

I attempted the instructions on this post:

First, you need lsl.com and ipxodi.com from novell netware, then you also need a novell clien packet driver for your network car […]
Show full quote
First, you need lsl.com and ipxodi.com from novell netware, then you also need a novell clien packet driver for your network card alongside a file named "net.cfg".

Next, load in this exact order :
LSL
the card's driver
IPXODI

I grabbed LSL.COM and IPXODI.COM from Gammy's github page.

I put LSL.COM, LNE100TX.COM (Driver Disk - E:\drivers\Netware\Client\Dos), IPXODI.COM, and NET.CFG (Driver Disk - E:\drivers\Netware\Client\Dos) in my C:\NETWORK directory. Made a batch file and ran it:

1LSL.COM
2LNE100TX.COM
3IPXODI.COM

Every time that I execute this batch file, I am greeted with this message:

1EMM386 has detected error #*7 in an application
2at memory addres 04ED:013C.  To minimize the chance
3of data loss, EMM386 has halted your computer.
4For more information, consult your documentation.
5
6To restart you computer, press ENTER.

Contents on NET.CFG

1Link Driver LNE100TX
2    FRAME Ethernet_802.2
3    FRAME Ethernet_802.3
4    FRAME Ethernet_SNAP
5    FRAME Ethernet_II
6
7;	No_Early_Rx_Interrupt_Enable	; Certification, please remove the 
8					; first ";" of this line
9;       FORCE_MEDIA
10;       Connection_Type	= 10MFD	; 10M 10MFD 100M 100MFD, default is AUTO
11        TX_THRESHOLD	= 0	; 0..3,	4=Store and forward, default=0
12        RX_THRESHOLD	= 1	; 0..2,	2=Store and forward, default=1
13        CAL		= 2	; 0..3,	default = 2
14        PBL		= 10	; 0,1,2,4,8,10,20, default = 10
15        Rx_Buffer_Size	= 100	; Hex number, 100-600
16;       Slot  1
17        RX_FIFO_SIZE	= 2	; 0..2, 0 ~ 2:2K, 3:1K; 0 is default
18
19NetWare DOS Requester
20        FIRST NETWORK DRIVE = F
21        NETWARE PROTOCOL = NDS BIND
22;       MAX IPG = 0
23;       PBURST READ WINDOW SIZE=45
24;       PBURST WRITE WINDOW SIZE=45

CONFIG.SYS

1DOS=HIGH,UMB
2DEVICE=C:\WINDOWS\HIMEM.SYS  /TESTMEM:OFF
3DEVICE=C:\WINDOWS\EMM386.EXE RAM AUTO I=B000-B7FF
4DEVICEHIGH=C:\DRIVERS\CDRom\VIDECDD.SYS /D:OPTICAL
5
6FILES=30
7BUFFERS=30
8LASTDRIVE=H
9DEVICE=C:\WINDOWS\SETVER.EXE

AUTOEXEC.BAT

1SET PROMPT=$p$g
2SET winbootdir=C:\WINDOWS
3SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND
4SET BLASTER=A220 I7 D1 H5 P330 T6
5LH C:\WINDOWS\COMMAND\MSCDEX.EXE /D:OPTICAL
6LH C:\DRIVERS\Mouse\CTMOUSE.EXE /R9
7C:\DRIVERS\Ekm049\Ek1m.exe -f C:\Drivers\EKM049\Ek1m.cfg
8C:\Drivers\SETYMF\Setymf.exe /INITONLY

I'm listing the complete directory structure below (DIRECTORIES in uppercase and files in lowercase)

1ACROBAT
2     rp500enu.exe
3AUTORUN
4     WINDOWS
5          XP
6               lne100v5.sys
7               netlne5.cat
8               netlnev5.inf
9          lne100v5.sys
10          netlnev5.cat
11          netlnev5.ini
12          w95fea.inf
13          w95fea.sys
14     install.exe
15     linksys.ico
16     remove.exe
17     setup.exe
18     setup.ini
19DRIVERS
20     CLIENT32
21          lne100tx.inf
22          lne100tx.lan
23          len100tx.ldi
24          readme.txt
25     DIAG
26          93C46
27               diag.exe
28               readme.txt
29          93C66
30               diag.exe
31               readme.txt
32     FREEBSD
33          readme.txt
34     LINUX
35          copying
36          netdrv.tgz
37          readme.txt
38     MSLANMAN,DOS
39          DRIVERS
40               FAST
41                    LNE100
42                         lne100.dos
43                         protocol.ini
44               NIF
45                    lne100.nif
46     MSLANMAN.OS2
47          DRIVERS
48               FAST
49                    LNE100
50                         lne100.os2
51                         protocol.ini
52               NIF
53                    lne100.nif
54     NDIS
55          DOS
56               lne100.dos
57               lne100.nif
58               oemsetup.inf
59               protocol.ini
60          OS2

…Show last 89 lines

61               lne100.nif
62               lne100.os2
63               protocol.ini
64          banyan.txt
65          lanman.txt
66          lansvr.txt
67          lantasti.txt
68          ndis.txt
69          pathwork.txt
70          pcnfs.txt
71     NETWARE
72          CLIENT
73               DOS
74                    lne100tx.com
75                    lne100tx.ins
76                    net.cfg
77                    readme.txt
78          SERVER
79               NW31X
80                    autoexec.ncf
81                    etherertsm.nlm
82                    lne100tx.lan
83                    len100tx.ldi
84                    msm31x.nlm
85                    nbi31x.nlm
86                    readme.txt
87               NS50
88                    lne100tx.lan
89                    len100tx.ldi
90                    readme.txt
91               NW411
92                    lne100tx.inf
93                    lne100tx.lan
94                    len100tx.ldi
95                    readme.txt
96     PKTDRV
97          lne100tx.com
98          readme.txt
99     SCO5
100          lne100tx.sc5
101          readme.txt
102     WFW311
103          lne100.dos
104          lne100.nif
105          oemsetup.inf
106          protocol.ini
107          readme.txt
108     WINNT
109          WNT35
110               lne100v5.sy_
111          WNT40
112               lne100v5.sy_
113          lne100v5.hl_
114          readme.txt
115     WINXP
116          lne100v5.sys
117          netnev5.cat
118          netlnev5.inf
119     disk1
120     lne100v5.sys
121     netlnev5.cat
122     netlnev5.inf
123     oemsetup.inf
124     readme.exe
125     readme.ini
126     readme.txt
127     readme95.txt
128     version.txt
129     w95fea.inf
130     w95fea.sys
131MANUAL
132     lne100tx_5.1-ug-revcweb.pdf
133WINNT
134     WNT35
135          lne100v5.sy_
136     WNT40
137          lne100v5.sy_
138     lne100v5.hl_
139     readme.txt
140autorun.bat
141autorun.ini
142linksys.ico
143lne100v5.sys
144netlnev5.cat
145netlnev5.inf
146oemsetup.inf
147w95fea.inf
148w95fea.sys

Last edited by w0lf42 on 2019-01-26, 06:35. Edited 1 time in total.

Reply 1 of 5, by wiretap

Posted on 2019-01-18, 17:20

wiretap Offline

Rank Oldbie

Rank: Oldbie
Posts: 1936
Joined: 2018-05-17, 08:26
Location: USA

Are you in actual DOS, or just running a DOS prompt window from the OS?

I'm using a LNE100TX v2.0 and IPX works under real DOS when I play Doom over IPX with my other retro machines. I just used the driver config off the install CD. Also, make sure you're using the right version driver/programs, because I had to match my NIC's hardware rev# with the software driver rev#.

My Github
Circuit Board Repair Manuals

Reply 2 of 5, by bakemono

Posted on 2019-01-18, 21:38

bakemono Offline

Rank Oldbie

Rank: Oldbie
Posts: 693
Joined: 2018-01-15, 06:56

Do you need EMM386 for something? I only ever used it for playing Master of Magic myself, so I don't know all the options for it, but maybe you need to exclude part of the upper memory area for the NIC driver?

I looked at some of my old NET.CFG files and they tend to look like this:

1Link Driver DRIVER_NAME
2    FRAME Ethernet_802.2
3    protocol IPX E0 Ethernet_802.2
4
5Link Support
6        Buffers 8 1514

Note that the "E0" is something like a network ID. I think you can set it to anything but it has to match the other computers you want to communicate with.

Reply 3 of 5, by w0lf42

Posted on 2019-01-21, 22:49

w0lf42 Offline

Rank Newbie

Rank: Newbie
Posts: 80
Joined: 2018-07-26, 04:20

Thanks for the responses. Here's an update.

Are you in actual DOS, or just running a DOS prompt window from the OS?

Well, in Windows 98SE, I "Restart in MS-DOS mode" and that gives me MS-DOS 7.10.

Do you need EMM386 for something?

If I REM out EMM386 the system just hangs after executing LSL.COM

1DOS=HIGH,UMB
2DEVICE=C:\WINDOWS\HIMEM.SYS  /TESTMEM:OFF
3REM DEVICE=C:\WINDOWS\EMM386.EXE RAM AUTO I=B000-B7FF
4REM DEVICEHIGH=C:\DRIVERS\CDRom\VIDECDD.SYS /D:OPTICAL
5
6FILES=30
7BUFFERS=30
8LASTDRIVE=H
9DEVICE=C:\WINDOWS\SETVER.EXE

Also, make sure you're using the right version driver/programs, because I had to match my NIC's hardware rev# with the software driver rev#.

I am using the driver disk that came with my NIC

I looked at some of my old NET.CFG files

Thanks. I tried using your config file with the same previous results

1Link Driver LNE100TX
2    FRAME Ethernet_802.2
3    protocol IPX E0 Ethernet_802.2
4
5Link Support
6        Buffers 8 1514

Reply 4 of 5, by bakemono

Posted on 2019-01-26, 00:59

bakemono Offline

Rank Oldbie

Rank: Oldbie
Posts: 693
Joined: 2018-01-15, 06:56

If I REM out EMM386 the system just hangs after executing LSL.COM

That's weird, maybe you can try a different LSL.COM. I've seen two different versions, one is dated '99 and has 18,285 bytes, the other is '94 and 18,313 bytes. Not sure if it's OK to distribute here.

again another retro game on itch: https://90soft90.itch.io/shmup-salad

Reply 5 of 5, by w0lf42

Posted on 2019-01-26, 06:34

w0lf42 Offline

Rank Newbie

Rank: Newbie
Posts: 80
Joined: 2018-07-26, 04:20

Thank you for the suggestion! Because of your help (and fixing some dumb issues on my end) it's working. If anyone is interested in the details, I put them below.

As far as the NIC being detected.... It was working in Windows 98SE. I assumed that it was still working because my WOL app on my phone still turned on my computer. But, when I looked at the Device Manager, it did not show a network adapter. I removed the card and reinserted it -- It worked!

I got a new-to-me version of LSL.com here

Batch File

1@echo off
2lsl
3lne100tx
4ipxodi

config.sys

1DEVICE=C:\WINDOWS\HIMEM.SYS  /TESTMEM:OFF
2DOS=HIGH,UMB
3DEVICE=C:\WINDOWS\EMM386.EXE RAM AUTO I=B000-B7FF
4DEVICEHIGH=C:\DRIVERS\CDRom\VIDECDD.SYS /D:OPTICAL
5
6FILES=30
7BUFFERS=30
8LASTDRIVE=H
9DEVICE=C:\WINDOWS\SETVER.EXE

NET.CFG

1Link Driver LNE100TX
2    FRAME Ethernet_802.2
3    FRAME Ethernet_802.3
4    FRAME Ethernet_SNAP
5    FRAME Ethernet_II
6
7;   No_Early_Rx_Interrupt_Enable   ; Certification, please remove the 
8               ; first ";" of this line
9;       FORCE_MEDIA
10;       Connection_Type   = 10MFD   ; 10M 10MFD 100M 100MFD, default is AUTO
11        TX_THRESHOLD   = 0   ; 0..3,   4=Store and forward, default=0
12        RX_THRESHOLD   = 1   ; 0..2,   2=Store and forward, default=1
13        CAL      = 2   ; 0..3,   default = 2
14        PBL      = 10   ; 0,1,2,4,8,10,20, default = 10
15        Rx_Buffer_Size   = 100   ; Hex number, 100-600
16;       Slot  1
17        RX_FIFO_SIZE   = 2   ; 0..2, 0 ~ 2:2K, 3:1K; 0 is default
18
19NetWare DOS Requester
20        FIRST NETWORK DRIVE = F
21        NETWARE PROTOCOL = NDS BIND
22;       MAX IPG = 0
23;       PBURST READ WINDOW SIZE=45
24;       PBURST WRITE WINDOW SIZE=45

Message

1NetWare Link Support Layer v2.11 (940817)
2(C) Copyright 1990-1994 Novell, Inc. All Rights Reserved.
3
4The configuration file used was "C:\DRIVERS\NETWORK2\NET.CFG".
5Max Boards 4, Max Stacks 4
6
7Linksys LNE1ooTX Fast Ethernet Adapter(LNE100TX v5) v 1.14 (010403)
8
9Slot 1, IRA 7, Port DC00, Node Address C41EC205A L
10Max Frame 1514 bytes, Line Speed 100 Mbps Full Duplex
11Board 1, Frame ETHERNET_802.2, LSB Mode
12Board 2, Frame ETHERNET_802.3, LSB Mode
13Board 3, Frame ETHERNET_SNAP, LSB Mode
14Board 4, Frame ETHERNET_II, LSB Mode
15
16NetWare IPX/SPX Protocol v3.00 BETA 5 (940812)
17(C) Copyright 1990-1994 Novell, Inc.  All Rights Reserved.
18
19Bound to logical board 1 (LNE100TX) : Protocol ID E0

Go to top of page Go to top of page

Back to Software

Main menu

Common searches